10Mbps+ throughput usb based ethernet recommendation

[Pyun YongHyeon]

On Wed, Mar 24, 2010 at 02:58:27PM -0700, Pyun YongHyeon wrote:
> On Wed, Mar 24, 2010 at 02:42:30PM -0700, Pyun YongHyeon wrote:
> > On Wed, Mar 24, 2010 at 06:16:21PM -0300, Nenhum_de_Nos wrote:
> > > 
> > > On Tue, March 23, 2010 22:01, Pyun YongHyeon wrote:
> > 
> > [...]
> > 
> > > >> Just adding info, I keep getting these outputs from ifconfig:
> > > >>
> > > >> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> > > >> 1500
> > > >> 	ether 00:11:50:e7:39:e9
> > > >> 	inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
> > > >> 	media: Ethernet autoselect (1000baseT <full-duplex>)
> > > >> 	status: active
> > > >> and:
> > > >> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
> > > >> 1500
> > > >> 	ether 00:11:50:e7:39:e9
> > > >> 	inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
> > > >> 	media: Ethernet autoselect (100baseTX <full-duplex,hw-loopback>)
> > > >                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > >> 	status: active
> > > >>
> > > >> and this keeps repeating over and over. iperf and on the other end an
> > > >
> > > > Maybe this is real problem. It seems PHY have trouble to establish
> > > > link. This is FreeBSD stable/8 right?
> > > 
> > > yes. on 7.2 is even worse :(
> > > 
> > > > Would you show me the output of "devinfo -rv| grep phy"?
> > > 
> > > /usr/home/matheus]$ devinfo -rv| grep phy
> > >                   ukphy0 pnpinfo oui=0x1e model=0x14 rev=0x9 at phyno=1
> > 
> > axe(4) requires correct resolved speed/link status reported from
> > PHY driver. Otherwise it will incorrectly reprogram some registers
> > and this can result in unexpected result.
> > The OUI 0x1e from the above looks odd and I'm not aware of any PHY
> > vendors that reports such OUI. Because FreeBSD does not strictly
> > follows OUI decoding defined by IEEE it's also possible that
> > FreeBSD incorrectly showed wrong OUI. What is your USB ethernet
> > controller model?
> > 
> 
> Please try this patch and let me know the output on your console.
> It will show you "XXX ID1 = 0xYYYY, ID2 = 0xZZZZ".
> 

Use this patch instead of previous one.
-------------- next part --------------
Index: sys/dev/mii/ukphy.c
===================================================================
--- sys/dev/mii/ukphy.c	(revision 205608)
+++ sys/dev/mii/ukphy.c	(working copy)
@@ -141,6 +141,8 @@
 		device_printf(dev, "OUI 0x%06x, model 0x%04x, rev. %d\n",
 		    MII_OUI(ma->mii_id1, ma->mii_id2),
 		    MII_MODEL(ma->mii_id2), MII_REV(ma->mii_id2));
+	device_printf(dev, "XXX ID1 = 0x%04x, ID2 = 0x%04x\n",
+	    ma->mii_id1, ma->mii_id2);
 
 	sc->mii_inst = mii->mii_instance;
 	sc->mii_phy = ma->mii_phyno;