From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Sylvain Munaut <tnt@246tNt.com>,
Paul Mackerras <paulus@samba.org>,
bbrv@genesi-usa.com
Subject: Re: [PATCH] Probe Efika platform before CHRP.
Date: Tue, 02 Jan 2007 21:29:48 +0000 [thread overview]
Message-ID: <1167773388.22068.443.camel@pmac.infradead.org> (raw)
In-Reply-To: <1166558300.19254.71.camel@localhost.localdomain>
On Wed, 2006-12-20 at 06:58 +1100, Benjamin Herrenschmidt wrote:
> > OK, let's drop the patch and assume the device-tree will be fixed
> > shortly.
>
> No, keep the patch for now. I'm afraid they aren't willing to fix their
> device-tree.
They need to fix their firmware anyway, because it's screwed in other
ways too -- they have an off-by-one error in their handling of partition
numbers, so when yaboot tries to read a partition table it actually gets
the first sector of the first partition, and it all goes downhill from
there. That one was even _fixed_ in the Pegasos firmware last year, but
it's come back in Efika -- and we _can't_ work around it in the kernel.
For Fedora, we're just going to wait for the fixed firmware; we can't
sensibly support it as-is.
--
dwmw2
next prev parent reply other threads:[~2007-01-02 21:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 6:23 Bug fixes for 2.6.20 Paul Mackerras
2006-12-19 9:54 ` [PATCH] Probe Efika platform before CHRP David Woodhouse
2006-12-19 11:39 ` Benjamin Herrenschmidt
2006-12-19 11:55 ` Sylvain Munaut
2006-12-19 14:29 ` David Woodhouse
2006-12-19 15:46 ` Grant Likely
2006-12-19 19:58 ` Benjamin Herrenschmidt
2006-12-19 22:33 ` Sylvain Munaut
2007-01-02 21:29 ` David Woodhouse [this message]
2007-01-02 21:37 ` Benjamin Herrenschmidt
2007-01-02 22:04 ` David Woodhouse
2007-01-02 23:04 ` Grant Likely
[not found] ` <45A01416.6080401@genesi-usa.com>
2007-01-06 22:23 ` Grant Likely
2007-01-06 23:13 ` David Woodhouse
2007-01-06 23:37 ` Grant Likely
2007-01-07 2:55 ` Sylvain Munaut
2007-01-07 9:11 ` Raquel Velasco and Bill Buck
2007-03-31 13:15 ` David Woodhouse
2007-03-31 13:18 ` Raquel Velasco and Bill Buck
2007-03-31 13:21 ` David Woodhouse
2007-05-09 11:42 ` Olaf Hering
2007-05-09 11:45 ` Raquel Velasco and Bill Buck
2007-01-07 20:09 ` Matt Sealey
2007-01-07 20:24 ` Segher Boessenkool
2007-01-07 22:10 ` Matt Sealey
2007-01-07 22:35 ` Benjamin Herrenschmidt
2007-01-07 22:35 ` Sylvain Munaut
2007-01-07 23:04 ` Segher Boessenkool
2007-01-07 23:07 ` Matt Sealey
2007-01-07 23:38 ` Sylvain Munaut
2007-01-08 0:37 ` Benjamin Herrenschmidt
2007-01-07 22:32 ` Matt Sealey
2007-01-07 22:39 ` Matt Sealey
2007-01-07 23:27 ` Segher Boessenkool
2007-01-07 21:16 ` Benjamin Herrenschmidt
2007-01-08 2:17 ` David Woodhouse
2007-01-08 9:18 ` Matt Sealey
2007-01-08 12:52 ` Sylvain Munaut
2007-01-08 13:16 ` Sylvain Munaut
2007-01-08 17:25 ` Matt Sealey
2007-01-08 15:44 ` Sylvain Munaut
2007-01-08 17:25 ` Matt Sealey
2007-01-08 17:24 ` Matt Sealey
2007-01-08 17:59 ` Sylvain Munaut
2006-12-19 19:02 ` [PATCH] powerpc export rtas_set_slot_reset() Linas Vepstas
2006-12-19 22:08 ` Brian King
2006-12-19 19:06 ` [PATCH] powerpc fixup error message Linas Vepstas
2006-12-19 20:00 ` [PATCH] powerpc initialize pci device channel state Linas Vepstas
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=1167773388.22068.443.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=bbrv@genesi-usa.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tnt@246tNt.com \
/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).