--- Thiemo Seufer <email@example.com> wrote:
> Jonathan Day wrote:
> > Hi,
> > Can anyone verify that the current kernel in
> > linux-mips git archive will work on a Broadcom
> > (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
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.
> > I have not been able to get anything more recent
> > a 2.6.17 kernel to compile and boot, the 2.6.18-rc
> > kernels seem to randomly either lock up or reboot
> > early on in the kernel initialization. However, I
> > 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.
What a peculiar bug! (I don't think that's a
limitation of PCI, but even if it were, Linux' VMM is
more than sophisticated enough to map any assortment
of pages that totalled a gigabyte or less into a blob
such that buggy drivers or hardware only saw what
memory they could handle, regardless of what physical
Regardless, the cards are all 1 Gb.
> > 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
> > projects that should compile just fine are blowing
> > compiler up.
> Hm, libc 2.4 means NPTL, that's not yet widely
> deployed and could well
> account for some exciting failures.
Yeah. I've tried building from source as much as
possible, but merely the lack of deployment opens up
all kinds of possibilites of me hitting bugs others
haven't seen, or don't see often enough to trace. I
run some weird stuff on the Broadcom.
> > If someone can post (or e-mail me direct) on what
> > latest combination of kernel and toolchain that
> > on the Swarm is, I would greatly appreciate it.
> > problem is driving me nuts. (Ok, more nuts than
> > usual.)
> 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.
Anyway, here is a logfile when trying to boot the
swarm. As soon as it passes the high precision timer
code, it jumps back into CFE.
Starting program at 0x80633000
Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2)
Board type: SiByte BCM91250A (SWARM)
[17179569.184000] Linux version
gb895b669-dirty (firstname.lastname@example.org) (gcc version 4.1.1)
PREEMPT Fri Sep 1 09:16:18 UTC 2006
[17179569.184000] CPU revision is: 01040102
[17179569.184000] FPU revision is: 000f0102
[17179569.184000] swarm setup: M41T81 RTC detected.
[17179569.184000] This kernel optimized for board runs
[17179569.184000] Determined physical RAM map:
[17179569.184000] memory: 000000000fe99e00 @
[17179569.184000] memory: 000000001ffffe00 @
[17179569.184000] memory: 000000000ffffe00 @
[17179569.184000] memory: 000000003ffffe00 @
[17179569.184000] Detected 1 available secondary
[17179569.184000] Built 1 zonelists. Total pages:
[17179569.184000] Kernel command line: ip=any rw
[17179569.184000] Primary instruction cache 32kB,
4-way, linesize 32
[17179569.184000] Primary data cache 32kB, 4-way,
linesize 32 bytes.
[17179569.184000] Synthesized TLB refill handler (39
[17179569.184000] Synthesized TLB load handler
[17179569.184000] Synthesized TLB store handler
[17179569.184000] Synthesized TLB modify handler
[17179569.184000] PID hash table entries: 4096 (order:
12, 32768 bytes)
[17179569.184000] Using 512.000 MHz high precision
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around