All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Blackfin: bfin_mac: hook up new write_hwaddr function
Date: Fri, 30 Apr 2010 09:10:47 -0400	[thread overview]
Message-ID: <201004300910.48443.vapier@gentoo.org> (raw)
In-Reply-To: <m27hnpktai.fsf@ohwell.denx.de>

On Friday 30 April 2010 08:40:21 Detlev Zundel wrote:
> > if the new direction is to have the OS booted with the current correct
> > MAC address programmed regardless of any net funcs being called, then
> > the current logic in eth_initialize() will probably need to be
> > replicated back into cmd_nvedit (see commit 56b555a644).  then the logic
> > in eth_init() here can be dropped, and drivers themselves can lose the
> > MAC programming in their init() funcs.
> 
> For the direction we have taken, I consider this to be a completion of
> the path.  Actually I did not realize that we had such a mac-programming
> in "setenv" at all and that Mike explicitely took it out, but I realized
> that we certainly would need such a thing.  I considered it to be much
> easier hoewever once we have such a method of the netdevice.

you seem to be confused by what that code actually did.  it never programmed 
the mac in the hardware, it synced the eth_device and the environment.  the 
behavior we have today is exactly the same before that series of commits i 
referenced.  i simply standardized things across the board and unified heavily 
duplicated behavior.  what i'm talking about adding here is different from 
what used to be there ... it's just that the mechanism is the same.

> > however, considering the number of drivers and thrashing this policy is
> > causing, and the intent for this to be a stop gap measure, i'm not sure
> > we should change the init() func in drivers to stop programming the MAC
> > address. otherwise we're going to have to do this same thing yet again
> > but in the reverse direction.
> 
> We are aiming at a level of consitency which we never had before, so I
> expect some changes.  They are quite small however and the amount of
> ongoing patches to adopt the new policy encourage me to be optimistic
> here ;)

there's going to be one patch for every driver.  just because only a few 
people have submitted patches for drivers they're interested in doesnt mean 
the overall thrashing is small.  a quick grep counts about 35 drivers that 
need updating.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100430/f9098326/attachment.pgp 

      reply	other threads:[~2010-04-30 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 18:15 [U-Boot] [PATCH] Blackfin: bfin_mac: hook up new write_hwaddr function Mike Frysinger
2010-04-27 18:33 ` Ben Warren
2010-04-27 18:42   ` Mike Frysinger
2010-04-27 18:46     ` Ben Warren
2010-04-27 19:32       ` Mike Frysinger
2010-04-27 20:07         ` Ben Warren
2010-04-27 20:24           ` Mike Frysinger
2010-04-30 12:40             ` Detlev Zundel
2010-04-30 13:10               ` Mike Frysinger [this message]

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=201004300910.48443.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.