Re: [Linux-mips-kernel] mips generic pci code

[Paul M. <pm...@mv...>]

On Thu, Jul 05, 2001 at 06:36:00PM -0700, Pete Popov wrote:
> > Very nice! Speaking of supported boards.. have you had a chance to test=
 it
> > out on the ITE IT8172? If not, I'll give it a try tomorrow and let you =
know
> > my results.
>=20
> Not yet. I tested it on the ev96100 and basically the same code is=20
> running on the ddb5477 board. I've got an ITE board sitting here in my=20
> home right now. I suspect some setup changes might have to be made to=20
> the ite code, but the pci code *should* just work. Matt has done a great=
=20
> job there, and it's been tested on pretty complex PPC CPCI systems (like=
=20
> I said though, we modified it slightly for mips, so I'm sure we'll=20
> evolve this over time).  The ITE can be a bit tricky because it's got=20
> discountinuous pci memory space regions.  Two of those regions are 64MB=
=20
> each; the others are smaller.  Globespan, for example, is using both=20
> 64MB regions for their custom mpeg chip, so no other devices can be=20
> assigned from those regions.  But I don't think I'll worry about that on=
=20
> the ITE board.
>=20
I don't think that should be too much of an issue on the ITE board. Worst c=
ase
scenario is that a few board specific fixups need to be existant in the cod=
e.

The Globespan sounds like it's the bigger nuisance out of the two.. though
watching out for discontinuous regions on the ITE might prove to be somewhat
bothersome.

I'd test it now, except I'm not at work, and the ATX power supply I have ho=
oked
up to the board doesn't like working properly with the NPS. Damned ATX desi=
gn.

I'll give it a try tomorrow and let you know my findings.

> Next I need to include this pci support in the Alchemy board. The=20
> problem is that right now I'm supposed to turn my attention to generic=20
> mips kernel problems ...
>=20
Try submitting it on Perseus and hope somebody fixes it before they realize=
 it's
not specific to the tree.

Who's doing the alchemy work anyways?

> BTW, what's up with the 2.4.5 bootp support? The code doesn't appear to=
=20
> get called unless you specify "ip=3D<ipaddress>" on the kernel command li=
ne.
>=20
That's a known 2.4.5 bug, it was fixed in Alan's tree for awhile.. I believ=
e the
fix is in 2.4.6. It was a rather trivial fix if I recall correctly.. if you=
're
stuck on 2.4.5, you should be able to apply it without any issues.

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.