From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Raphael Assenat <raph@8d.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add PCI device ID for IT8152 RISC-to-PCI chip
Date: Tue, 13 Feb 2007 16:20:57 +0000 [thread overview]
Message-ID: <20070213162057.GC15227@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070213154728.GM7584@csclub.uwaterloo.ca>
On Tue, Feb 13, 2007 at 10:47:28AM -0500, Lennart Sorensen wrote:
> On Tue, Feb 13, 2007 at 03:30:29PM +0000, Russell King wrote:
> > On Tue, Feb 13, 2007 at 10:16:33AM -0500, Lennart Sorensen wrote:
> > > There doesn't seem to be very many
> > > arm systems with PCI, so it's hard to tell.
> >
> > NetWinder, EBSA285 (which the NetWinder is a derivative of), the N2100,
> > etc are PCI based and are all well proven in the field.
>
> Which PCI controller do they use?
NetWinder and EBSA285 are DC21285 (footbridge). The N2100 is IOP32x
based. As for gluing a PCI bridge to something not designed for PCI
(eg, a PXA255) I can't comment.
> > (I did consider replacing the Promise UDMA card, but the IT821x card
> > I bought to replace it didn't have all the pins on the chip soldered
> > down - to the extent that even a PC couldn't recognise the PCI card.
> > So I'm running on the assumption that the self-repaired Promise UDMA
> > card is all round going to be more reliable than the as yet unproven
> > IT821x card.)
>
> And they shipped a card in that state?
Indeed. :(
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2007-02-13 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 20:14 Raphael Assenat
2007-02-09 21:28 ` Lennart Sorensen
2007-02-13 14:45 ` Raphael Assenat
2007-02-13 15:16 ` Lennart Sorensen
2007-02-13 15:30 ` Russell King
2007-02-13 15:47 ` Lennart Sorensen
2007-02-13 16:20 ` Russell King [this message]
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=20070213162057.GC15227@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=raph@8d.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®