| To: | Stuart Longland <stuartl@longlandclan.hopto.org> |
|---|---|
| Subject: | Re: Kernel 2.6 for R4600 Indy |
| From: | Florian Lohoff <flo@rfc822.org> |
| Date: | Fri, 24 Sep 2004 11:07:03 +0200 |
| Cc: | "Stephen P. Becker" <geoman@gentoo.org>, linux-mips@linux-mips.org |
| In-reply-to: | <41536765.9000304@longlandclan.hopto.org> |
| Organization: | rfc822 - pure communication |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <4152D58B.608@longlandclan.hopto.org> <4152E4FC.8000408@gentoo.org> <41536765.9000304@longlandclan.hopto.org> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.4i |
On Fri, Sep 24, 2004 at 10:16:37AM +1000, Stuart Longland wrote:
> Ahh yes... sorry, it was after midnight (GMT+10) and my mind must've
> been elsewhere -- I meant o64. I was planning on moving to either n32
> or n64 userland eventually, but I won't do that unless I can get a
> 64-bit kernel going.
The 64 bit kernel should work so far - With the ip22zilog.c fixes
tsbogend just committed the console begins to work again.
Includeing the patch i sent earlier my R5k Indy boots fine a 64bit
current cvs head and goes into userspace.
Using the "soo to be" rtc and statfs64 fixes everything seems to be
fine for o32 userspace.
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | "Can't analyze prologue code ..." at boot time, Thomas Petazzoni |
|---|---|
| Next by Date: | Re: "Can't analyze prologue code ..." at boot time, Atsushi Nemoto |
| Previous by Thread: | Re: Kernel 2.6 for R4600 Indy, Stuart Longland |
| Next by Thread: | Re: Kernel 2.6 for R4600 Indy, Stuart Longland |
| Indexes: | [Date] [Thread] [Top] [All Lists] |