All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
To: sparclinux@vger.kernel.org
Subject: Re: Linux 2.6.3 still doesn't boot on UltraSparc I
Date: Thu, 26 Feb 2004 09:12:05 +0000	[thread overview]
Message-ID: <20040226091205.GA1059@blop.info> (raw)
In-Reply-To: <20040224144245.GA468@phunnypharm.org>

On Wed, Feb 25, 2004 at 12:28:53AM -0800, "David S. Miller" <davem@redhat.com> wrote:
> On Tue, 24 Feb 2004 09:42:45 -0500
> Ben Collins <bcollins@debian.org> wrote:
> 
> > Why it's looping with prom_init(), I'm not sure. Maybe the prom cif
> > handler and stack aren't getting setup properly. Dave, any ideas?
> 
> Nothing jumps to my mind, it might even be just looping inside the
> OBP itself, ie. in the prom_printf() call.

Ok. Now, what's next ? I understand fixing a problem with some very old
Sparcs isn't one of your priorities. Do you want to drop support for
them in 2.6 ? Or there is still something you/we could do to try to fix
this ?

The box is a quadriprocessor with 1.6GB RAM, so we really are interested
in using it : it isn't _that_ slow.

Lucas

  parent reply	other threads:[~2004-02-26  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 14:42 Linux 2.6.3 still doesn't boot on UltraSparc I Ben Collins
2004-02-25  8:28 ` David S. Miller
2004-02-26  9:12 ` Lucas Nussbaum [this message]
2004-02-26 13:08 ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2004-02-10 16:32 2.6.3-rc2 fails to boot with "Illegal Instruction" on sparc64 Lucas Nussbaum
2004-02-23 13:32 ` Linux 2.6.3 still doesn't boot on UltraSparc I Lucas Nussbaum
2004-02-23 13:25   ` Ben Collins
2004-02-23 15:06     ` Lucas Nussbaum
2004-02-23 15:45       ` Ben Collins
2004-02-24 12:57         ` Lucas Nussbaum

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=20040226091205.GA1059@blop.info \
    --to=lucas@lucas-nussbaum.net \
    --cc=sparclinux@vger.kernel.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.