From: Xavier Bestel <xavier.bestel@free.fr>
To: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Cc: "Robert W. Fuller" <orangemagicbus@sbcglobal.net>,
linux-kernel@vger.kernel.org
Subject: Re: Documentation/i386/IO-APIC.txt (Re: 2.6.11 USB broken on VIA computer (not just ACPI))
Date: Wed, 16 Mar 2005 11:08:12 +0100 [thread overview]
Message-ID: <1110967692.20838.224.camel@gonzales> (raw)
In-Reply-To: <1110967201.20838.221.camel@gonzales>
Le mercredi 16 mars 2005 à 11:00 +0100, Xavier Bestel a écrit :
> Le mardi 15 mars 2005 à 21:54 -0800, Andrew Morton a écrit :
> > You may be able to set the thing up by hand with the help of
> > Documentation/i386/IO-APIC.txt.
>
> There's something I don't get in this document's ascii-art:
>
> 8<------------------------------------------------------------------
> ,-. ,-. ,-. ,-. ,-.
> PIRQ4 ----| |-. ,-| |-. ,-| |-. ,-| |--------| |
> |S| \ / |S| \ / |S| \ / |S| |S|
> PIRQ3 ----|l|-. `/---|l|-. `/---|l|-. `/---|l|--------|l|
> |o| \/ |o| \/ |o| \/ |o| |o|
> PIRQ2 ----|t|-./`----|t|-./`----|t|-./`----|t|--------|t|
> |1| /\ |2| /\ |3| /\ |4| |5|
> PIRQ1 ----| |- `----| |- `----| |- `----| |--------| |
> `-' `-' `-' `-' `-'
>
> every PCI card emits a PCI IRQ, which can be INTA,INTB,INTC,INTD:
>
> ,-.
> INTD--| |
> |S|
> INTC--|l|
> |o|
> INTB--|t|
> |x|
> INTA--| |
> `-'
>
> These INTA-D PCI IRQs are always 'local to the card', their real meaning
> depends on which slot they are in. If you look at the daisy chaining diagram,
> a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ2 of
> the PCI chipset. [...]
> 8<------------------------------------------------------------------
>
> If I follow the wire from Slot4's INTA, I'm ending on PIRQ4 whereas the
> doc says IRQ2. Do I need glasses, or a new fixed-font ?
Sorry for replying to myself, in fact it seems like somebody reversed
the order of PIRQ[1-4] and INT[A-D] in the ascii-art, but didn't touch
the rest of the text at all. There are several more references to a
"reversed order".
Xav
next prev parent reply other threads:[~2005-03-16 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 3:19 2.6.11 USB broken on VIA computer (not just ACPI) Robert W. Fuller
2005-03-16 4:39 ` Andrew Morton
2005-03-16 5:28 ` Robert W. Fuller
2005-03-16 5:31 ` Andrew Morton
2005-03-16 5:37 ` Robert W. Fuller
2005-03-16 5:54 ` Andrew Morton
2005-03-16 6:58 ` Robert W. Fuller
2005-03-16 17:19 ` Greg KH
2005-03-16 17:50 ` Robert W. Fuller
2005-03-16 17:56 ` Greg KH
2005-03-16 10:00 ` Documentation/i386/IO-APIC.txt (Re: 2.6.11 USB broken on VIA computer (not just ACPI)) Xavier Bestel
2005-03-16 10:08 ` Xavier Bestel [this message]
2005-03-16 17:17 ` 2.6.11 USB broken on VIA computer (not just ACPI) 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=1110967692.20838.224.camel@gonzales \
--to=xavier.bestel@free.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=orangemagicbus@sbcglobal.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
all inboxes | Powered by JetHome®