All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: MIPS - 64bit woes
Date: Mon, 07 Nov 2005 19:51:21 -0500	[thread overview]
Message-ID: <436FF689.3010308@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0511071143210.28165@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
> 
>  It must be platform-specific -- I haven't checked 2.6.14, but 64-bit
> 2.6.13 is good enough to boot into multi-user with the SWARM.

2.6.13.4 works on all systems I can test (O2, Octane, Origin*, Indy, I2 Impact), 
but for me, it appears 2.6.14 dies very early in kernel initialization on both 
Octane and Origin.  I have yet to try another, like O2, but I'm going to do that 
shortly in the hopes O2 may initialize an output device and give me an idea of 
what's going on.

* 2.6.13.4 Works on Origin, but can't allocate PCI resources for the scsi 
properly.  2.6.12.5 is what works best for this system.


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  reply	other threads:[~2005-11-08  0:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05 18:56 MIPS - 64bit woes Jim Gifford
2005-11-05 23:19 ` Kumba
2005-11-07 22:22   ` Jim Gifford
2005-11-08  1:41     ` Stuart Anderson
2005-11-07 11:46 ` Maciej W. Rozycki
2005-11-08  0:51   ` Kumba [this message]
2005-11-09  8:51   ` Jim Gifford
2005-11-09 13:36     ` Kumba
2005-11-09 17:22       ` Jim Gifford
2005-11-15 15:17         ` Jim Gifford
2005-11-17 22:57           ` Jim Gifford
2005-11-18  1:21             ` Jim Gifford
2005-11-18 17:17               ` Ralf Baechle
2005-11-18 17:24                 ` Jim Gifford
2005-11-18 17:29                   ` Ralf Baechle
2005-11-19 17:36                     ` mips iomap.c (Was: Re: MIPS - 64bit woes) Atsushi Nemoto

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=436FF689.3010308@gentoo.org \
    --to=kumba@gentoo.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.