Hi! > > > I guess it just defines an appropriate policy. You can call it > > > 'usb_mp3' if you wish ;) > > > I don't think it's too embedded-specific. > > > > Well, it leads to exponential number of policies -- not nice. Having > > usb_mp3_fileserver_webserver is not nice. > > To some extent having lots of specific policies in the embedded space is > inevitable. The hardware is very tightly coupled. You may have Maybe. But you certainly do not have to export that uglyness to userspace. > I have some notion that a policy manager can create a state with simple > & general names like fast, medium, slow (whatever) which is the > interface in which applications might speak. A complex policy > manager ...which is very bad interface for applications. See my other mail. Applications should not have to play with fast/medium/slow, explicitely. Instead, on opening /dev/dsp, you should power up the sound system (and maybe adjust cpu frequency if neccessary). Application should not have to do echo fast > somewhere before opening /dev/dsp. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
