Hi! > > Of greatest importance to us would be to know what facilities your project > > needs the kernel to provide, particularly for peripheral power management. > > As yet there isn't an agreed-upon design, and it would help to know what > > users will want. > > That's a pretty difficult question to answer - I guess the most > important for user space is having a uniform interface to the kernel > that it easy to use. > > That's pretty broad, I realize that, to me it means > > - sysfs interface > > - asynchronous change notification using e.g. uevents > - this is both per device but also for things like "Not enough > power to use USB device XYZ" (both Windows and OS X does this) > - IIRC we currently lack this for e.g. ACPI suspend/resume What uevents would you want and why? Currently, there are no events (except X see console switches). That's on purpose; if you want to send some events, just do send suspend events echo 4 > /proc/acpi/sleep send resume events in a script. Is it inadequate? I don't think so. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
