|To:||Don Fry <brazilnut@xxxxxxxxxx>|
|Subject:||Re: Ethernet MAC address question|
|From:||Jeff Garzik <jgarzik@xxxxxxxxx>|
|Date:||Tue, 15 Jun 2004 12:11:18 -0400|
|Cc:||Mark Brown <broonie@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510|
Don Fry wrote:
So how does the driver distinguish between a valid, but incorrect MAC address, and the 'correct' MAC address? The incorrect one that is the value that just happened to be in the uninitialized volatile registers, and the correct address which some magic platform means loaded into the same, but this time initialized, volatile registers.
You have to notice that certain platform-specific attributes are present, that tells your code to search in <this magic place> rather than the standard place for MAC address.
For example, some Compaqs have a magic MAC address location (this might even be pcnet32), and one solution proposed was looking for the platform's DMI table identifiers. Another solution -- working -- was to load the MAC address registers when the driver loads, and just hope it is a correct address.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [RFC] Wireless extensions rethink, Vladimir Kondratiev|
|Next by Date:||[1/9][PATCH 2.6] Restructure reset code, Roger Luethi|
|Previous by Thread:||Re: Ethernet MAC address question, Don Fry|
|Next by Thread:||ENOBUFS and dev_queue_xmit(), Alex Pankratov|
|Indexes:||[Date] [Thread] [Top] [All Lists]|