[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081021133304.GB9617@ucw.cz>
Date: Tue, 21 Oct 2008 15:33:05 +0200
From: Pavel Machek <pavel@...e.cz>
To: Samuel Thibault <samuel.thibault@...-lyon.org>,
Bodo Eggert <7eggert@....de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Use PC-BIOS NUMLOCK flag
On Thu 2008-10-16 21:11:06, Samuel Thibault wrote:
> Bodo Eggert, le Thu 16 Oct 2008 20:00:31 +0200, a écrit :
> > On Thu, 16 Oct 2008, Samuel Thibault wrote:
> > > Bodo Eggert, le Thu 16 Oct 2008 13:59:49 +0200, a écrit :
> >
> > > > + If you have an alternative firmware like OpenFirmware or LinuxBios,
> > > > + this flag might not be set correctly, which results in a random state
> > > > + of the Numlock key.
> > >
> > > That's an issue. That means that distributions will just not enable,
> > > and thus the flag is not really useful, since people who would
> > > compile their own kernel would very likely have already setup their
> > > initialization scripts into calling setleds +num (or just set LEDS=+num
> > > in /etc/console-tools/config on a debian machine).
> >
> > I hope somebody will pop up and say "Hey, those will create an IBM PC data
> > area, because they run DOS" ...
>
> Mmm, or rather "hey, here are the patches to fix those BIOSes" :)
Broken bioses being around should not penalize working bioses. Patch
looks good to me. Yes, I consider LinuxBios broken in this regard.
--
(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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists