Messages in this thread | | | Date | Tue, 3 Jul 2007 09:12:37 +0200 | From | Bernhard Walle <> | Subject | Re: blink driver power saving |
| |
* Pavel Machek <pavel@ucw.cz> [2007-07-03 01:08]: > On Mon 2007-07-02 14:39:27, Andi Kleen wrote: > > > > > > 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.
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).
Thanks, Bernhard - 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/
| |