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 18:37:30 +0100 [thread overview]
Message-ID: <20060901173730.GC4893@networkno.de> (raw)
In-Reply-To: <20060901163839.49311.qmail@web31504.mail.mud.yahoo.com>
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.
> I have not been able to get anything more recent than
> a 2.6.17 kernel to compile and boot, the 2.6.18-rc
> kernels seem to randomly either lock up or reboot very
> early on in the kernel initialization. However, I am
> undecided whether it's a kernel issue,
I presume you know that PCI devices and more than 1 GB of RAM don't
work under Linux.
> a hardware
> issue (we've had nothing but trouble from these
> boards) or a toolchain issue (versions: gcc 4.1.1,
> libc 2.4, binutils 2.17.50) as I've found a few large
> projects that should compile just fine are blowing the
> compiler up.
Hm, libc 2.4 means NPTL, that's not yet widely deployed and could well
account for some exciting failures.
> If someone can post (or e-mail me direct) on what the
> latest combination of kernel and toolchain that works
> on the Swarm is, I would greatly appreciate it. This
> problem is driving me nuts. (Ok, more nuts than
> usual.)
Current Debian unstable works for me.
Thiemo
next prev parent reply other threads:[~2006-09-01 17:39 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 [this message]
2006-09-01 20:41 ` Jonathan Day
2006-09-01 21:32 ` Thiemo Seufer
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=20060901173730.GC4893@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox