From: "Matt Carlson" <mcarlson@broadcom.com>
To: "Francesco Piccinno" <stack.box@gmail.com>
Cc: "Matthew Carlson" <mcarlson@broadcom.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"Benjamin Li" <benli@broadcom.com>,
"Michael Chan" <mchan@broadcom.com>
Subject: Re: [Bugme-new] [Bug 42132] New: Support BCM5750M in tg3
Date: Thu, 1 Sep 2011 18:04:31 -0700 [thread overview]
Message-ID: <20110902010431.GA5105@mcarlson.broadcom.com> (raw)
In-Reply-To: <CAA7bCn6DRmoqhHGBOAkaDqCdiYwrjPGuaYcck7n4+o3Lm10w2g@mail.gmail.com>
It's showing up on lspci as a PCIe device, so it can't be the 5750M.
The bcm5750M is a pci device.
I'm wondering if bootcode is failing. Do you see any messages in your
syslogs that say "No firmware running"?
Can you post the output of 'ethtool -i ethX'?
On Thu, Sep 01, 2011 at 05:48:50PM -0700, Francesco Piccinno wrote:
> Yes sure.
>
> # lspci -vvv -s 08:00.0
> 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5750M
> Gigabit Ethernet
> Subsystem: Broadcom Corporation NetXtreme BCM5750M Gigabit Ethernet
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 10
> Region 0: Memory at f4100000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [48] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
> Capabilities: [50] Vital Product Data
> pcilib: sysfs_read_vpd: read failed: Connection timed out
> Not readable
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Address: 5149526521410124 Data: 8b60
> Capabilities: [d0] Express (v1) Endpoint, MSI 00
> DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
> RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <4us, L1 <64us
> ClockPM- Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive-
> BWMgmt- ABWMgmt-
> Capabilities: [100 v1] Advanced Error Reporting
> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
> MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
> MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
> AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
> Capabilities: [13c v1] Virtual Channel
> Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
> Arb: Fixed- WRR32- WRR64- WRR128-
> Ctrl: ArbSelect=Fixed
> Status: InProgress-
> VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
> Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
> Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
> Status: NegoPending- InProgress-
> Capabilities: [160 v1] Device Serial Number 00-00-00-ff-fe-00-00-00
>
> Serial number is CND71700K6.
> --
> Best regards,
> Francesco Piccinno
>
>
>
> On Fri, Sep 2, 2011 at 2:06 AM, Matt Carlson <mcarlson@broadcom.com> wrote:
> > On Thu, Sep 01, 2011 at 04:40:11PM -0700, Andrew Morton wrote:
> >>
> >> (switched to email. ??Please respond via emailed reply-to-all, not via the
> >> bugzilla web interface).
> >>
> >> On Wed, 31 Aug 2011 18:18:40 GMT
> >> bugzilla-daemon@bugzilla.kernel.org wrote:
> >>
> >> > https://bugzilla.kernel.org/show_bug.cgi?id=42132
> >> >
> >> > ?? ?? ?? ?? ?? ??Summary: Support BCM5750M in tg3
> >> > ?? ?? ?? ?? ?? ??Product: Drivers
> >> > ?? ?? ?? ?? ?? ??Version: 2.5
> >> > ?? ?? Kernel Version: 3.0.3
> >> > ?? ?? ?? ?? ?? Platform: All
> >> > ?? ?? ?? ?? OS/Version: Linux
> >> > ?? ?? ?? ?? ?? ?? ?? Tree: Mainline
> >> > ?? ?? ?? ?? ?? ?? Status: NEW
> >> > ?? ?? ?? ?? ?? Severity: normal
> >> > ?? ?? ?? ?? ?? Priority: P1
> >> > ?? ?? ?? ?? ??Component: Network
> >> > ?? ?? ?? ?? AssignedTo: drivers_network@kernel-bugs.osdl.org
> >> > ?? ?? ?? ?? ReportedBy: stack.box@gmail.com
> >> > ?? ?? ?? ?? Regression: Yes
> >> >
> >> >
> >> > I have a notebook (HP TC4400) which has a BCM5750 ethernet card inside. The
> >> > ouput of lspci is:
> >> >
> >> > 08:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5750M
> >> > Gigabit Ethernet [14e4:167c]
> >> >
> >> > Commit 67b284d476bcb3d100e946da23d6cf9acfd0465c removed the support for this
> >> > device.
> >> >
> >>
> >> 67b284d476bcb3d100 says "These devices were never released to the public".
> >>
> >> > I wish to have the support for this network card back again. Thanks!
> >>
> >> oops ;)
> >
> > Really? ??All the TC4400 documentation I find says it uses a bcm5753M on a
> > PCIe bus. ??Can you post the full output of 'lspci -vvv -s 08:00.0' ?
> >
> >
>
next prev parent reply other threads:[~2011-09-02 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42132-10286@https.bugzilla.kernel.org/>
2011-09-01 23:40 ` [Bugme-new] [Bug 42132] New: Support BCM5750M in tg3 Andrew Morton
2011-09-02 0:02 ` Francesco Piccinno
2011-09-02 0:06 ` Matt Carlson
2011-09-02 0:48 ` Francesco Piccinno
2011-09-02 1:04 ` Matt Carlson [this message]
2011-09-02 1:14 ` Francesco Piccinno
2011-09-02 1:25 ` Matt Carlson
2011-09-02 9:20 ` Francesco Piccinno
2011-09-02 17:43 ` Matt Carlson
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=20110902010431.GA5105@mcarlson.broadcom.com \
--to=mcarlson@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=benli@broadcom.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=stack.box@gmail.com \
/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.