linux-kernel - Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130812200628.GG23006@n2100.arm.linux.org.uk>
Date:	Mon, 12 Aug 2013 21:06:29 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Peter Maydell <peter.maydell@...aro.org>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>, qemu-devel@...gnu.org,
	Arnd Bergmann <arnd.bergmann@...aro.org>
Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/