I did, in fact it was another reason that I posted the above. Consistent
interfaces as suggested are well, fine, and good, but (XthreadX with UDI)
you can't always maintain interface consistency when that interface is
broken, as with the dev->flush() changes. And /proc/cpuinfo strikes me as
an interface which may well have problems being simultaneously consistent
and complete while addressing multiple CPU architecture families (heck, it's
been a problem just between Intel, AMD, and Cyrix; should we be surprised at
problems between x86 and PPC, Alpha, SPARC, ...?).
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/