From: Tom Rini <trini@kernel.crashing.org>
To: Sven Hartge <hartge@ds9.gnuu.de>
Cc: Meelis Roos <mroos@linux.ee>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-pre* does not boot on my PReP PPC
Date: Tue, 30 Mar 2004 12:09:59 -0700 [thread overview]
Message-ID: <20040330190958.GA13819@smtp.west.cox.net> (raw)
In-Reply-To: <c4cf82nnq0@ds9.argh.org>
On Tue, Mar 30, 2004 at 08:49:15PM +0200, Sven Hartge wrote:
> Um 08:15 Uhr am 29.03.04 schrieb Tom Rini:
>
> > Ok. Can both of you try the following patch on top of the version which
> > fails?
>
> 2.6.4 and earlier are unpatchable, because they differ to much from 2.6.5.
> Someone with a better connection than a tiny ISDN line should check the
> ppc32-changes between 2.6.2-rc2 and 2.6.4, because 2.6.2-rc2 was the last
> kernel I tried before 2.6.4 and 2.6.2-rc2 did at least boot.
I know what the failure is due to, in general terms. It's merging
arch/ppc/boot/prep/ into arch/ppc/boot/simple/ . What I'm not so sure
about are the specific breakage, but I know it has to do with the
OpenFirmware code as it does work (or rather, it did when I submitted
it, and I'm going to verify that 2.6.5-rc3 stock does today) on my
Motorola PowerStack Series E (PPC1Bug, not OpenFirmware).
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-03-30 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 18:33 2.6.5-pre* does not boot on my PReP PPC Meelis Roos
2004-03-26 18:51 ` Tom Rini
2004-03-27 13:55 ` Sven Hartge
2004-03-29 15:09 ` Tom Rini
2004-03-29 15:15 ` Tom Rini
2004-03-30 11:31 ` Meelis Roos
2004-03-30 18:45 ` Sven Hartge
2004-04-04 17:34 ` Christian Kujau
2004-04-05 15:50 ` Tom Rini
2004-04-05 21:19 ` Christian Kujau
2004-04-05 21:48 ` Hollis Blanchard
2004-04-05 22:30 ` Hollis Blanchard
2004-04-05 21:45 ` Christian Kujau
2004-04-05 16:15 ` Tom Rini
2004-03-30 18:49 ` Sven Hartge
2004-03-30 19:09 ` Tom Rini [this message]
2004-03-26 21:54 ` Christian Kujau
2004-03-27 13:56 ` Sven Hartge
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=20040330190958.GA13819@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=hartge@ds9.gnuu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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