From: Sven Luther <sven@genesi-usa.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: Sven Luther <sven@genesi-usa.com>, Olaf Hering <olaf@aepfle.de>,
linuxppc-dev@ozlabs.org
Subject: Re: add phy-handle property for fec_mpc52xx
Date: Wed, 9 Jan 2008 18:05:40 +0100 [thread overview]
Message-ID: <20080109170540.GA6789@powerlinux.fr> (raw)
In-Reply-To: <4784F803.9030003@genesi-usa.com>
On Wed, Jan 09, 2008 at 04:36:19PM +0000, Matt Sealey wrote:
>
> Sven Luther wrote:
> >On Wed, Jan 09, 2008 at 04:30:13PM +0000, Matt Sealey wrote:
> >>Sven Luther wrote:
> >>>Let's just fix this in the kernel, until we get a fixed efika firmware,
> >>>then we can drop it easily enough. But until this happens, we need to be
> >>>able to boot the kernel without any extra work on the users part.
> >>That is exactly why I don't like the idea. Yes, it makes it easier for
> >>users
> >>and easier for distro managers to say "it supports the Efika" but it makes
> >>the Forth fixing, and any further firmware development (ignore the lack of
> >>releases, it means nothing) much harder.
> >
> >efika firmware development is dead. Until we see a release we should
> >assume that the efika is a firmware with breakage, and no upstream
>
> The link that Olaf presented, www.powerdeveloper.org/asset/by-id/46 *is*
> the upstream support for now. What his patch does is say, the upstream
> support exists, but we don't like it, so we will supplement the patch..
Matt, your work on efika.forth is laudable, and it is nice that you took
the time to support it.
*BUT* it is not acceptable for a distribution, or for someone who will
have to do user support, to have to launch a second binary before
launching the kernel. Especially when netbooting for example.
Friendly,
Sven Luther
next prev parent reply other threads:[~2008-01-09 17:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 14:06 add phy-handle property for fec_mpc52xx Olaf Hering
2008-01-09 14:44 ` Grant Likely
2008-01-09 14:49 ` Sven Luther
2008-01-09 14:50 ` Grant Likely
2008-01-09 14:58 ` Sven Luther
2008-01-09 15:34 ` Matt Sealey
2008-01-09 15:21 ` Matt Sealey
2008-01-09 15:20 ` Grant Likely
2008-01-09 15:21 ` Sven Luther
2008-01-09 15:10 ` Grant Likely
2008-01-09 15:26 ` Matt Sealey
2008-01-09 15:35 ` Sven Luther
2008-01-09 16:30 ` Matt Sealey
2008-01-09 16:29 ` Sven Luther
2008-01-09 16:36 ` Matt Sealey
2008-01-09 17:05 ` Sven Luther [this message]
2008-01-09 17:17 ` Matt Sealey
2008-01-09 17:22 ` Sven Luther
2008-01-09 15:46 ` Grant Likely
2008-01-09 16:35 ` Matt Sealey
2008-01-09 16:44 ` Grant Likely
2008-01-09 15:49 ` David Woodhouse
2008-01-09 16:48 ` Matt Sealey
2008-01-10 2:21 ` Paul Mackerras
2008-01-10 5:04 ` Benjamin Herrenschmidt
2008-01-10 9:14 ` David Woodhouse
2008-01-09 16:02 ` Olof Johansson
2008-01-09 16:26 ` Grant Likely
2008-01-10 2:20 ` Paul Mackerras
2008-01-10 11:47 ` Olaf Hering
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=20080109170540.GA6789@powerlinux.fr \
--to=sven@genesi-usa.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
--cc=olaf@aepfle.de \
/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).