mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Linux kernel" <linux-kernel@vger.kernel.org>,
	<linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] USB Keyboard
Date: Thu, 15 Mar 2007 17:40:39 -0400	[thread overview]
Message-ID: <Pine.LNX.4.61.0703151736070.5767@chaos.analogic.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0703151723350.2482-100000@iolanthe.rowland.org>


On Thu, 15 Mar 2007, Alan Stern wrote:

> On Thu, 15 Mar 2007, Dmitry Torokhov wrote:
>
>> On 3/15/07, linux-os (Dick Johnson) <linux-os@analogic.com> wrote:
>>> echo "Loading uhci-hcd.ko module"
>>> insmod /lib/uhci-hcd.ko
>>> echo "Loading ehci-hcd.ko module"
>>> insmod /lib/ehci-hcd.ko
>>
>> I don't see you loading OHCI and I thought AMD boxes used that flavor.
>
> It depends on the chipset used for the motherboard.  Intel and VIA use
> UHCI, pretty much everyone else uses OHCI.
>
> Dick, there's an even simpler way to debug this.  Install your special CD
> on a machine with an old-fashioned PS/2 keyboard and use that!
>
> Alan Stern

It's not the same hardware and all the machines that I tried that
have keyboards end up WORKING with the USB keyboard as well!  But
Dmitry Torokhov was right! I just burned a CD with all three modules,
and the keyboard works! I didn't bother to check the DEBUG messages.
It's interesting that the "wrong" module loaded fine with no warnings
that it might not be the correct one!

Thanks a lot.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5615.29 BogoMips).
New book: http://www.AbominableFirebug.com/
_
\x1a\x04

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

  reply	other threads:[~2007-03-15 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 17:32 linux-os (Dick Johnson)
2007-03-15 17:36 ` Jiri Kosina
2007-03-15 17:49   ` linux-os (Dick Johnson)
2007-03-15 17:53     ` Jiri Kosina
2007-03-15 17:59       ` Dmitry Torokhov
2007-03-15 18:18       ` linux-os (Dick Johnson)
2007-03-15 19:07         ` [linux-usb-devel] " Alan Stern
2007-03-15 19:58           ` linux-os (Dick Johnson)
2007-03-15 20:07             ` Dmitry Torokhov
2007-03-15 21:25               ` Alan Stern
2007-03-15 21:40                 ` linux-os (Dick Johnson) [this message]
2007-03-16  1:54                   ` Alan Stern
2007-03-15 21:41               ` linux-os (Dick Johnson)
2007-03-15 21:43             ` Jiri Kosina
2007-03-15 21:49               ` linux-os (Dick Johnson)
2007-03-15 21:54                 ` Jiri Kosina

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=Pine.LNX.4.61.0703151736070.5767@chaos.analogic.com \
    --to=linux-os@analogic.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®