From: David Woodhouse <dwmw2@infradead.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: removal of arch/ppc in 2.6.27?
Date: Mon, 21 Apr 2008 09:03:05 +0100 [thread overview]
Message-ID: <1208764985.9212.453.camel@pmac.infradead.org> (raw)
In-Reply-To: <18443.13999.770734.826892@cargo.ozlabs.ibm.com>
On Sun, 2008-04-20 at 22:27 +1000, Paul Mackerras wrote:
> Marvin writes:
>
> > will this be the end of life for all the PReP's ? I remember a patch posted
> > some month ago, but didn't heard anything since then. Any news? Or just let
> > it die quietly?
>
> No, I'm still planning on getting PReP support over to arch/powerpc,
> but getting time to work on it has been the difficulty.
>
> What sort of PReP do you have?
I have a 43P-140, which I bought on eBay a few weeks ago to add to the
Fedora testing pile. Foolishly I was trying to get the CHRP kernel
booting on it, just because it says 'chrp' in its device_type.
Unfortunately I seem to have killed it -- I tried to update its firmware
from TIG97251 to TIG04204 and although the update looked successful, it
never came back. Says 'F2A' on the diagnostic panel. I renamed the
firmware file on the floppy to 'precover.img' as the documentation
suggests, but it never even looks at the floppy drive when it starts up.
Anyone know if the firmware flash on these can be removed and flashed
externally, or have any better suggestions?
--
dwmw2
next prev parent reply other threads:[~2008-04-21 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 15:30 removal of arch/ppc in 2.6.27? Kumar Gala
2008-04-19 16:27 ` Grant Likely
2008-04-19 18:13 ` Josh Boyer
2008-04-19 20:43 ` Chuck Meade
2008-04-20 0:39 ` Dwayne Fontenot
2008-04-20 11:14 ` Marvin
2008-04-20 12:27 ` Paul Mackerras
2008-04-20 12:55 ` Gabriel Paubert
2008-04-20 13:43 ` Marvin
2008-04-21 8:03 ` David Woodhouse [this message]
2008-05-16 14:05 ` Suresh Chandra Mannava
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=1208764985.9212.453.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).