Hi! > > > And what to do if internal keyboard is not platform but USB? Like > > > Google "Whiskers"? (I am not sure why you decided to drop my mention > > > of internal USB keyboards completely off your reply). > > > > I don't have answers for everything. Even if you have USB keyboard, you'll > > likely still have backlight connected to embedded controller. If not, > > then maybe you have exception userland needs to know about. > > > > Still better than making everything an exception. > > You do not need to make everything exception. You just need to look > beyond the name, and see how the device is connected. And then apply > your exceptions for "weird" devices. "Where it is connected" is not interesting to the userland. "Is it backlight for internal keyboard" is the right question. It may be connected to embedded controller or some kind of controller over i2c... my shell scripts should not need to know about architecture of every notebook out there. But I don't see why I should do additional work when its trivial for kernel to just name the LED in an useful way. "platform::kbd_backlight" has no disadvantages compared to "wilco::kbd_backlight" ... so lets just use it. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
