From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>,
Ruben Puettmann <ruben@puettmann.net>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: Problems with usb-ohci on 2.4.22-preX
Date: Tue, 15 Jul 2003 12:42:06 -0700 [thread overview]
Message-ID: <3F14590E.90202@pacbell.net> (raw)
In-Reply-To: <20030715192241.GA4862@kroah.com>
Greg KH wrote:
> On Tue, Jul 15, 2003 at 11:34:03AM -0700, David Brownell wrote:
>
>>I've hardly ever seen ACPI do anything except break USB.
>
>
> Heh, my laptop _requires_ ACPI to get USB to work properly :)
The fact that I've seen one laptop work with ACPI is the
entire reason I said "hardly ever" ... ;) I've seen some
hardware work with "pci=noacpi", which still counts as
broken in my book.
Desktop hardware has uniformly broken if I enable ACPI in
the build. The usual rule of thumb seems to be that when
ACPI assigns the USB IRQs to values over 16, they won't
work for me ... example, 2.5.75 on an SN41G2 assigned
all four USB controllers (including a net2280!) that way.
That was a curious symptom though: /proc/interrupts
showed endless streams of IRQs going to the devices,
rather than the somewhat-more-typical "no IRQs". I had
not seen that before. (It was almost a 2.6-test1 kernel.)
In theory, this is just a bug that will get fixed, but
in practice, the behavior has never yet changed.
- dave
prev parent reply other threads:[~2003-07-15 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 14:14 Problems with usb-ohci on 2.4.22-preX Ruben Puettmann
2003-07-13 4:21 ` Greg KH
2003-07-13 8:04 ` Ruben Puettmann
2003-07-15 13:47 ` Roger Larsson
2003-07-15 18:34 ` [linux-usb-devel] " David Brownell
2003-07-15 19:22 ` Greg KH
2003-07-15 19:42 ` David Brownell [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=3F14590E.90202@pacbell.net \
--to=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=roger.larsson@skelleftea.mail.telia.com \
--cc=ruben@puettmann.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).