On 12/18/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
From usbdevs:
/*
* List of known USB vendors
*
* USB.org publishes a VID list of USB-IF member companies at
* http://www.usb.org/developers/tools
* Note that it does not show companies that have obtained a Vendor ID
* without becoming full m
In message: <[EMAIL PROTECTED]>
"Dan Frohlich" <[EMAIL PROTECTED]> writes:
: At the top of which file? In there is no vendor info for 0x13b1 in usbdevs.
>From usbdevs:
/*
* List of known USB vendors
*
* USB.org publishes a VID list of USB-IF member companies at
* http://www.usb.org
Thanks for the tips Bernd I'll comment on each in turn.
I now understand that this is new hardware although I did not at the time of
my post. I have been reading the OpenBSD axe driver which apparently has
included support for these devices for over a year now according to the CVS
log.
I am not
At the top of which file? In there is no vendor info for 0x13b1 in usbdevs.
OpenBSD usbdevs has: vendor CISCOLINKSYS 0x13b1 Cisco-Linksys
I called is LINKSYS4 trying to follow the pattern that was established in
usbdevs, but now I'm using the line from the OpenBSD usbdevs file.
-Dan
On 12/17/06
On Sun, Dec 17, 2006 at 03:42:59PM -0500, Dan Frohlich wrote:
> Here is a link to the existing defect usb/106621 btw.
> http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/106621
And as it said: DLink sold diffenrent hardware under the same name.
This is in fact a new device requiring new driver and n
In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: On Sun, Dec 17, 2006 at 04:24:21PM -0500, Dan Frohlich wrote:
: > Here is what I did to try to get the linksys 200m running:
: >
: > in if_axe.c:
: > /* product LINKSYS2 USB200M 0x2226 USB 2.0 10/100 ethern
On Sun, Dec 17, 2006 at 04:24:21PM -0500, Dan Frohlich wrote:
> Here is what I did to try to get the linksys 200m running:
>
> in if_axe.c:
> /* product LINKSYS2 USB200M 0x2226 USB 2.0 10/100 ethernet */
> product LINKSYS4 USB200M0x0018 USB 2.0 10/100 ethernet rev 2.00
> /0.01
>
> i
Here is what I did to try to get the linksys 200m running:
in if_axe.c:
/* product LINKSYS2 USB200M 0x2226 USB 2.0 10/100 ethernet */
product LINKSYS4 USB200M0x0018 USB 2.0 10/100 ethernet rev 2.00
/0.01
in usbdevs:
/* { USB_VENDOR_LINKSYS2, USB_PRODUCT_LINKSYS2_USB200M },*/
Here is a link to the existing defect usb/106621 btw.
http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/106621
On 12/17/06, Dan Frohlich <[EMAIL PROTECTED]> wrote:
Thanks for the reply. Both the dlink and linksys are listed as supported
hardware. Getting the dlink defect fixed would be the best
Thanks for the reply. Both the dlink and linksys are listed as supported
hardware. Getting the dlink defect fixed would be the best solution from my
opinion. I will buy new adapters if I need to, but I would like to avoid
buying more adapters that are supposed to be supported but do not actually
w
On Sat, 16 Dec 2006 15:14:37 -0500
Dan Frohlich <[EMAIL PROTECTED]> wrote:
> any usb ethernet devices currently on the market which do work with
> 6.2rc1 ?
The ural(4) man page does have a list of supported devices. The same
does the axe(4) man page, but you probably already know that.
Using 'apr
Synopsis: USB HP printer is not detected by kernel when ACPI enabled.
Responsible-Changed-From-To: freebsd-bugs->freebsd-usb
Responsible-Changed-By: remko
Responsible-Changed-When: Sun Dec 17 13:03:15 UTC 2006
Responsible-Changed-Why:
Reassign to USB team.
http://www.freebsd.org/cgi/query-pr.cgi
12 matches
Mail list logo
