Messages in this thread | | | Date | Wed, 4 Jul 2007 21:37:12 +0200 | From | Pavel Machek <> | Subject | Re: blink driver power saving |
| |
Hi!
> > > > > Perhaps one of you geniuses who all hate it can find a better way to > > > > > solve the "video output dead after kexec; but need visual feedback to the user > > > > > while crash dumping" problem. I'm waiting for your patches. > > > > > > > > > > > > > I don't don't like it ;) Unfortunately too many people end up enabling > > > > > > Yes that's pretty weird. I admit I hadn't expected > > > that problem. blink is equivalent to "annoy me" and it > > > is a mystery why so many people should willingly ask their computer to > > > annoy them. > > > > tristate "Keyboard blink driver" > > > > ...drivers are not expected to act on their own. I was expecting to > > get nice /sys/class/led* interface to my keyboard leds. > > What's the benefit of such an interface? If you're able to trigger > keyboard LEDs via that interface, you're also able to use the ioctl() > on /dev/console.
Well, at least it is standartized interface... plus it can do stuff like "blink that led on disk access".
> I think the intention of the blink driver was to have a *early* blink, > i.e. before initrd (and on systems without intrd, before the first > init script runs).
...and yes, it can autoblink, too. It should be even possible to set default behaviour of led to blink, doing what the blink driver does, but in a clean way. 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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |