linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven@genesi-usa.com>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Olaf Hering <olaf@aepfle.de>,
	sven@genesi-usa.com
Subject: Re: add phy-handle property for fec_mpc52xx
Date: Wed, 9 Jan 2008 16:35:11 +0100	[thread overview]
Message-ID: <20080109153511.GA5086@powerlinux.fr> (raw)
In-Reply-To: <4784E78C.40904@genesi-usa.com>

On Wed, Jan 09, 2008 at 03:26:04PM +0000, Matt Sealey wrote:
> Clarification: I really have to disagree with this patch, and Sven.
> 
> The whole point of removing the stuff from the Linux kernel (as the
> efika.forth script and the associated patch performs) is that it means
> the Linux kernel is no longer a "moving target" for our firmware
> development.

What firmware development ? 

> If users require these kernels they can run efika.forth - the major
> stumbling block being this is quite ugly to do right now. This is our
> problem - bplan, Genesi, myself whoever you want to target - it should
> not be made into a Linux problem by creating this "moving target" that
> needs constant patching to maintain driver coherency.

Then get the firmware fixed, and everyone would be happy. I don't see
that happening in the near future, just as there has been no pegasos
firmware release in ages, and my work on it has been scratched, and
ignored for the efika firmware which has lot of regression compared to
the latest pegasos beta releases.

A new efika firmware upgrade has been promised in, what was it, marsch
last year or so, where is it ? 

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.

Friendly,

Sven Luther

  reply	other threads:[~2008-01-09 15:35 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 [this message]
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
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=20080109153511.GA5086@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).