linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Olaf Hering <olaf@aepfle.de>
Subject: Re: add phy-handle property for fec_mpc52xx
Date: Wed, 9 Jan 2008 09:44:55 -0700	[thread overview]
Message-ID: <fa686aa40801090844t18fd5e2cy63dd6b3c46ca1ae2@mail.gmail.com> (raw)
In-Reply-To: <4784F7D1.1050301@genesi-usa.com>

On 1/9/08, Matt Sealey <matt@genesi-usa.com> wrote:
> > However, I'm still inclined to pick up Olaf's patch with the
> > appropriate protections around it so it is only done if the nodes are
> > missing.
>
> Eh.. yeah. Maybe. Seems like a cop-out to me. I would rather you removed
> the patch and called us a bunch of idiots for coding bad firmware, than
> have the fixups be dependant on what could turn into a very well coded
> but essentially screen-long list of fixups for myriad firmware versions
> where the properties may or may not be present or correct for various
> firmware versions and devices.

I've come to the conclusion that Postel knew what he was talking
about; "Be conservative in what you do; be liberal in what you accept
from others."  :-)

I 100% agree that this stuff is better done in firmware.  However,
until that stuff is in place; it is 100% reasonable and desirable to
work around it in prom_init.  That being said, I will modify prom_init
to not blindly apply fixups if they have already been done in
firmware.

> Grant, are you any good at coding firmware-level stuff without utilizing
> any preexisting code under the GPL? I'd like to collaborate on an installer
> tool which can put efika.forth (and therefore all these fixes) in.

I'm good at firmware stuff, but time comes at a premium.  This level
of work would require a contract arrangement between our two
companies.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-01-09 16:44 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
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 [this message]
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=fa686aa40801090844t18fd5e2cy63dd6b3c46ca1ae2@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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).