All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@mvista.com>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: "H . J . Lu" <hjl@lucon.org>, linux-mips@oss.sgi.com
Subject: Re: I am looking for a mips machine
Date: 24 Oct 2001 14:00:15 -0700	[thread overview]
Message-ID: <1003957215.26240.29.camel@zeus> (raw)
In-Reply-To: <20011024121944.B6520@lucon.org>
In-Reply-To: <Pine.SGI.4.33.0110241637200.11721-100000@thor.tetracon-eng.net>

On Wed, 2001-10-24 at 13:42, J. Scott Kasten wrote:
> 
> My general impression is that your looking for a "FAST" board, and a
> little endian board make for mutually exclusive requirements.  Not that
> little endian couldn't be fast, but just about every piece of hardware
> I've seen running little endian has used one of the lesser mips chips in
> it where they've cut corners multiplexing address and data over the same
> pins and so forth.  Someone correct me if I'm wrong, but of all the ones
> I've looked at, the little endian boards had the less capable hardware to
> boot.  I think that's because the market was being driven by these little
> Win CE things, and CE only supports little endian.

Well, not quite. Linux supports LE too but the choice of LE mips desktop
systems is limited.

The fastest LE cpu/board I've worked with is the Alchemy Au1000 part
running at 396MHz. The board doesn't have and IDE or SCSI controller
though. However, it has pcmcia and we've added support for their pcmcia
controller, so I was able to use a Hitachi 2GB pcmcia ata card (looks
like the IBM Microdrive).  That might be one option for reasonably fast
native compiles.

Pete

> 
> On Wed, 24 Oct 2001, H . J . Lu wrote:
> 
> > On Wed, Oct 24, 2001 at 11:19:27AM -0700, James Simmons wrote:
> > >
> > > I use a Cobalt Qube for alot of my developement. It works fine. I know it
> > > is not in Ralph's tree yet but I plan to send him my work soon.
> >
> > I think Cobalt Qube is slow and is hard to expand the memory. I need at
> > least 128MB RAM. Also the current mips kernel doesn't support it.
> >
> >
> > H.J.
> >
> 

  reply	other threads:[~2001-10-24 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 15:03 I am looking for a mips machine H . J . Lu
2001-10-24 18:19 ` James Simmons
2001-10-24 19:19   ` H . J . Lu
2001-10-24 20:16     ` James Simmons
2001-10-24 20:24       ` H . J . Lu
2001-10-24 20:28         ` James Simmons
2001-10-24 20:30         ` Taco IJsselmuiden
2001-10-24 20:42     ` J. Scott Kasten
2001-10-24 20:42       ` J. Scott Kasten
2001-10-24 21:00       ` Pete Popov [this message]
2001-10-25  7:57       ` Geert Uytterhoeven
2001-10-24 21:24 ` Jun Sun
2001-10-25  8:28 ` Carsten Langgaard

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=1003957215.26240.29.camel@zeus \
    --to=ppopov@mvista.com \
    --cc=hjl@lucon.org \
    --cc=jsk@tetracon-eng.net \
    --cc=linux-mips@oss.sgi.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 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.