From: "Michael Chan" <mchan@broadcom.com>
To: "Wojtek Sawasciuk" <voyo@no-ip.pl>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"jgarzik@pobox.com" <jgarzik@pobox.com>
Subject: Re: not supported broadcom (?) NIC revision
Date: Fri, 16 Oct 2009 09:30:14 -0700 [thread overview]
Message-ID: <1255710614.20869.335.camel@nseg_linux_HP1.broadcom.com> (raw)
In-Reply-To: <4AD86F2F.90809@no-ip.pl>
On Fri, 2009-10-16 at 06:03 -0700, Wojtek Sawasciuk wrote:
> Hi,
>
> I'v got server with built-in 9 NIC ports. Two ports are not recognized
> by any driver, I suppose it *should* be by tg3 or bnx2
> Below is lspci info, not supported NIC are in slots 00:10.0 and 00:10.2
> strange thing is that this vendor is described as Serverworks, but lspci
> says its Broadcom.
ServerWorks was bought by Broadcom many years ago.
>
> # grep 1166 include/linux/pci_ids.h
> #define PCI_VENDOR_ID_SERVERWORKS 0x1166
>
> Can someone help here ?
>
>
> # lspci
> 00:00.0 Host bridge: Broadcom GCNB-LE Host Bridge (rev 32)
> 00:00.1 Host bridge: Broadcom GCNB-LE Host Bridge
> 00:02.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet
> Controller (rev 05)
> 00:0f.0 ISA bridge: Broadcom CSB5 South Bridge (rev 93)
> 00:0f.1 IDE interface: Broadcom CSB5 IDE Controller (rev 93)
> 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05)
> 00:0f.3 Host bridge: Broadcom CSB5 LPC bridge
>
> 00:10.0 Host bridge: Broadcom CIOB-E I/O Bridge with Gigabit Ethernet
> (rev 12)
> 00:10.2 Host bridge: Broadcom CIOB-E I/O Bridge with Gigabit Ethernet
> (rev 12)
These 2 are bridge devices and no driver is needed. I think the
integrated ethernet device should be behind these bridges showing up as
BCM5704 below.
>
> 02:02.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 02:02.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 02:04.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 02:04.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704
> Gigabit Ethernet (rev 02)
> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704
> Gigabit Ethernet (rev 02)
>
>
> 00:10.0 0600: 1166:0110 (rev 12)
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort+ >SERR- <PERR-
> Capabilities: [60] PCI-X non-bridge device
> Command: DPERE- ERO- RBC=512 OST=8
> Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=bridge
> DMMRBC=512 DMOST=8 DMCRS=8 RSCEM- 266MHz- 533MHz-
>
> 00:10.2 0600: 1166:0110 (rev 12)
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort+ >SERR- <PERR-
> Capabilities: [60] PCI-X non-bridge device
> Command: DPERE- ERO- RBC=512 OST=8
> Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- DC=bridge
> DMMRBC=512 DMOST=8 DMCRS=8 RSCEM- 266MHz- 533MHz-
>
>
>
>
>
>
prev parent reply other threads:[~2009-10-16 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 13:03 not supported broadcom (?) NIC revision Wojtek Sawasciuk
2009-10-16 16:30 ` Michael Chan [this message]
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=1255710614.20869.335.camel@nseg_linux_HP1.broadcom.com \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=voyo@no-ip.pl \
/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;
as well as URLs for NNTP newsgroup(s).