SEO

#1 (**permalink**) 02-16-2008, 07:24 AM

Is there a way to force a NIC driver onto a NIC that is unknown to
OpenBSD?

I ask this question because I have a USB Ethernet adapter that returns a
vendor/device ID unknown to OpenBSD but it's linux driver source shows
it is based on Davicom DM9601.

#2 (**permalink**) 02-16-2008, 07:24 AM

M.K. <mk38@ozemail.com.au> wrote:
> Is there a way to force a NIC driver onto a NIC that is unknown to
> OpenBSD?
>
> I ask this question because I have a USB Ethernet adapter that returns a
> vendor/device ID unknown to OpenBSD but it's linux driver source shows
> it is based on Davicom DM9601.

This is usually not too hard[1] to patch into the source if the original is
supported. However, there is, AFAIK, no way to force it otherwise.

Joachim

[1] Although I wouldn't necessarily know how...

#3 (**permalink**) 02-16-2008, 07:24 AM

M.K. wrote:
> Is there a way to force a NIC driver onto a NIC that is unknown to
> OpenBSD?
>
> I ask this question because I have a USB Ethernet adapter that returns a
> vendor/device ID unknown to OpenBSD but it's linux driver source shows
> it is based on Davicom DM9601.
>

I think you should be able to do this with mknod().

#4 (**permalink**) 02-16-2008, 07:24 AM

>> Is there a way to force a NIC driver onto a NIC that is unknown to
>> OpenBSD?
>>
>> I ask this question because I have a USB Ethernet adapter that returns a
>> vendor/device ID unknown to OpenBSD but it's linux driver source shows
>> it is based on Davicom DM9601.
>>
>
> I think you should be able to do this with mknod().

Nonsense. First, ethernet interfaces do not have any device nodes in
/dev since the socket API does not need them; second, whatever device
node you'll create will still end up in the driver corresponding to its
major number, and if it can not cope with your hardware, this will not
change anything.

#5 (**permalink**) 02-16-2008, 07:24 AM

jKILLSPAM.schipper@math.uu.nl wrote:

> M.K. <mk38@ozemail.com.au> wrote:
> > Is there a way to force a NIC driver onto a NIC that is unknown to
> > OpenBSD?
> >
> > I ask this question because I have a USB Ethernet adapter that returns a
> > vendor/device ID unknown to OpenBSD but it's linux driver source shows
> > it is based on Davicom DM9601.
>
> This is usually not too hard[1] to patch into the source if the original is
> supported. However, there is, AFAIK, no way to force it otherwise.
>
> Joachim
>
> [1] Although I wouldn't necessarily know how...

To follow up further:

This is the OpenBSD (3.9/i386) dmesg for the device:
ugen0 at uhub0 port 1
ugen0: WK-668 USB NIC HenTong Tech CO., LTD, rev 1.10/1.01, addr 2
(The GENERIC kernel uses the ugen driver for unknown USB devices. Unfortunately
ugen is not an Ethernet driver so i can't run ifconfig on ugen0)

This is the Linux dmesg for the device (showing vendor/product ID):
usb.c: USB device 2 (vend/prod 0xa46/0x668) is not claimed by any active
driver.
(Linux is handy for getting info like that.)

I have seen the chip & it is a DAVICOM DM9601E.

The kernel driver source (if_udav.c) has a disabled generic driver that uses
0x9601 as prod ID:
#if 0
/* DAVICOM DM9601 Generic? */
/* XXX: The following ids was obtained from the data sheet. */
{{ 0x0a46, 0x9601 }, 0},
#endif

I will try adding this below it:
#if 1
/* HenTong WK-668 */
{{ 0x0a46, 0x0668 }, 0},
#endif

If this ugly works, I may consider making a proper kernel source contribution,
although I wouldn't know how...

#6 (**permalink**) 02-16-2008, 07:24 AM

In article <44CA4586.77A75AA5@ozemail.com.au>,
M.K. <mk38@ozemail.com.au> wrote:
>Is there a way to force a NIC driver onto a NIC that is unknown to
>OpenBSD?
>
>I ask this question because I have a USB Ethernet adapter that returns a
>vendor/device ID unknown to OpenBSD but it's linux driver source shows
>it is based on Davicom DM9601.

Should be quite easy to do. All based vendor/device buses have tables mapping
IDs to drivers (/usr/src/sys/dev/usb/usbdevs in this case).

Then the specific driver does some further magic to make sure it's matching
the right device (in that case, look at if_udav.c, the udav_lookup macro
and the list udav_devs).

If you set up your ethernet adapter that way, and it works, it's probably
worth sending us a detailed patch, preferably to tech@openbsd.org...

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Can I force a driver onto an unknown NIC?