Date: Thu, 12 Jul 2007 16:11:11 -0700 From: "David Christensen" <davidch@broadcom.com> To: "Paul Schmehl" <pauls@utdallas.edu>, freebsd-net@freebsd.org Subject: RE: Question about bce driver Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD9030477CD64@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <48951B1B7222BB1512D27F8D@utd59514.utdallas.edu> References: <200707121608.l6CG8Sur002750@ambrisko.com> <469657BD.3010204@tomjudge.com> <09BFF2FA5EAB4A45B6655E151BBDD9030477CD0F@NT-IRVA-0750.brcm.ad.broadcom.com> <48951B1B7222BB1512D27F8D@utd59514.utdallas.edu>
index | next in thread | previous in thread | raw e-mail
> Dave, perhaps you could answer my question? > > I'm using the 0.9.6 driver with 6.1 RELEASE. I don't use > jumbo frames, so > the only problem I've experienced is the link state going up and down > occasionally. > > Does the more current driver solve the link state problem? > If it does, can > I use it on 6.1 merely by replacing the three files included > with it? Or > are there includes that refer to other libraries that have > changed since > 6.1? > > Am I better off upgrading the entire system to 6.2? (I > prefer not to do > this, because I have to take the site down to do so. > Patching files and > rebuilding world and kernel only takes the box out of service > during the > reboots. I've never seen the link up/down problem myself, so I don't know if any changes I've made have an effect on it. You would need to change more than the bce driver since it depends upon the brgphy driver under sys/dev/mii which would also need to change. There may be other dependencies upon changes in the 6.2 kernel which would prevent a quick/easy port without some debugging. Davehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?09BFF2FA5EAB4A45B6655E151BBDD9030477CD64>