From: "Mitch Lichtenberg" <mpl@broadcom.com>
To: "Ken Giusti" <manwithastinkydog@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: running 2.6 on swarm pass1
Date: Mon, 17 May 2004 11:18:05 -0700 [thread overview]
Message-ID: <40A901DD.80308@broadcom.com> (raw)
In-Reply-To: <20040517150631.13795.qmail@web13301.mail.yahoo.com>
Ken,
Pass1 BCM1250's have enough problems that it's no surprise
that things don't work anymore. Most of the workarounds
to CPU core issues are deliberately not checked into the external
(linux-mips) tree, and some require some nasty toolchain
hacks (for example, taking exceptions on the instruction
in a branch delay slot is perilous).
I don't know how you got your SWARM, but you might want to
press for getting a new one. No pass1's were ever shipped
in volume, so it would be best to NOT support it.
/Mitch.
Ken Giusti wrote:
> Hi,
>
> I've got a swarm board with a pass1 sibyte sb1250.
> Here's the relevant system info from the boot up
> console:
>
<<snip>>
next prev parent reply other threads:[~2004-05-17 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 15:06 running 2.6 on swarm pass1 Ken Giusti
2004-05-17 18:18 ` Mitch Lichtenberg [this message]
2004-05-18 0:16 ` Ralf Baechle
2004-05-18 16:57 ` Ken Giusti
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=40A901DD.80308@broadcom.com \
--to=mpl@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=manwithastinkydog@yahoo.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