Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Jun 2012 13:45:44 -0400
From:      Rick Miller <vmiller@hostileadmin.com>
To:        Devin Teske <dteske@freebsd.org>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: How do I determine support for $xx?
Message-ID:  <CAHzLAVGBxPsOfVHc=M%2B7Kmw1x%2BZZ6rQhnaxGR3he4KEFf4DuYA@mail.gmail.com>
In-Reply-To: <1FCB8643-87F8-4B89-A5DC-1082B20F8682@fisglobal.com>
References:  <CAHzLAVHJL-%2B5Aofcf%2BG8p19ZQX0s5QA=M4t5D7Hz%2B-Fwuoqkgg@mail.gmail.com> <7BDA2790-A852-4BA1-B6D3-BCA3C465A341@fisglobal.com> <1FCB8643-87F8-4B89-A5DC-1082B20F8682@fisglobal.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Matthew/Devin,  Thanks for the feedback.

After I sent this email, I determined that the Intel i350 is indeed
supported as a machine I built with FreeBSD was utilizing this NIC.

I've tried the BCM5719 with stable/8 (5/21/2012) and it kernel panics
when the interface is configured.  I was told by a source contributor
that the BCM5720 does not work (confirmed as recently as within the
last week), but I've not tested it.  I'm just passing this on as
information...I don't expect any feedback with regards to this.

On Fri, Jun 8, 2012 at 1:06 PM, Devin Teske <devin.teske@fisglobal.com> wro=
te:
>
> On Jun 8, 2012, at 9:45 AM, Devin Teske wrote:
>
>> Hi Rick (!),
>>
>> On Jun 8, 2012, at 8:07 AM, Rick Miller wrote:
>>
>
> [snip]
>
>>>
>>> I browsed the source and found many references to the BCM5719 and
>>> BCM5720. =A0However, I am unfamiliar enough with driver programming in =
C
>>> to identify if a controller is fully supported.
>>>
>>
>
> [snip]
>
>> If you were running, say, 8.0-R, even if you have the bge(4) driver load=
ed, you would see this in /var/run/dmesg.boot:
>>
>> =A0 =A0 =A0 pciN: <unknown card> (vendor=3D0x1106, dev=3D0x165f) at X.Y
>>
>
> Correction, (specific to BCM5720) you'd see:
>
> =A0 =A0 =A0 =A0pciN: <unknown card> (vendor=3D0x14e4, dev=3D0x165f) at X.=
Y
>
> Which, btw, you can confirm to yourself by executing the following within=
 8.3-R (with attached bge(4)):
>
> $ pciconf -lv | awk '/^bge/{print $1,$4}'
> bge0@pciN:A:B:C: chip=3D0x165f14e4
>
> Otherwise, you can see an unknown (non-working bge(4)) Broadcom BCM5720 h=
ardware by executing (on 8.0-R for example):
>
> $ grep unk /var/run/dmesg.boot | grep 0x14e4
> pciN: <unknown card> (vendor=3D0x14e4, dev=3D0x165f) at X.Y
>
> NOTE: On a system where all hardware is probed/attached, "grep unk /var/r=
un/dmesg.boot" should not produce any results. In this case, pciconf is you=
r tool for probing vendor/device IDs.
>
>
>> NOTE: Insert random numbers for "N", and "X.Y"
>>
>> How you know that 8.3-R's bge(4) driver supports the BCM5720 is because =
this source file:
>>
>> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bgereg.h?annota=
te=3D1.83.2.35.2.1
>>
>> NOTE: I specifically pointed you at CVS instead of SVN so that you can s=
ee the version tagged for 8.3-R
>>
>> Specifically, this line:
>>
>> =A0 =A0 =A0 2309: #define =A0 =A0 =A0 =A0BCOM_DEVICEID_BCM5720 =A0 =A0 =
=A0 =A0 =A0 0x165F
>
> [snip]
>
> --
> Devin
>
> _____________
> The information contained in this message is proprietary and/or confident=
ial. If you are not the intended recipient, please: (i) delete the message =
and all copies; (ii) do not disclose, distribute or use the message in any =
manner; and (iii) notify the sender immediately. In addition, please be awa=
re that any message addressed to our domain is subject to archiving and rev=
iew by persons other than the intended recipient. Thank you.



--=20
Take care
Rick Miller



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVGBxPsOfVHc=M%2B7Kmw1x%2BZZ6rQhnaxGR3he4KEFf4DuYA>