Hi! > >> Often, in the embedded world, the person defining the operating > >> states will not be a kernel developer, and may not be comfortable > >> with, or capable of, creating a kernel module. (There are > > > > That's okay, we can create HOWTO or something. 'System designed is too > > stupid to hack kernel' should not be an argument. > > It's not a matter of stupidity. The example I gave of not being > able to create a kernel module was the situation where loadable > module support is not available. A HOWTO wouldn't alter this. So they need to recompile the kernel. Not a big deal when you are developing new machine. > > Maybe operating points need to be changed at runtime -- I do not think > > so -- but *please* get the basic stuff in/merged ASAP and then add > > features one-by-one. > > I agree. :-) Yes, I believe we are actually in agreement. Maybe features you want will indeed be useful, but we want to get basics right, first. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
