From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
qemu-devel@nongnu.org, Arnd Bergmann <arnd.bergmann@linaro.org>
Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Mon, 12 Aug 2013 21:06:29 +0100 [thread overview]
Message-ID: <20130812200628.GG23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAFEAcA97PuORg920f-A_8rvCgBq=k5Y=0W6m2Nv8nnzjY19Utg@mail.gmail.com>
On Mon, Aug 12, 2013 at 06:33:28PM +0100, Peter Maydell wrote:
> /* Slot to IRQ mapping for RealView EB and PB1176 backplane
> * name slot IntA IntB IntC IntD
> * A 31 IRQ50 IRQ51 IRQ48 IRQ49
> * B 30 IRQ49 IRQ50 IRQ51 IRQ48
> * C 29 IRQ48 IRQ49 IRQ50 IRQ51
> * Slot C is for the host bridge; A and B the peripherals.
> * Our output irqs 0..3 correspond to the baseboard's 48..51.
> */
>
> ie IRQ48 == board's PCI0 == slot C connector A6 (IntA) == PCI_nINTB
> == Slot B connector B8 (IntD) == Slot A connector A7 (IntC).
>
> and so on round.
>
> The 926's routing is one extra round of swizzling because the
> board itself connects FPGA P_nINTA to its edge connector's
> INTB (B7) pin rather than INTA (A6) as the EB/1176 do.
> (This isn't even hinted at in the documentation, you need to
> either experiment or look at the 926 board schematic.)
Okay, so the above just adds to the confusion, because you appear to be
mistaking "slot" for the AD signal which the IDSEL pin is connected to.
As I'm seeing a report of a card appearing in slot 0x0d at the top of
this thread, this doesn't match your numbering above. So, is slot
0x0d slot A or slot B?
If we assume that slot A is indeed has IDSEL connected to AD31, then
that surely makes it slot 20 (AD11 + 20 = 31) and slot B = 19. So
why do we apparantly have a card in a non-existent slot at 13?
Now, it looks to me like we have the rotation in the right direction,
it's just a matter of ensuring that we have the right starting point.
That's where we need to know what slot number Linux believes slot A
and slot B actually are.
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
qemu-devel@nongnu.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Guenter Roeck <linux@roeck-us.net>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Mon, 12 Aug 2013 21:06:29 +0100 [thread overview]
Message-ID: <20130812200628.GG23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAFEAcA97PuORg920f-A_8rvCgBq=k5Y=0W6m2Nv8nnzjY19Utg@mail.gmail.com>
On Mon, Aug 12, 2013 at 06:33:28PM +0100, Peter Maydell wrote:
> /* Slot to IRQ mapping for RealView EB and PB1176 backplane
> * name slot IntA IntB IntC IntD
> * A 31 IRQ50 IRQ51 IRQ48 IRQ49
> * B 30 IRQ49 IRQ50 IRQ51 IRQ48
> * C 29 IRQ48 IRQ49 IRQ50 IRQ51
> * Slot C is for the host bridge; A and B the peripherals.
> * Our output irqs 0..3 correspond to the baseboard's 48..51.
> */
>
> ie IRQ48 == board's PCI0 == slot C connector A6 (IntA) == PCI_nINTB
> == Slot B connector B8 (IntD) == Slot A connector A7 (IntC).
>
> and so on round.
>
> The 926's routing is one extra round of swizzling because the
> board itself connects FPGA P_nINTA to its edge connector's
> INTB (B7) pin rather than INTA (A6) as the EB/1176 do.
> (This isn't even hinted at in the documentation, you need to
> either experiment or look at the 926 board schematic.)
Okay, so the above just adds to the confusion, because you appear to be
mistaking "slot" for the AD signal which the IDSEL pin is connected to.
As I'm seeing a report of a card appearing in slot 0x0d at the top of
this thread, this doesn't match your numbering above. So, is slot
0x0d slot A or slot B?
If we assume that slot A is indeed has IDSEL connected to AD31, then
that surely makes it slot 20 (AD11 + 20 = 31) and slot B = 19. So
why do we apparantly have a card in a non-existent slot at 13?
Now, it looks to me like we have the rotation in the right direction,
it's just a matter of ensuring that we have the right starting point.
That's where we need to know what slot number Linux believes slot A
and slot B actually are.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Mon, 12 Aug 2013 21:06:29 +0100 [thread overview]
Message-ID: <20130812200628.GG23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAFEAcA97PuORg920f-A_8rvCgBq=k5Y=0W6m2Nv8nnzjY19Utg@mail.gmail.com>
On Mon, Aug 12, 2013 at 06:33:28PM +0100, Peter Maydell wrote:
> /* Slot to IRQ mapping for RealView EB and PB1176 backplane
> * name slot IntA IntB IntC IntD
> * A 31 IRQ50 IRQ51 IRQ48 IRQ49
> * B 30 IRQ49 IRQ50 IRQ51 IRQ48
> * C 29 IRQ48 IRQ49 IRQ50 IRQ51
> * Slot C is for the host bridge; A and B the peripherals.
> * Our output irqs 0..3 correspond to the baseboard's 48..51.
> */
>
> ie IRQ48 == board's PCI0 == slot C connector A6 (IntA) == PCI_nINTB
> == Slot B connector B8 (IntD) == Slot A connector A7 (IntC).
>
> and so on round.
>
> The 926's routing is one extra round of swizzling because the
> board itself connects FPGA P_nINTA to its edge connector's
> INTB (B7) pin rather than INTA (A6) as the EB/1176 do.
> (This isn't even hinted at in the documentation, you need to
> either experiment or look at the 926 board schematic.)
Okay, so the above just adds to the confusion, because you appear to be
mistaking "slot" for the AD signal which the IDSEL pin is connected to.
As I'm seeing a report of a card appearing in slot 0x0d at the top of
this thread, this doesn't match your numbering above. So, is slot
0x0d slot A or slot B?
If we assume that slot A is indeed has IDSEL connected to AD31, then
that surely makes it slot 20 (AD11 + 20 = 31) and slot B = 19. So
why do we apparantly have a card in a non-existent slot at 13?
Now, it looks to me like we have the rotation in the right direction,
it's just a matter of ensuring that we have the right starting point.
That's where we need to know what slot number Linux believes slot A
and slot B actually are.
next prev parent reply other threads:[~2013-08-12 20:06 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 15:54 SCSI bus failures with qemu-arm in kernel 3.8+ Guenter Roeck
2013-08-11 15:54 ` Guenter Roeck
2013-08-11 22:04 ` Russell King - ARM Linux
2013-08-11 22:04 ` Russell King - ARM Linux
2013-08-12 0:40 ` Guenter Roeck
2013-08-12 0:40 ` Guenter Roeck
2013-08-12 0:40 ` [Qemu-devel] " Guenter Roeck
2013-08-12 16:24 ` Peter Maydell
2013-08-12 16:24 ` Peter Maydell
2013-08-12 16:24 ` Peter Maydell
2013-08-12 16:45 ` Russell King - ARM Linux
2013-08-12 16:45 ` Russell King - ARM Linux
2013-08-12 16:45 ` Russell King - ARM Linux
2013-08-12 17:33 ` Peter Maydell
2013-08-12 17:33 ` Peter Maydell
2013-08-12 17:33 ` Peter Maydell
2013-08-12 20:06 ` Russell King - ARM Linux [this message]
2013-08-12 20:06 ` Russell King - ARM Linux
2013-08-12 20:06 ` Russell King - ARM Linux
2013-08-12 20:49 ` Peter Maydell
2013-08-12 20:49 ` Peter Maydell
2013-08-12 20:49 ` Peter Maydell
2013-08-12 21:21 ` Russell King - ARM Linux
2013-08-12 21:21 ` Russell King - ARM Linux
2013-08-12 21:21 ` Russell King - ARM Linux
2013-08-12 21:36 ` Peter Maydell
2013-08-12 21:36 ` Peter Maydell
2013-08-12 21:36 ` Peter Maydell
2013-08-12 22:12 ` Russell King - ARM Linux
2013-08-12 22:12 ` Russell King - ARM Linux
2013-08-12 22:12 ` Russell King - ARM Linux
2013-08-12 22:48 ` Guenter Roeck
2013-08-12 22:48 ` Guenter Roeck
2013-08-12 22:48 ` Guenter Roeck
2013-08-12 23:04 ` Guenter Roeck
2013-08-12 23:04 ` Guenter Roeck
2013-08-12 23:04 ` Guenter Roeck
2013-08-14 10:33 ` Russell King - ARM Linux
2013-08-14 10:33 ` Russell King - ARM Linux
2013-08-14 10:33 ` Russell King - ARM Linux
2013-08-14 12:44 ` Peter Maydell
2013-08-14 12:44 ` Peter Maydell
2013-08-14 12:44 ` Peter Maydell
2013-08-14 12:49 ` Russell King - ARM Linux
2013-08-14 12:49 ` Russell King - ARM Linux
2013-08-14 12:49 ` Russell King - ARM Linux
2013-08-14 12:56 ` Peter Maydell
2013-08-14 12:56 ` Peter Maydell
2013-08-14 12:56 ` Peter Maydell
2013-08-14 14:41 ` Guenter Roeck
2013-08-14 14:41 ` Guenter Roeck
2013-08-14 14:41 ` Guenter Roeck
2013-08-14 15:26 ` [Qemu-devel] memory reads and writes Herbei Dacian
2013-08-12 17:48 ` [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ Peter Maydell
2013-08-12 17:48 ` Peter Maydell
2013-08-12 17:48 ` Peter Maydell
2013-08-13 8:37 ` Rob Landley
2013-08-13 8:37 ` Rob Landley
2013-08-13 8:37 ` Rob Landley
2013-08-13 9:12 ` Peter Maydell
2013-08-13 9:12 ` Peter Maydell
2013-08-13 9:12 ` Peter Maydell
2013-08-13 11:30 ` Russell King - ARM Linux
2013-08-13 11:30 ` Russell King - ARM Linux
2013-08-13 11:30 ` Russell King - ARM Linux
2013-08-13 3:40 ` Guenter Roeck
2013-08-13 3:40 ` Guenter Roeck
2013-08-13 3:40 ` Guenter Roeck
2013-08-15 16:45 ` Peter Maydell
2013-08-15 16:45 ` Peter Maydell
2013-08-15 16:45 ` Peter Maydell
2013-08-15 17:54 ` Guenter Roeck
2013-08-15 17:54 ` Guenter Roeck
2013-08-15 17:54 ` Guenter Roeck
2013-08-15 18:05 ` Peter Maydell
2013-08-15 18:05 ` Peter Maydell
2013-08-15 18:05 ` Peter Maydell
2013-08-15 18:39 ` Guenter Roeck
2013-08-15 18:39 ` Guenter Roeck
2013-08-15 18:39 ` Guenter Roeck
2013-08-15 20:50 ` Guenter Roeck
2013-08-15 20:50 ` Guenter Roeck
2013-08-15 20:50 ` Guenter Roeck
2013-08-15 21:49 ` Peter Maydell
2013-08-15 21:49 ` Peter Maydell
2013-08-15 21:49 ` Peter Maydell
2013-08-15 22:18 ` Guenter Roeck
2013-08-15 22:18 ` Guenter Roeck
2013-08-15 22:18 ` Guenter Roeck
2013-08-15 22:23 ` Peter Maydell
2013-08-15 22:23 ` Peter Maydell
2013-08-15 22:23 ` Peter Maydell
2013-08-15 23:25 ` Guenter Roeck
2013-08-15 23:25 ` Guenter Roeck
2013-08-15 23:25 ` Guenter Roeck
2013-08-19 15:26 ` Guenter Roeck
2013-08-19 15:26 ` Guenter Roeck
2013-08-19 15:26 ` Guenter Roeck
2013-08-12 19:02 ` Paul Gortmaker
2013-08-12 19:02 ` Paul Gortmaker
2013-08-12 19:02 ` [Qemu-devel] " Paul Gortmaker
2013-08-12 20:58 ` Peter Maydell
2013-08-12 20:58 ` Peter Maydell
2013-08-12 20:58 ` [Qemu-devel] " Peter Maydell
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=20130812200628.GG23006@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd.bergmann@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=paul.gortmaker@windriver.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.