All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Aizenstros" <daizenstros@quicklogic.com>
To: <coldwell@frank.harvard.edu>, <kevink@mips.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: NCD900 port?
Date: Fri, 25 Apr 2003 06:56:14 -0700	[thread overview]
Message-ID: <sea8dc20.086@quicklogic.com> (raw)

Hello Chip,

The V320USC is fully documented and manuals are
available if you want them. The QuickLogic web site
is a bit out of date with respect to the Linux support.
I am tracking the linux-mips CVS tree and I can send
you a patch sometime next week. However, the patch will
be for our Hurricane board and so you will have to make
changes to support the NCD device.

Can you provide any information about the bootloader?
Does it support loading of ELF images?

Also, do you know what endian the machine is using.
The Linux port is mostly tested little endian and
may need some work to get big endian going.

Regards,

Dan Aizenstros

>>> Chip Coldwell <coldwell@frank.harvard.edu> 04/24/03 15:51 PM >>>
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"?

There's also two RS-232 line drivers/receivers, MAX3185 made by Maxim
(now part of Dallas Semiconductor) and some nearby Samsung parts that
I suppose are probably UARTs (this thing has two serial ports).  I
would guess that getting something to come out on a serial console is
going to be my first step.

Digitally signed images and bootloaders that enforce them sounds
particularly nasty.  That's a show topper for me, if it turns out to
be that way.

Chip

-- 
Charles  M. "Chip" Coldwell
"Turn on, log in, tune out"

WARNING: multiple messages have this Message-ID (diff)
From: "Dan Aizenstros" <daizenstros@quicklogic.com>
To: coldwell@frank.harvard.edu, kevink@mips.com
Cc: linux-mips@linux-mips.org
Subject: Re: NCD900 port?
Date: Fri, 25 Apr 2003 06:56:14 -0700	[thread overview]
Message-ID: <sea8dc20.086@quicklogic.com> (raw)
Message-ID: <20030425135614.GK_Djsol1s1RqorOKvTzh6vahDE4jKcnEgKmWUMIXfE@z> (raw)

Hello Chip,

The V320USC is fully documented and manuals are
available if you want them. The QuickLogic web site
is a bit out of date with respect to the Linux support.
I am tracking the linux-mips CVS tree and I can send
you a patch sometime next week. However, the patch will
be for our Hurricane board and so you will have to make
changes to support the NCD device.

Can you provide any information about the bootloader?
Does it support loading of ELF images?

Also, do you know what endian the machine is using.
The Linux port is mostly tested little endian and
may need some work to get big endian going.

Regards,

Dan Aizenstros

>>> Chip Coldwell <coldwell@frank.harvard.edu> 04/24/03 15:51 PM >>>
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"?

There's also two RS-232 line drivers/receivers, MAX3185 made by Maxim
(now part of Dallas Semiconductor) and some nearby Samsung parts that
I suppose are probably UARTs (this thing has two serial ports).  I
would guess that getting something to come out on a serial console is
going to be my first step.

Digitally signed images and bootloaders that enforce them sounds
particularly nasty.  That's a show topper for me, if it turns out to
be that way.

Chip

-- 
Charles  M. "Chip" Coldwell
"Turn on, log in, tune out"

             reply	other threads:[~2003-04-25 13:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 13:56 Dan Aizenstros [this message]
2003-04-25 13:56 ` NCD900 port? Dan Aizenstros
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 15:04 Dan Aizenstros
2003-04-25 15:04 ` 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-24 20:20 Chip Coldwell
2003-04-24 20:57 ` Alan Cox
2003-04-24 21:51 ` Kevin D. Kissell
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
2003-04-25  6:53         ` Kevin D. Kissell
2003-04-25  8:39         ` Sander Wichers
2003-04-25  8:39           ` Sander Wichers
2003-04-25  1:46   ` Brad Parker
2003-04-25  2:17     ` Chip Coldwell
2003-04-27 20:01       ` Brad Parker

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=sea8dc20.086@quicklogic.com \
    --to=daizenstros@quicklogic.com \
    --cc=coldwell@frank.harvard.edu \
    --cc=kevink@mips.com \
    --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.