All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Jonathan Day <imipak@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Broadcom SB1 query
Date: Fri, 1 Sep 2006 22:32:23 +0100	[thread overview]
Message-ID: <20060901213223.GA24995@networkno.de> (raw)
In-Reply-To: <20060901204131.42144.qmail@web31512.mail.mud.yahoo.com>

Jonathan Day wrote:
> --- Thiemo Seufer <ths@networkno.de> wrote:
> 
> > Jonathan Day wrote:
> > > Hi,
> > > 
> > > Can anyone verify that the current kernel in
> > > linux-mips git archive will work on a Broadcom
> > 1250
> > > (SB1), specifically the "Swarm" or the "Sentosa"
> > > flavours of the BCM91250.
> > 
> > A 2.6.18-rc4 from a one week old git checkout works
> > fine on a SWARM
> > here, booted via tftp. The same kernel fails to boot
> > on another
> > SWARM board from the onboard IDE, I guess the
> > swarm-ide is currently
> > broken.
> 
> That might explain it. I've included the output from
> the console at the end of this message, so you can
> take a squint at it and see if that confirms it.

Hm, no. It hangs way too early for that. Looks like it dies on the
first interrupts.

[snip]
> > Current Debian unstable works for me.
> > 
> 
> Well, my machine's already unstable, so I guess Debian
> can't hurt! :) I didn't know they had a big-endian
> 64-bit build, though. I'll have to look that up.

Only the kernel is 64 bit, userland is still 32 bit. This should at
least help to verify the hardware.


Thiemo

      reply	other threads:[~2006-09-01 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 16:38 Broadcom SB1 query Jonathan Day
2006-09-01 17:37 ` Thiemo Seufer
2006-09-01 20:41   ` Jonathan Day
2006-09-01 21:32     ` Thiemo Seufer [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=20060901213223.GA24995@networkno.de \
    --to=ths@networkno.de \
    --cc=imipak@yahoo.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.