From: Daniel Ann <ktdann@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EEPROM content and multiple NIC
Date: Fri, 22 Apr 2005 14:35:06 +0900 [thread overview]
Message-ID: <9b7ca657050421223538095e59@mail.gmail.com> (raw)
In-Reply-To: <61cc712d05042110026ef75769@mail.gmail.com>
On 4/22/05, Kylo Ginsberg <kylo.ginsberg@gmail.com> wrote:
> Compounding the confusion is the god-awful bit-swapping method of
> access to the EEPROM. And then someone at National who was either
> confused or had a sick sense of humor apparently provided EEPROM
> defaults for the Subsystem Vendor Id (0x2c) and Subsystem Device Ids
> (0x2e) that are bitswapped versions of the main Vendor Id (0x00) and
> Device Id (0x02). Ugh.
I take it its an explanation right ? :)
Yeah.. Ugh indeed. I guess its that somebody who obviously had one
drink too many would know why then.
Interesting..
--
Daniel
next prev parent reply other threads:[~2005-04-22 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 15:13 [U-Boot-Users] EEPROM content and multiple NIC Frank
2005-04-21 8:44 ` Daniel Ann
2005-04-21 17:02 ` Kylo Ginsberg
2005-04-22 5:35 ` Daniel Ann [this message]
-- 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 5:24 Daniel Ann
2005-04-20 6:07 ` Mark Rakes
2005-04-20 6:44 ` 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=9b7ca657050421223538095e59@mail.gmail.com \
--to=ktdann@gmail.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