From: Andy Isaacson <adi@hexapodia.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB IRQ routing problems on Via Apollo Pro 133A
Date: Fri, 7 Sep 2001 16:44:56 -0500 [thread overview]
Message-ID: <20010907164456.A27672@hexapodia.org> (raw)
In-Reply-To: <20010906004520.A2891@hexapodia.org> <20010906202536.A11264@middle.of.nowhere> <20010907154129.B9370@hexapodia.org> <20010907135703.D25421@kroah.com>
In-Reply-To: <20010907135703.D25421@kroah.com>; from greg@kroah.com on Fri, Sep 07, 2001 at 01:57:03PM -0700
On Fri, Sep 07, 2001 at 01:57:03PM -0700, Greg KH wrote:
> On Fri, Sep 07, 2001 at 03:41:29PM -0500, Andy Isaacson wrote:
> > Booting a non-APIC kernel makes it work, of course.
> >
> > The system is a Tyan Tiger 133A, Via Apollo Pro 133A chipset, SMP,
> > currently running 2.4.9. Complete dmesg, lspci -vvvvxxxx, and
> > /proc/interrupts are at
> > http://web.hexapodia.org/~adi/straum/usb/
>
> That's the only solution to enable the on board USB controller for this
> motherboard, sorry. If you can't live with noapic mode, spend $20 for
> a PCI USB controller.
Are you claiming that the USB controller IRQ line isn't routed to the
APIC? If so, I'm curious as to any evidence you can provide to that
effect.
I'd appreciate a pointer to any discussion or whatnot. URL? Or even a
suggestion for where to search? I think I've looked pretty
thoroughly...
But looking at noapic mode a bit more closely, it appears likely that I
can survive with its limitations, so thanks for the tip!
-andy
next prev parent reply other threads:[~2001-09-07 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010906004520.A2891@hexapodia.org>
[not found] ` <20010906202536.A11264@middle.of.nowhere>
2001-09-07 20:41 ` USB IRQ routing problems on Via Apollo Pro 133A Andy Isaacson
2001-09-07 20:57 ` Greg KH
2001-09-07 21:44 ` Andy Isaacson [this message]
2001-09-07 21:54 ` Greg KH
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=20010907164456.A27672@hexapodia.org \
--to=adi@hexapodia.org \
--cc=greg@kroah.com \
--cc=linux-kernel@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