From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: newbie kernel hacking question.
Date: Fri, 03 Dec 2004 09:22:06 -0800 [thread overview]
Message-ID: <41B0A0BE.3070107@osdl.org> (raw)
In-Reply-To: <200412031715.15067.nick@linicks.net>
Nick Warne wrote:
> Hi all,
>
> I am trying to learn more in operation of kernel, and decided to attempt some
> small hacks with a meaningful purpose - 'see it in action' type stuff rather
> than just play.
>
> One area to start with I decided is the keyboard warning at boot. I have 5
> headless/keyboardless boxes and wish the kernel to stop reporting I have no
> keyboard at boot(I KNOW!!).
>
> I finally located where kb gets initialized.
>
> Is it this simple just to undef this in /include/linux/pc_keyb.h
>
> #define KBD_REPORT_TIMEOUTS /* Report keyboard timeouts */
>
> I have read code through, and it appears the right thing to do (and it's so
> simple I am in doubt it is this easy), but I am loath to try it in case the
> box doesn't come up and I will have to fart around getting out monitor and kb
> and move my sofa for access and stuff...
>
> Thanks for any help.
Yes, it looks like that should do it in Linux 2.4.x.
The keyboard driver isn't the same in 2.6.x....
--
~Randy
next prev parent reply other threads:[~2004-12-03 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 17:15 newbie kernel hacking question Nick Warne
2004-12-03 17:22 ` Randy.Dunlap [this message]
2004-12-03 17:44 ` Nick Warne
[not found] ` <1102096955.14037.5.camel@mcmanus.datapower.com>
2004-12-03 18:23 ` Nick Warne
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=41B0A0BE.3070107@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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