linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] bootwrapper: In cuImage, print message for ENET devices not found in tree
Date: Fri, 31 Aug 2007 14:25:36 +1000	[thread overview]
Message-ID: <20070831042536.GL19271@localhost.localdomain> (raw)
In-Reply-To: <fa686aa40708302114g77b916bftb01c14e1b3357506@mail.gmail.com>

On Thu, Aug 30, 2007 at 10:14:41PM -0600, Grant Likely wrote:
> On 8/30/07, David Gibson <david@gibson.dropbear.id.au> wrote:
> > On Thu, Aug 30, 2007 at 02:26:18PM -0600, Grant Likely wrote:
> > > From: Grant Likely <grant.likely@secretlab.ca>
> > >
> > > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > > CC: Scott Wood <scottwood@freescale.com>
> > > CC: Kumar Gala <galak@kernel.crashing.org>
> > > CC: David Gibson <david@gibson.dropbear.id.au>
> >
> > Hrm... I thought Scott had deliberately removed that message in his
> > patch set, to work with the way PlanetCore generates Ethernet
> > addresses.
> 
> I'm confused then.  The code either sets the property or it doesn't.
> >From what I can see, the message doesn't make any sense in the context
> of *not* calling setprop().  How does PlanetCore work?  Scott?

Sorry, I was misleading.  Scott moved the printf() into the if (devp)
as you do, but *didn't* add the alternative warning message in the
else.

The reason for this is that Planetcore only supplies the first MAC
address, and the bootwrapper must derive the addresses for all the
ENETs from that.  That in turn means it is much more convenient to
call fixup_mac_addresses() with more addresses than there are
ethernets, so we don't want a warning message when that happens.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-08-31  4:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 20:26 [PATCH 1/3] bootwrapper: In cuImage, print message for ENET devices not found in tree Grant Likely
2007-08-30 20:26 ` [PATCH 2/3] mpc8349: Add linux, network-index to ethernet nodes in device tree Grant Likely
2007-08-31  2:44   ` David Gibson
2007-08-30 20:26 ` [PATCH 3/3] mpc8349emitx(gp): update defconfigs for 2.6.23 Grant Likely
2007-08-31  2:43 ` [PATCH 1/3] bootwrapper: In cuImage, print message for ENET devices not found in tree David Gibson
2007-08-31  4:14   ` Grant Likely
2007-08-31  4:25     ` David Gibson [this message]
2007-08-31 15:29       ` Grant Likely

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=20070831042536.GL19271@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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).