From: Kylo Ginsberg <kylo.ginsberg@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EEPROM content and multiple NIC
Date: Thu, 21 Apr 2005 10:02:47 -0700 [thread overview]
Message-ID: <61cc712d05042110026ef75769@mail.gmail.com> (raw)
In-Reply-To: <9b7ca65705042101442a4a1f64@mail.gmail.com>
Daniel,
I haven't used this part but took a look at the manual. Please note
that PCI configuration registers include Vendor ID (at offset 0x00)
and Subsystem Vendor ID (at offset 0x2c). Look in linux/pci.h. On
this part, the former is read-only always 0x100b, the latter can be
read from EEPROM.
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.
Kylo
On 4/21/05, Daniel Ann <ktdann@gmail.com> wrote:
> On 4/21/05, Frank <frannk_m1@yahoo.com> wrote:
> > > > > > d008 == 1101000000001000
> > > > > > 100b == 0001000000001011
>
> > Oops, you're right, I meant the bits appear to be reversed. Like
> > they were shifted in bit 0 first and the other bit 31 first...
>
> yeah.. you guys are right. It aint endian issue. Funny thing is,
> NS83815 manual thinks d008, while pci_ids file thinks 100b.
>
> I still have no idea how one could actually read it this way. I dont
> think any right mind will delibrately read it this way.
> I guess a dive into the code will help but.. gonna leave it for later :P
>
> Anyway, got my EEPROM content right this time. And all is working
> smoothly. As u-boot boots its displaying the content of EEPROM in
> exactly the fashion shown above.
>
> --
> Daniel
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: New Crystal Reports XI.
> Version 11 adds new functionality designed to reduce time involved in
> creating, integrating, and deploying reporting solutions. Free runtime info,
> new features, or free trial, at: http://www.businessobjects.com/devxi/728
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
>
next prev parent reply other threads:[~2005-04-21 17:02 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 [this message]
2005-04-22 5:35 ` 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 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=61cc712d05042110026ef75769@mail.gmail.com \
--to=kylo.ginsberg@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