From: Niels de Vos <niels.devos@wincor-nixdorf.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Get NUMLOCK from PC BIOS
Date: Wed, 2 Jan 2008 15:11:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20080102T150709-806@post.gmane.org> (raw)
In-Reply-To: <alpine.LSU.0.999.0712301230270.3273@be1.lrz>
> + 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.
Looks good. But would it not be helpfull to have a kernel-parameter for
overruling the BIOS-setting?
Cheers,
Niels
prev parent reply other threads:[~2008-01-02 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 11:38 Bodo Eggert
2008-01-02 15:11 ` Niels de Vos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20080102T150709-806@post.gmane.org \
--to=niels.devos@wincor-nixdorf.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome