Messages in this thread | | | Date | Sun, 21 Jul 2002 10:08:18 +0100 | From | Russell King <> | Subject | Re: [PATCH -ac] Panicking in morse code v3 |
| |
On Sun, Jul 21, 2002 at 06:49:55PM +1000, Brad Hards wrote: > While it will be non-trivial, it won't be hard either. > The advantage of the input layer is that it no longer matters what > type of keyboard is attached - you can just call input_event() and > turn on and off the LED. The input layer abstracts out the magic > values needed for any particular keyboard.
Hmm. I thought the original idea for the "flash LEDs on panic" was so you knew something had gone wrong early in the boot, at the kind of places where you don't have a console initialised. If you don't have the console initialised, you sure as hell don't have the input layer or keyboard drivers initialised.
Otherwise it becomes a "toy" feature that doesn't have much value. What would be more useful would be to disable the console blank timer on a panic() so it doesn't blank half-way through someone reading the oops, leaving them with no way to read the rest of it!
-- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.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/
| |