| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Building the kernel for a Broadcom SB1 |
| From: | Jonathan Day <imipak@yahoo.com> |
| Date: | Wed, 21 Sep 2005 10:24:35 -0700 (PDT) |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Qn9JcmBx6YYmK+5v3Iifb4Qf2VXkBZ8xzHO69XDbrsOd+HHCedWWV/FrkxPp98EvSc40QrcKr4u17DC/0wA8MGncFpFPu9/g/8+mlDbTH8AswwtFPRgq1j2ecV3yl5lJk8aCUhlY2yuRMVRoK3qHy4N6pcdf17TdHZhIr3Yqcig= ; |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
Hi,
Things've been interesting here, of late. I've got the
toolchain to compile natively 64-bit code (with
considerable effort and the instructions from Linux
From Scratch) and I have a working Linux 2.6.12-rc2
kernel with the SB1 patches from the linux-mips
mailing lists.
So far, so good. Tried compiling the 2.6.14-rc1
kernel, forward-porting all the changes that hadn't
been merged in. the kernel locks in the initial boot
sequence, after a couple of printf's.
Are there any kernel patches for the Broadcom/SiByte
processors that are specific to the 2.6.13-* or
2.6.14-*, or any options that are definitely producing
Bad Code on these kernels but not earlier?
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: sparse for mips, Ralf Baechle |
|---|---|
| Next by Date: | Kernel panic problem, Vinay Venkataraghavan |
| Previous by Thread: | Re: Building the kernel for a Broadcom SB1, Mark Mason |
| Next by Thread: | Re: Building the kernel for a Broadcom SB1, Andy Isaacson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |