mvme2600 netdemo: "

[Till Straumann]

rtwas wrote:

> Hello,
>
> Till Straumann wrote:
>
>> I believe it should work.
>>
>> You only need a interrupt routing table to correct
>> mistakes of the firmware. 
>
>
> Is it assumed that the end user (me) should understand how to do this?

No.

>
>> Ideally, the firmware should
>> initialize/configure all PCI devices. Usually, firmwares
>> have problems with PCI-PCI bridges and configuring
>> devices behind them  (read PCI-extenders, PMC
>> cards with bridges, ...). That's when the routing table
>> helps (or in the unlikely case that the firmware screws
>> up configuring on-board devices).
>
>
> The reason I'm asserting that interrupts are to blame is based on 
> Joel's post to
> that effect. So if that is not really the issue I'm back to square one.
>
Not really. You learned that you have to use the relevant 'driver attach'
function in the network config. table.

Then, Joel (sorry, Joel) sent out the frightening (but untrue) message
that without an irq routing/mapping table nothing will work.
I believe it should work and if it doesn't we'll find out why...

>
> Are you able to help with this further? Should I send you my build 
> files and dumps?

Yes, please. Same as last time.

HTH
T.

>
>
> Thanks.
>
> Robert W.
>