linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Michel Bouissou <michel@bouissou.net>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble
Date: Tue, 12 Jul 2005 14:15:54 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0507121412490.5351-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <200507121903.49792@totor.bouissou.net>

On Tue, 12 Jul 2005, Michel Bouissou wrote:

> > In case it's not already clear, when you install this patch the UHCI
> > controllers will not be useable.
> 
> Okay, the patch applied easily and the kernel is now compiling. When 
> installed, I'll try and boot it (and will use a PS/2 mouse instead of my 
> current USB mouse, or should I rather try to plug my USB mouse to the 
> ehci_hcd controller ?).

USB mice generally run at low speed.  This means that you _can't_ plug it 
into an EHCI controller -- the controller will see that it's not a 
high-speed device and will hand it over to a companion controller, which 
in your case will be UHCI.

> How would you like me to boot ? With or without the "usb-handoff" option ? 
> With or without the BIOS "USB mouse support" option ?

Use "usb-handoff" and turn off BIOS USB mouse support.

> And once booted, what information will you be interested in ?

I'll be interested in seeing if you still get the "IRQ 21 nobody cared" 
message.

Alan Stern


  reply	other threads:[~2005-07-12 18:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 18:50 Kernel 2.6.12 + IO-APIC + uhci_hcd = Trouble Protasevich, Natalie
2005-07-11  9:06 ` Michel Bouissou
2005-07-11 18:36   ` Alan Stern
2005-07-11 19:33     ` [SOLVED ??] " Michel Bouissou
2005-07-11 19:43       ` Alan Stern
2005-07-11 20:02         ` Michel Bouissou
2005-07-11 20:16           ` Alan Stern
2005-07-11 20:46             ` Michel Bouissou
2005-07-11 20:58               ` Michel Bouissou
2005-07-11 21:21                 ` [NOT solved] " Michel Bouissou
2005-07-11 21:21               ` [SOLVED ??] " Alan Stern
2005-07-11 21:34                 ` Michel Bouissou
2005-07-12  1:54                   ` Alan Stern
2005-07-12  7:54                     ` Michel Bouissou
2005-07-12 14:12                       ` Alan Stern
2005-07-12 17:03                         ` Michel Bouissou
2005-07-12 18:15                           ` Alan Stern [this message]
2005-07-12 18:16                           ` Michel Bouissou
2005-07-12 18:57                             ` Alan Stern
2005-07-12 20:40                               ` Michel Bouissou
2005-07-12 21:37                                 ` Alan Stern
2005-07-12 22:01                                   ` Michel Bouissou
  -- strict thread matches above, loose matches on Subject: below --
2005-07-12 23:16 Protasevich, Natalie
2005-07-13  6:46 ` Michel Bouissou
2005-07-12 21:02 Protasevich, Natalie
2005-07-10  8:11 Michel Bouissou

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.44L0.0507121412490.5351-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=Natalie.Protasevich@UNISYS.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@bouissou.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;
as well as URLs for NNTP newsgroup(s).