From: Mark Rakes <mrakes@mac.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EEPROM content and multiple NIC
Date: Tue, 19 Apr 2005 23:07:22 -0700 [thread overview]
Message-ID: <918fdd71464515158f829fd2530f6ebf@mac.com> (raw)
In-Reply-To: <9b7ca65705041922243be672db@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Apr 19, 2005, at 10:24 PM, Daniel Ann wrote:
> I'm very curious about this output I'm getting,
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 00 14 100b 0020 0200 ff
...
> Net: natsemi: EEPROM contents:
> d008 0001 0001 0001 0001 0001 0001 0001 0001 0001 1841 0001
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> As far as I know, NS83815 manual claims that d008 is a default value
> for vendor ID. but pci_ids thinks 100b is National semiconductor's
> vendor ID. Does anyone know why the difference ?
d008 == 1101000000001000
100b == 0001000000001011
It's been a long, long time since I touched/looked at this code (or the
docs!), so don't ask me why this is like it is, but, there you have
it...
I do remember that getting MAC addresses into the EEPROM wasn't much
fun because of the shifting required to get the bits into the right
places.
hope this helps,
- -mark rakes
-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.0 (Build 1917)
Comment: secure:
iQA/AwUBQmXxor7wvj+mn5e0EQJZQwCgxlk6DqwQjjZRQENWEHFKPONxe2EAoN7D
Kw8DfjjKiOeVhNbiyvYs3tb9
=QHgw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-04-20 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 5:24 [U-Boot-Users] EEPROM content and multiple NIC Daniel Ann
2005-04-20 6:07 ` Mark Rakes [this message]
2005-04-20 6:44 ` Daniel Ann
-- strict thread matches above, loose matches on Subject: below --
2005-04-20 14:44 Frank
2005-04-20 15:08 ` Wolfgang Denk
2005-04-20 15:13 Frank
2005-04-21 8:44 ` Daniel Ann
2005-04-21 17:02 ` Kylo Ginsberg
2005-04-22 5:35 ` Daniel Ann
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=918fdd71464515158f829fd2530f6ebf@mac.com \
--to=mrakes@mac.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