linux-mips
[Top] [All Lists]

Re: Nile 4

To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Nile 4
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 10 Jul 2003 00:45:50 +0200
Cc: Brian Murphy <brm@murphy.dk>, Linux/MIPS Development <linux-mips@linux-mips.org>
In-reply-to: <Pine.GSO.4.21.0307090953320.18825-100000@vervain.sonytel.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030705225445.GA26533@linux-mips.org> <Pine.GSO.4.21.0307090953320.18825-100000@vervain.sonytel.be>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Wed, Jul 09, 2003 at 09:58:08AM +0200, Geert Uytterhoeven wrote:

> > Well, I was wondering because the code in arch/mips/pci/ops-nile4.c which
> > was extraced from the lasat code is completly different from
> > ddb5xxx/ddb5074/pci_ops.c, so it's hard to extract the commonc code into
> > a shared file.
> 
> If you know the chip, they are actually quite similar :-)
> 
> The differences between the Lasat and the DDB code are these:
>   - The Lasat code checks the PCI error registers to detect the presence of 
> PCI
>     devices, while the DDB code doesn't,
>   - The Lasat code is limited to 8 PCI devices on bus 0, while the DDB code
>     uses a different access scheme to access the extra devices,
>   - The DDB code uses abstraction functions to access the Nile 4 registers,
>     while the Lasat code accesses the registers directly.

Time to cleanup that mess also then.

Does anybody still care about the DDB5074?  I was just told somebody tried
it and it didn't boot into userspace ...

  Ralf

<Prev in Thread] Current Thread [Next in Thread>