From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] PCIE supported networking cards?
Date: Wed, 2 Feb 2011 15:51:14 -0800 [thread overview]
Message-ID: <201102021551.15060.Aaron.Williams@caviumnetworks.com> (raw)
In-Reply-To: <A30AC2CB-52E2-47A0-A7CF-B0E8AF654A09@kernel.crashing.org>
Thanks,
I took the patch but it looks like it's unable to read the eeprom. It's
possible it may also have something to do with our PCIE implementation since
I'm trying to bring that up with the updated u-boot. I also need to go through
the code and make sure that the driver is 64-bit friendly since we load u-boot
above 4GB when enough memory is loaded (virt_to_phys returns a 64-bit address
on our platform).
In the Linux e1000e driver I do see some differences between the e1000_82573
and the e1000_82574.
-Aaron
PCIe: Port 0 is SRIO, skipping.
PCIe: Port 1 link active, 1 lanes, speed gen1
PCI Autoconfig: Bus Memory region: [0xf8000000-0xffffffff],
Physical Memory [f8000000-ffffffffx]
PCI Autoconfig: Bus I/O region: [0x100000-0x1000ffffe],
Physical Memory: [100000-1000ffffe]
address=0x100000 bus_lower=0x100400PCI: Bus Dev VenId DevId Class Int
PCI Autoconfig: Bus Memory region: [0xf8000000-0xffffffff],
Physical Memory [f8000000-ffffffffx]
PCI Autoconfig: Bus I/O region: [0x100000-0x1000ffffe],
Physical Memory: [100000-1000ffffe]
PCI Scan: Found Bus 0, Device 0, Function 0
PCI Autoconfig: BAR 0, Mem, size=0x20000, address=0xf8000000
bus_lower=0xf8020000
PCI Autoconfig: BAR 1, Mem, size=0x80000, address=0xf8080000
bus_lower=0xf8100000
PCI Autoconfig: BAR 2, I/O, size=0x20, address=0x100000 bus_lower=0x100020
PCI Autoconfig: BAR 3, Mem, size=0x4000, address=0xf8100000
bus_lower=0xf8104000
PCIe: port=1, first_bus=0, last_bus=0
e1000_initialize
e1000#0: iobase 0xf8000000
e1000_set_mac_type
Found 52574, setting mac type to 17
e1000_set_media_type
copper interface
e1000_reset_hw
Masking off all interrupts
Issuing a global reset to MAC
Masking off all interrupts
e1000_init_eeprom_params
e1000_is_onboard_nvm_eeprom
e1000_validate_eeprom_checksum
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
e1000_read_eeprom
e1000_is_onboard_nvm_eeprom
On Tuesday, February 01, 2011 08:18:27 pm Kumar Gala wrote:
> You may want to look at the following patch that adds support for 0x10d3:
>
> http://patchwork.ozlabs.org/patch/79788/
>
> - k
>
> On Feb 1, 2011, at 3:32 PM, Aaron Williams wrote:
> > This is an Intel EXPI9301 PRO/1000 OEM card, vendor ID 0x8086, device ID
> > 0x10d3. I added it to the list but I don't know what the MAC type is.
> > I'll look into the Linux driver and see if I can see what it is.
> >
> > -Aaron
> >
> > On Tuesday, February 01, 2011 11:19:24 am Scott Wood wrote:
> >> On Tue, 1 Feb 2011 13:15:01 -0600
> >>
> >> Kumar Gala <galak@kernel.crashing.org> wrote:
> >>> We utilize e1000 PCIe cards all the time
> >>
> >> Aren't there some versions that work, and some that don't?
> >>
> >> -Scott
> >>
> >>> - k
> >>>
> >>> On Feb 1, 2011, at 1:10 PM, Aaron Williams wrote:
> >>>> Are there any PCIE networking cards that are supported? So far I've
> >>>> tried an Intel card and a Realtek RTL8168 card, but neither is
> >>>> supported. It looks like the E1000 driver only supports PCI and PCIX
> >>>> based cards (Linux uses the e1000e card for PCIe cards).
> >>>>
> >>>> -Aaron
> >>>> _______________________________________________
> >>>> U-Boot mailing list
> >>>> U-Boot at lists.denx.de
> >>>> http://lists.denx.de/mailman/listinfo/u-boot
> >>>
> >>> _______________________________________________
> >>> U-Boot mailing list
> >>> U-Boot at lists.denx.de
> >>> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2011-02-02 23:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-01 19:10 [U-Boot] PCIE supported networking cards? Aaron Williams 2011-02-01 19:15 ` Kumar Gala 2011-02-01 19:19 ` Scott Wood 2011-02-01 21:32 ` Aaron Williams 2011-02-02 4:18 ` Kumar Gala 2011-02-02 23:51 ` Aaron Williams [this message] 2011-02-03 6:05 ` Aaron Williams 2011-02-10 1:25 ` Aaron Williams
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=201102021551.15060.Aaron.Williams@caviumnetworks.com \
--to=aaron.williams@caviumnetworks.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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.