From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, arnd@arndb.de
Subject: Re: [PATCH 2/15] powerpc, celleb: Basic supports for Celleb
Date: Thu, 14 Dec 2006 07:37:17 +0000 [thread overview]
Message-ID: <1166081837.5253.822.camel@pmac.infradead.org> (raw)
In-Reply-To: <1166074655.11914.313.camel@localhost.localdomain>
On Thu, 2006-12-14 at 16:37 +1100, Benjamin Herrenschmidt wrote:
> > > I'm not sure if it's a good idea to claim CHRP compatibility
> > > here. Is that a workaround for a specific incompatibility? Normally,
> > > I'd say you should print "machine\t\t: BEAT %s\n" or
> > > "machine\t\t: Celleb %s\n", since you are definitely not running
> > > a CHRP compatible firmware.
> >
> > This is placed only to "trick" Anaconda into installing Fedora Core Linux.
> > Fedora refuses to be installed into 'unknown' system.
>
> David, can you do some serious LART'ing of whoever is responsible for
> this in anaconda ? Is there at least an option somebody can pass on the
> commmand line to make it work on unknown platforms ?
Define 'work'. I believe it ends up doing _different_ things according
to the machine type -- in particular the selection of the bootloader
setup. You want to treat all unknown machines as CHRP? Paul, can we do
that?
When does the Fedora team get a Celleb machine for compatibility
testing, btw?
--
dwmw2
next prev parent reply other threads:[~2006-12-14 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 3:14 [PATCH 2/15] powerpc, celleb: Basic supports for Celleb Ishizaki Kou
2006-12-12 12:42 ` Arnd Bergmann
2006-12-14 1:38 ` Ishizaki Kou
2006-12-14 5:37 ` Benjamin Herrenschmidt
2006-12-14 7:37 ` David Woodhouse [this message]
2006-12-14 7:43 ` Benjamin Herrenschmidt
2006-12-14 8:24 ` Geert Uytterhoeven
2006-12-12 17:26 ` Geoff Levand
2006-12-14 1:52 ` Ishizaki Kou
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=1166081837.5253.822.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.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).