From: "Kevin D. Kissell" <kevink@mips.com>
To: "Chip Coldwell" <coldwell@frank.harvard.edu>
Cc: <linux-mips@linux-mips.org>
Subject: Re: NCD900 port?
Date: Fri, 25 Apr 2003 08:53:02 +0200 [thread overview]
Message-ID: <004201c30af7$524fb0a0$10eca8c0@grendel> (raw)
In-Reply-To: Pine.LNX.4.44.0304241839110.19067-100000@frank.harvard.edu
> On Thu, 24 Apr 2003, Chip Coldwell wrote:
>
> > On Thu, 24 Apr 2003, Kevin D. Kissell wrote:
> > >
> > > What PCI bridge is being used? Galileo?
> >
> > Good question. Short answer: I don't know. I'll pry off the hood
> > and take a peek at what's on the board, unless this is something that
> > shares a die with the CPU.
>
> It was easy to identify once I took off the cover. The PCI bridge is
> made by V3 Semiconductor (now a part of QuickLogic?), part number
> V32OUSC-75LP (Rev. B1):
>
> http://www.quicklogic.com/home.asp?PageID=235&sMenuID=126
>
> Is this the one called "Galileo"?
No, Galileo is/was a different company. So you may not be able
to recycle as much existing code as you might have otherwise, but
at least you've got some documentation for it.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Chip Coldwell <coldwell@frank.harvard.edu>
Cc: linux-mips@linux-mips.org
Subject: Re: NCD900 port?
Date: Fri, 25 Apr 2003 08:53:02 +0200 [thread overview]
Message-ID: <004201c30af7$524fb0a0$10eca8c0@grendel> (raw)
Message-ID: <20030425065302.QgCEpm193h60gr2YXk4mMP2zTKoAlOHtMYCCtZhCqIs@z> (raw)
In-Reply-To: Pine.LNX.4.44.0304241839110.19067-100000@frank.harvard.edu
> On Thu, 24 Apr 2003, Chip Coldwell wrote:
>
> > On Thu, 24 Apr 2003, Kevin D. Kissell wrote:
> > >
> > > What PCI bridge is being used? Galileo?
> >
> > Good question. Short answer: I don't know. I'll pry off the hood
> > and take a peek at what's on the board, unless this is something that
> > shares a die with the CPU.
>
> It was easy to identify once I took off the cover. The PCI bridge is
> made by V3 Semiconductor (now a part of QuickLogic?), part number
> V32OUSC-75LP (Rev. B1):
>
> http://www.quicklogic.com/home.asp?PageID=235&sMenuID=126
>
> Is this the one called "Galileo"?
No, Galileo is/was a different company. So you may not be able
to recycle as much existing code as you might have otherwise, but
at least you've got some documentation for it.
Kevin K.
next prev parent reply other threads:[~2003-04-25 6:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 20:20 NCD900 port? Chip Coldwell
2003-04-24 20:57 ` Alan Cox
2003-04-24 21:51 ` Kevin D. Kissell
2003-04-24 21:48 ` Chip Coldwell
2003-04-24 22:48 ` Chip Coldwell
2003-04-25 6:53 ` Kevin D. Kissell [this message]
2003-04-25 6:53 ` Kevin D. Kissell
2003-04-25 8:39 ` Sander Wichers
2003-04-25 8:39 ` Sander Wichers
2003-04-24 21:51 ` Kevin D. Kissell
2003-04-25 1:46 ` Brad Parker
2003-04-25 2:17 ` Chip Coldwell
2003-04-27 20:01 ` Brad Parker
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 13:56 Dan Aizenstros
2003-04-25 13:56 ` Dan Aizenstros
[not found] <sea8dc20.085@quicklogic.com>
2003-04-25 14:18 ` Chip Coldwell
2003-04-25 14:18 ` Chip Coldwell
2003-04-27 20:08 ` Brad Parker
2003-04-25 15:04 Dan Aizenstros
2003-04-25 15:04 ` Dan Aizenstros
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='004201c30af7$524fb0a0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=coldwell@frank.harvard.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox