Re: [PATCH] Default keyboard LEDs

2008-01-14 Thread Samuel Thibault
H. Peter Anvin, le Sun 13 Jan 2008 19:50:34 -0800, a écrit : > >Actually, what would be perfect would be to use the configuration that > >the BIOS sets at boot by default. That is device-dependent, however. > > > > It is, but it can be read out either by INT calls at initialization > time, or by

Re: [PATCH] Default keyboard LEDs

2008-01-14 Thread Samuel Thibault
Jan Engelhardt, le Mon 14 Jan 2008 02:40:08 +0100, a écrit : > On Jan 14 2008 00:52, Samuel Thibault wrote: > >In many cases, one prefers to have e.g. the NumLock on by default. In > >many cases, one doesn't want to have it by default, e.g. on laptops. > > > >Distributions actually have a very har

Re: [PATCH] Default keyboard LEDs

2008-01-13 Thread H. Peter Anvin
Samuel Thibault wrote: In many cases, one prefers to have e.g. the NumLock on by default. In many cases, one doesn't want to have it by default, e.g. on laptops. Distributions actually have a very hard time trying to set this correctly after the kernel boot, and that doesn't work for new consol

Re: [PATCH] Default keyboard LEDs

2008-01-13 Thread Jan Engelhardt
On Jan 14 2008 00:52, Samuel Thibault wrote: > >In many cases, one prefers to have e.g. the NumLock on by default. In >many cases, one doesn't want to have it by default, e.g. on laptops. > >Distributions actually have a very hard time trying to set this >correctly after the kernel boot, and that

[PATCH] Default keyboard LEDs

2008-01-13 Thread Samuel Thibault
In many cases, one prefers to have e.g. the NumLock on by default. In many cases, one doesn't want to have it by default, e.g. on laptops. Distributions actually have a very hard time trying to set this correctly after the kernel boot, and that doesn't work for new consoles that are created via t