Hi! > > > Being able to assign only some of the devices to the linux console > > > would indeed probably be good, but to me it's just a refinement. Users > > > a priori assume all keyboards get their leds updated, so my patch > > > makes sense. And it won't prevent a further patch that, in addition > > > to input::<led> leds, adds per-device leds, which the user could use > > > instead of input::<led>. > > > > I think that if we want to go LED route we shoudl start with adding led > > devices to individual keyboard drivers first > > Mmm, thinking again, I think my patch could be rather easily converted > into creating led instances for each device, with proper trigger > defaults. Something like input-devicename::numlock? (devicename::numlock > might get conflicts with non-input devices I guess?) Yep, that would be cool. > That being said, usermode tools which want to set up the modifiers and > connect the input LEDs to them need an easy and proper way to do so. > Having central input::numlock and such still seems a good thing. This is something where I'm not too sure. Opening few files in sequence is not that hard to the userland so "group of leds" abstraction does not make too much sense... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
