Date: Sun, 17 Jun 2007 23:23:09 -0400 From: Randall Stewart <rrs@cisco.com> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: Linksys USB200M Message-ID: <4675FA9D.8010507@cisco.com> In-Reply-To: <200706181244.11235.doconnor@gsoft.com.au> References: <4675F1FF.3030505@cisco.com> <200706181244.11235.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel O'Connor wrote: > On Monday 18 June 2007 12:16, Randall Stewart wrote: > >>it in to my leading bleeding edge current and I see: >>ugen0: <vendor 0x13b1 product 0x0018, class 255/255, rev 2.00/0.01, >>addr 2> on uhub4 > > > According to usbdevs a USB200M has a device ID of 0x2226 and a vendor ID > of 0x066b. > > Linksys have probably changed the chip they use without changing the > model name :( Since you work there maybe you can go yell at someone ;) ahh.. but we are completely seperate.. so there is no one to yell at :-) > > From the Linux driver it looks like an ASIX AX88178 10/100/1000 > > Interestingly I can't actually find who uses the vendor ID of 0x066b.. > (0x13b1 is CISCO/Linksys) > > I don't think you'll get it working without cutting some code. > > On the plus side the data sheet is readily available.. > http://www.asix.com.tw/FrootAttach/datasheet/AX88178_datasheet_Rev11.pdf > Yeah... the thing is its a 0x0018.. which is unlisted in the usb devices.. In the driver it has { USB_VENDOR_LINKSYS2, USB_PRODUCT_LINKSYS2_USB200M }, For the linksys code which is: #define USB_VENDOR_LINKSYS2 0x077b #define USB_PRODUCT_LINKSYS2_USB200M 0x2226 Hmm.. searching around there is mention of hacking a tivo with this critter.. but and that it is an AxE driver.. let me dig a bit deeper. R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4675FA9D.8010507>