Board based on MPC7447 and MV64462

Board based on MPC7447 and MV64462

[Ashish Bijlani]

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

Hi,

I've added platform support for a board based on MPC7447A and MV64462
Marvell Discovery III system controller. I modified code for Katana to make
it work for this board. The ethernet and serial are working fine but I don't
see anything in "lspci" output. Also I don't see timer in "cat
/proc/interrupts". Does anybody have any idea on this? Thanks in advance.

Thanks,
Ashish

[-- Attachment #2: Type: text/html, Size: 436 bytes --]

Re: Board based on MPC7447 and MV64462

[Mark A. Greer]

On Thu, Oct 27, 2005 at 06:47:29PM +0530, Ashish Bijlani wrote:
> Hi,
> 
> I've added platform support for a board based on MPC7447A and MV64462
> Marvell Discovery III system controller. I modified code for Katana to make
> it work for this board. The ethernet and serial are working fine but I don't
> see anything in "lspci" output.

Do you have any pci devices?  If not, then that's to be expected.
If you do, then you have something messed up in your code and they
aren't being found.

> Also I don't see timer in "cat /proc/interrupts".

Neither do I...  :)

Mark

Re: Board based on MPC7447 and MV64462

[Sven Luther]

On Thu, Oct 27, 2005 at 11:17:51AM -0700, Mark A. Greer wrote:
> On Thu, Oct 27, 2005 at 06:47:29PM +0530, Ashish Bijlani wrote:
> > Hi,
> > 
> > I've added platform support for a board based on MPC7447A and MV64462
> > Marvell Discovery III system controller. I modified code for Katana to make
> > it work for this board. The ethernet and serial are working fine but I don't
> > see anything in "lspci" output.
> 
> Do you have any pci devices?  If not, then that's to be expected.
> If you do, then you have something messed up in your code and they
> aren't being found.

They should at least shgow the northbridge pci ids, no ? 

Friendly,

Sven Luther

Re: Board based on MPC7447 and MV64462

[Mark A. Greer]

On Thu, Oct 27, 2005 at 08:49:21PM +0200, Sven Luther wrote:
> On Thu, Oct 27, 2005 at 11:17:51AM -0700, Mark A. Greer wrote:
> > On Thu, Oct 27, 2005 at 06:47:29PM +0530, Ashish Bijlani wrote:
> > > Hi,
> > > 
> > > I've added platform support for a board based on MPC7447A and MV64462
> > > Marvell Discovery III system controller. I modified code for Katana to make
> > > it work for this board. The ethernet and serial are working fine but I don't
> > > see anything in "lspci" output.
> > 
> > Do you have any pci devices?  If not, then that's to be expected.
> > If you do, then you have something messed up in your code and they
> > aren't being found.
> 
> They should at least shgow the northbridge pci ids, no ? 

No b/c the regs for the bridge are not pci compliant so the bridge is
"excluded" or hidden from the generic pci code (which is where lspci
gets its info from).  If it wasn't, the generic pci code would get
confused as would the bridge.

Mark

Re: Board based on MPC7447 and MV64462

[Mark A. Greer]

On Thu, Oct 27, 2005 at 01:04:47PM -0700, Mark A. Greer wrote:
> On Thu, Oct 27, 2005 at 08:49:21PM +0200, Sven Luther wrote:
> > On Thu, Oct 27, 2005 at 11:17:51AM -0700, Mark A. Greer wrote:
> > > On Thu, Oct 27, 2005 at 06:47:29PM +0530, Ashish Bijlani wrote:
> > > > Hi,
> > > > 
> > > > I've added platform support for a board based on MPC7447A and MV64462
> > > > Marvell Discovery III system controller. I modified code for Katana to make
> > > > it work for this board. The ethernet and serial are working fine but I don't
> > > > see anything in "lspci" output.
> > > 
> > > Do you have any pci devices?  If not, then that's to be expected.
> > > If you do, then you have something messed up in your code and they
> > > aren't being found.
> > 
> > They should at least shgow the northbridge pci ids, no ? 
> 
> No b/c the regs for the bridge are not pci compliant so the bridge is
> "excluded" or hidden from the generic pci code (which is where lspci
> gets its info from).  If it wasn't, the generic pci code would get
> confused as would the bridge.

Actually, I guess this is more to hide the bridge from the pci_auto when
it walks the pci buses.  If the pci resources are already allocated
correctly (as in pegasos?) it may not confuse the generic pci code.
Even if it doesn't get confused, its by luck.  The bridge's pci regs
are NOT pci compliant and, IMHO, its iffy to assume that things woun't
get messed up.

Mark

Re: Board based on MPC7447 and MV64462

[Sven Luther]

On Thu, Oct 27, 2005 at 01:04:47PM -0700, Mark A. Greer wrote:
> On Thu, Oct 27, 2005 at 08:49:21PM +0200, Sven Luther wrote:
> > On Thu, Oct 27, 2005 at 11:17:51AM -0700, Mark A. Greer wrote:
> > > On Thu, Oct 27, 2005 at 06:47:29PM +0530, Ashish Bijlani wrote:
> > > > Hi,
> > > > 
> > > > I've added platform support for a board based on MPC7447A and MV64462
> > > > Marvell Discovery III system controller. I modified code for Katana to make
> > > > it work for this board. The ethernet and serial are working fine but I don't
> > > > see anything in "lspci" output.
> > > 
> > > Do you have any pci devices?  If not, then that's to be expected.
> > > If you do, then you have something messed up in your code and they
> > > aren't being found.
> > 
> > They should at least shgow the northbridge pci ids, no ? 
> 
> No b/c the regs for the bridge are not pci compliant so the bridge is
> "excluded" or hidden from the generic pci code (which is where lspci
> gets its info from).  If it wasn't, the generic pci code would get
> confused as would the bridge.

The pegasos OF allows access to the pci config area through rtas, and those
call filter out any dangerous accesses. And since you didn't know about rtas,
i will explain for others who may be in other cases.

RTAS is a OpenFirmware/CHRP extension (RunTimeAbstraction..., not sure about
the S), which provides a set of methods which will run even when linux has
taken over and overwritten the firmware, providing stuff like halt/reset,
pci-read|write-config, nvram-fetch|store, clock access functions, ...

Friendly,

Sven Luther

Re: Board based on MPC7447 and MV64462

[Sven Luther]

On Thu, Oct 27, 2005 at 01:11:05PM -0700, Mark A. Greer wrote:
> Actually, I guess this is more to hide the bridge from the pci_auto when
> it walks the pci buses.  If the pci resources are already allocated
> correctly (as in pegasos?) it may not confuse the generic pci code.
> Even if it doesn't get confused, its by luck.  The bridge's pci regs
> are NOT pci compliant and, IMHO, its iffy to assume that things woun't
> get messed up.

As said, the pci access rtas functions will stop any access to the non-pci
compliant regs.

Friendly,

Sven Luther

Re: Board based on MPC7447 and MV64462

[Mark A. Greer]

All,

For the record, Sven, Matt Porter, and I talked about this some more on
IRC.  I think we agreed that the best solution would be to register a
pci quirk for the bad regs and no longer hide the bridge.

Anyone think that's a bad idea?

Mark