public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bootloader MAC
Date: Fri, 9 Jun 2006 12:14:02 -0500	[thread overview]
Message-ID: <200606091214.02360.ngustavson@emacinc.com> (raw)
In-Reply-To: <20060609165626.9F7573535E0@atlas.denx.de>

On Friday 09 June 2006 11:56 am, you wrote:
> You never bothered to check for example  "drivers/rtl8139.c"  in  the
> U-Boot sources or "drivers/net/8139*.c" in the Linux kernel tree.
>
> You never bothered to check for example  "drivers/eepro100.c"   in  the
> U-Boot sources or "drivers/net/e100.c"  in the Linux kernel tree.
Your right I didn't check the driver, but I checked the data sheets which 
states that the MAC is loaded upon any reset. If the driver does it it's 
purely redundancy

>You claim things which you obviously never checked.
> It's a common practice among ethernet controllers, such as the Realtek 8139 
> and the Intel 82559 to have the MAC address automatically load from the 
> EEPROM upon reset with no intervention from any sort of driver.
There is nothing about my statement that is not true.

>But you write:
> There isn't really anything incorrect about expecting the MAC to be
> valid upon loading the OS,It's typical of the industry.
>Maybe you should go and read a bit of driver code from some operating
>systems, before claiming to know what these do or don't do.
I stand by my statement. The core system put's it there, regardless of whether 
the OS reloads it or not. I believe we should do the same.

It is an interesting point however, I was unaware that the drivers are loading 
the MAC, thank you for pointing it out. Nevertheless, the MAC was already 
there, this loading is redundant.

NZG.

  reply	other threads:[~2006-06-09 17:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 16:34 [U-Boot-Users] Help U-Boot NFS filesystem muqiyong
     [not found] ` <008501c68b19$639091e0$8ed3fea9@first>
2006-06-08 16:57   ` Wolfgang Denk
2006-06-08 17:57     ` Marco Cavallini
2006-06-08 19:49       ` Wolfgang Denk
2006-06-08 20:22         ` Marco Cavallini
2006-06-08 20:59           ` Wolfgang Denk
2006-06-08 20:40         ` [U-Boot-Users] Help U-Boot NFS filesystem->bootloader MAC NZG
2006-06-08 21:40           ` Wolfgang Denk
2006-06-08 22:31             ` [U-Boot-Users] bootloader MAC NZG
2006-06-08 22:58               ` Rune Torgersen
2006-06-08 23:16                 ` NZG
2006-06-08 23:24                   ` Rune Torgersen
2006-06-09  0:49                     ` Wolfgang Denk
2006-06-09  0:44               ` Wolfgang Denk
2006-06-09  4:06                 ` NZG
2006-06-09  7:44                   ` Wolfgang Denk
2006-06-09 14:23                     ` NZG
2006-06-09 16:56                       ` Wolfgang Denk
2006-06-09 17:14                         ` NZG [this message]
2006-06-09 17:58                         ` NZG
2006-06-09  8:48 ` [U-Boot-Users] Help U-Boot NFS filesystem Alex Zeffertt
2006-06-09 12:22   ` muqiyong
     [not found]     ` <002401c68bbf$6f7dfd20$8ed3fea9@first>
2006-06-09 13:08       ` Wolfgang Denk
2006-06-10  3:18         ` [U-Boot-Users] Help U-Boot NFS filesystem. (Flash error! maybe I need wait my next board) muqiyong

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=200606091214.02360.ngustavson@emacinc.com \
    --to=ngustavson@emacinc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox