Date: Thu, 16 Oct 2008 21:11:06 +0200
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use PC-BIOS NUMLOCK flag
Message-ID: <20081016191106.GB4988@const.famille.thibault.fr>
Mail-Followup-To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Bodo Eggert <7eggert@gmx.de>, linux-kernel@vger.kernel.org
References: <alpine.LSU.0.999.0810161358540.5404@be1.lrz> <20081016143856.GD5071@const.bordeaux.inria.fr> <alpine.LSU.0.999.0810161958450.5051@be1.lrz>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.LSU.0.999.0810161958450.5051@be1.lrz>
User-Agent: Mutt/1.5.12-2006-07-14
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1140
Lines: 25

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" :)

Samuel
--
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/