From: Krishnakumar B <kitty@cs.wustl.edu>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] AT Keyboard not present?
Date: Fri, 07 Sep 2001 19:55:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805141@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805137@msgid-missing>
On Friday, 7 September 2001, Johannes Erdfelt wrote:
>
> The only way to supress the message is to hack it out of the kernel.
>
> The message comes from the fact the BIOS does legacy device emulation
> for USB keyboards and mice. I think the ia64 BIOS supports this as well.
> However, the emulation isn't perfect and will cause messages like this.
>
> When the HC driver loads, it turns this off and natively handles the USB
> keyboard.
>
> The real fix is to use USB drivers as early as possible.
How does one do this ? Can it be loaded via initrd ? I got some symbol
referencing errors while doing this. Then the uhci module was loaded as
usual when booting and this time there were no symbol referencing errors.
-kitty.
--
Krishnakumar B <kitty at cs dot wustl dot edu>
Distributed Object Computing Laboratory, Washington University in St.Louis
next prev parent reply other threads:[~2001-09-07 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 17:49 [Linux-ia64] AT Keyboard not present? KOCHI Takayoshi
2001-09-07 19:05 ` Krishnakumar B
2001-09-07 19:36 ` Johannes Erdfelt
2001-09-07 19:55 ` Krishnakumar B [this message]
2001-09-07 20:02 ` Johannes Erdfelt
2001-09-07 20:09 ` Khalid Aziz
2001-09-07 20:12 ` KOCHI Takayoshi
2001-09-10 8:46 ` Martin Wilck
2001-09-10 21:43 ` Michael Madore
2001-09-10 22:10 ` Luck, Tony
2001-09-10 23:28 ` David Mosberger
2001-09-19 13:35 ` Richard Hirst
2001-09-19 21:49 ` David Mosberger
2001-09-19 22:27 ` Richard Hirst
2001-09-20 22:56 ` Richard Hirst
2001-09-21 15:44 ` David Mosberger
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=marc-linux-ia64-105590698805141@msgid-missing \
--to=kitty@cs.wustl.edu \
--cc=linux-ia64@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