Re: Broadcom NetXtreme 5703 NIC
Jonathan Disher writes: > On Wed, 11 Dec 2002, Long Le wrote: > > > Hi all, > > > > We installed FreeBSD 4.7 on an IBM eServer machine with an on-board > > copper Broadcom BCM5703X and put two more fiber Broadcom BCM5703X NICs > > into the machine. We used cvs to get the latest update on the stable > > branch yesterday. However, only the copper NIC and one fiber NIC > > come up. The log message says "bge2: MII without any PHY!" for the > > second fiber NIC. Does anyone have any suggestion for us? > > I'm in somewhat the same boat. We just purchased and installed two ASUS > A7V8X motherboards with onboard Broadcom BCM5702 Gigabit ethernet > controllers, and we're having some problems getting them to work. I > cvsup'd to the latest -STABLE last night, and the controller is found, but > it's using ukphy instead of brgphy. Has anyone gotten this controller to New phy support which is required for the BCM5703 was merged from current yesterday. You may which to try a more recent stable and verify that you have rev 1.4.2.10 of sys/dev/mii/miidevs.h Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Broadcom NetXtreme 5703 NIC
> > I'm in somewhat the same boat. We just purchased and installed two ASUS > > A7V8X motherboards with onboard Broadcom BCM5702 Gigabit ethernet > > controllers, and we're having some problems getting them to work. I > > cvsup'd to the latest -STABLE last night, and the controller is found, but > > it's using ukphy instead of brgphy. Has anyone gotten this controller to > > New phy support which is required for the BCM5703 was merged from > current yesterday. You may which to try a more recent stable and > verify that you have rev 1.4.2.10 of sys/dev/mii/miidevs.h Yeah, I'd imagine it was merged in by Paul Saab, who sent me a patch that made things work. I was waiting for him to post that it was in. Thanks. -j To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
transport protocol hook for kqueue
I have been trying to integrate Dave Bailey's bsdproxy with an experimental transport protocol (substitutes for TCP and preserves same API semantics). However, I can't seem to trigger a read event with the new protocol-- the client side socket buffer fills up with data but bsdproxy never gets a read event. I have been able to use simpler proxies (ones that basically pipe between descriptors) successfully. Is there anything special that needs to be done at the transport layer to trigger a kevent read? My protocol calls sorwakeup() at the appropriate times-- I had thought that would be enough and that kqueue would be indifferent to the underlying transport protocol implementation. Nothing seems apparent in the TCP code, however. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
