Date: Fri, 7 Oct 2011 14:23:10 -0700 From: "David Christensen" <davidch@broadcom.com> To: "pyunyh@gmail.com" <pyunyh@gmail.com>, "Sean Bruno" <seanbru@yahoo-inc.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Pyun YongHyeon <yongari@freebsd.org> Subject: RE: bce(4) with IPMI [puzzling and puzzling] Message-ID: <5D267A3F22FD854F8F48B3D2B523819385F35B561B@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <20111007175137.GA11808@michelle.cdnetworks.com> References: <1317315666.2777.8.camel@hitfishpass-lx.corp.yahoo.com> <1317952651.9892.19.camel@hitfishpass-lx.corp.yahoo.com> <1318004610.27029.1.camel@hitfishpass-lx.corp.yahoo.com> <20111007175137.GA11808@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > so, I cracked open my R410 this morning to see what the Ethernet > chipset > > had for a indentification mark. It is definitely stamped as a > BCM5716, > > so I'm confused. > > > > bce(4) has code to handle the 5716 chipset, but its never being > executed > > AFAIK. What's going on here? > > >=20 > I guess BCE_CHIP_NUM() returns 0x5709 for 5709 and 5716 > controllers. I don't know why bce(4) explicitly checks 5716 from > the BCE_MISC_ID register. Public data sheet indicates CHIP_NUM bits > have 0x5909 for 5716(NetXtremeII-PG203-R pp229). > To me 5716 is virtually the same as 5709 except for not supporting > TOE and iSCSI offloading. >=20 That's a typo then, 5709 and 5716 share the same ASIC ID. Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D267A3F22FD854F8F48B3D2B523819385F35B561B>