From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Brian Murphy <brm@murphy.dk>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Nile 4
Date: Thu, 10 Jul 2003 00:45:50 +0200 [thread overview]
Message-ID: <20030709224550.GA30793@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0307090953320.18825-100000@vervain.sonytel.be>
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
next prev parent reply other threads:[~2003-07-09 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 13:22 [PATCH 2.4] ndelay typo? Brian Murphy
2003-07-05 13:34 ` Ralf Baechle
2003-07-05 21:16 ` Geert Uytterhoeven
2003-07-05 22:54 ` Ralf Baechle
2003-07-09 7:58 ` Nile 4 (was: Re: [PATCH 2.4] ndelay typo?) Geert Uytterhoeven
2003-07-09 22:45 ` Ralf Baechle [this message]
2003-07-10 7:29 ` Nile 4 Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030709224550.GA30793@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=brm@murphy.dk \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.