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

[Pete P. <pp...@mv...>]

Paul Mundt wrote:

>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.
>>>
>>Not yet. I tested it on the ev96100 and basically the same code is 
>>running on the ddb5477 board. I've got an ITE board sitting here in my 
>>home right now. I suspect some setup changes might have to be made to 
>>the ite code, but the pci code *should* just work. Matt has done a great 
>>job there, and it's been tested on pretty complex PPC CPCI systems (like 
>>I said though, we modified it slightly for mips, so I'm sure we'll 
>>evolve this over time).  The ITE can be a bit tricky because it's got 
>>discountinuous pci memory space regions.  Two of those regions are 64MB 
>>each; the others are smaller.  Globespan, for example, is using both 
>>64MB regions for their custom mpeg chip, so no other devices can be 
>>assigned from those regions.  But I don't think I'll worry about that on 
>>the ITE board.
>>
>I don't think that should be too much of an issue on the ITE board. Worst case
>scenario is that a few board specific fixups need to be existant in the code.
>
>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.
>
That's a very custom board anyway.

>I'd test it now, except I'm not at work, and the ATX power supply I have hooked
>up to the board doesn't like working properly with the NPS. Damned ATX design.
>
>I'll give it a try tomorrow and let you know my findings.
>

I might give it a shot tonight. We'll see. I'll let you know if I do.

>Next I need to include this pci support in the Alchemy board. The 
>problem is that right now I'm supposed to turn my attention to generic 
>mips kernel problems ...
>
>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?
>

Steve L. and I.

>BTW, what's up with the 2.4.5 bootp support? The code doesn't appear to 
>get called unless you specify "ip=<ipaddress>" on the kernel command line.
>
>That's a known 2.4.5 bug, it was fixed in Alan's tree for awhile.. I believe 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.
>
OK, thanks.

Pete