mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: David Woodhouse <dwmw2@infradead.org>, Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: netwinder or ARM build platform
Date: Sat, 11 Sep 2004 10:52:15 +0200	[thread overview]
Message-ID: <20040911085215.GD13173@xi.wantstofly.org> (raw)
In-Reply-To: <1094772143.9144.42.camel@imladris.demon.co.uk>

On Fri, Sep 10, 2004 at 12:22:23AM +0100, David Woodhouse wrote:

> > BK found another bad hard drive today, on our netwinder.  The disk is dieing
> > badly unfortunately and I don't have installation media for this beast.
> > I suspect I can go find it but does anyone know of a faster build platform
> > for arm?  Russell uses bk on arms (no kidding, that's amazing) and so we
> > continue to support it but that netwinder is just amazingly slow.  If there
> > is a faster platform we want one.
> 
> TBH I'd suggest cross-building and testing in qemu-arm. Assuming
> qemu-arm is actually working now.

Not quite.  It works okay for simple binaries now, but still craps out
on running bigger apps such as gcc.

I'm using the gumstix (www.gumstix.com) myself for little endian ARM
builds, but they only have 64M RAM and no ethernet or IDE.  For big
endian, I use the Linksys NSLU2, which has only 32M RAM but ethernet
and dual USB (which lets you hook up a disk each.)


--L

  parent reply	other threads:[~2004-09-11  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 17:59 Larry McVoy
2004-09-09 23:22 ` David Woodhouse
2004-09-09 23:38   ` Ben Greear
2004-09-16  9:33     ` Andrew McGregor
2004-09-11  8:52   ` Lennert Buytenhek [this message]
2004-09-10  6:51 ` Andrey Panin
2004-09-11  6:04   ` Brad Campbell

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=20040911085215.GD13173@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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®