Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: gigo@poczta.ibb.waw.pl
Cc: linux-mips@linux-mips.org
Subject: Re: Old Indy, 64-bit setup
Date: Wed, 23 Jan 2008 10:51:13 +0100	[thread overview]
Message-ID: <20080123095113.GA30081@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801222106460.31014@poczta.ibb.waw.pl>

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

On Tue, Jan 22, 2008 at 10:10:37PM +0100, gigo@poczta.ibb.waw.pl wrote:
>  Hello,
> Just a silly question. Is there any working 64-bit kernel configuration 
> for my r4k 100MHz Indy? From time to time i compile another new kernel for 
> 64-bit... and see the thing dying. Recently it looked pretty well like 
> Indy r4k 100MHz (BROTHER!?!?!) crash shown in 
> http://www.linux-mips.org/archives/linux-mips/2007-11/msg00186.html
> Everything but the kernel is debian stable: binutils 2.17
> gcc 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)...

There are CPU Bug workarounds needed which are not yet complete in
kernel and gcc. I am running my 100Mhz Indy with an 32Bit Kernel built
from the debian source package just by replacing the 64BIT ...

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-171-2280134
	Those who would give up a little freedom to get a little 
          security shall soon have neither - Benjamin Franklin

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2008-01-23  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 21:10 Old Indy, 64-bit setup gigo
2008-01-22 22:33 ` Thomas Bogendoerfer
2008-01-23 17:53   ` Maciej W. Rozycki
2008-01-23  9:51 ` Florian Lohoff [this message]

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=20080123095113.GA30081@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=gigo@poczta.ibb.waw.pl \
    --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