AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071109185024.047e42f9@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Nov 2007 18:50:43 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Brian Stark <brian.stark@onstor.com>
Cc: Maxim Kozlovsky <maxim.kozlovsky@onstor.com>
Subject: BMFPGA address clarification
Message-ID: <20071109185043.716f80e5@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Howdy pards,

So, I'm holding a doc that Brian sent a little while ago that lists the
BMFPGA at phys 0x1f40.0000, but Max showed me a document that listed
the address as 0xf8.1f40.0000, ie., indicating that it was in the PCI
bus address space.  I know that some FPGA is visible on the PCI bus
scan, but I guess in my mind it was not the BMFPGA.

Which is it?  Or is it a little from column A and a little from column
B?  Is that chunklet of PCI space mapped into the KSEG1 space some way?
It makes a big difference to how much code we have to change to get the
chassisd working on cougar.

Cheers,

a
