Zt6688 Source?

[Capn_Fish]

After foobaring my DM9601 USB-to-ethernet adapter (never even got to try it ), I ordered another one that I thought was just like it, but uses a zt6688 chip, which I don't even know who makes it. Does anybody here know who makes it and/or where I can get the Linux driver source?

Thanks.

[pelrun]

Actually, you still have a dm9601, just with different USB ids. I built a new beta3 driver which includes the other ids (one of which is 0x6688):

https://www.oesf.org/forums/index.php?showt...ndpost&p=164466

It should be trivial to patch the source to add new ids for a beta4+ driver; there are macros at the bottom of the driver header file.

[Capn_Fish]

Unfortunately, I have a few issues:

-I am using a 2.6 kernel, so your 2.4 driver won't work.

-The chip says "ZT6688" on it, so I don't think it's a dm9601 chip. It also doesn't say DaviCom on it, and has a funny logo that looks lik "ZT"

The whole text on the chip is:

(ZT logo)
ZT6688
0646S
MM26G6P

If it helps.

[Capn_Fish]

Ah...I see what you mean. It's a rebranded DM9601 chip. I saw a patch for the kernel driver to add in support, but I don't see the same thing in the source I have... Any hints?

[pelrun]

There should be a list of supported usb id's somewhere in the driver - searching for 0x9601 is probably going to get you there pretty quickly - all you need to do is add the id for your particular dongle and recompile.

[Capn_Fish]

Any other info I need to know? Do I need to get the name exactly right? Would it be in the .c file or the .h file?

I tried once and it didn't work, so I"ll give it another shot...

[Capn_Fish]

I think I got it recognized (when I plug it in it loads the DM9601 driver), but I can't get it to work. I've been trying:

Code: [Select]

ifconfig eth0 up
dhcpcd eth0
But it just sits there, then shuts down eth0. Am I doing something wrong? Or is the driver not working?

Any help would be much appreciated.

[pelrun]

What does dmesg say?

[Capn_Fish]

If I plug it in without modprobing DM9601, it says new USB device found, loading DM9601 or, something to that effect. If I modprobe it before inserting the USB device, it doesn't show anything. I can get the specifics if necessary.

[Capn_Fish]

OK, here's the relevent part of dmesg:

Code: [Select]

usbcore: registered new driver usbfs
usbcore: registered new driver hub
pxa27x-ohci pxa27x-ohci: PXA27x OHCI
pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usb 1-2: new full speed USB device using pxa27x-ohci and address 2
usb 1-2: configuration #1 chosen from 1 choice
/mnt/ide2/files/dm9601-2.6/dm9601.c: /mnt/ide2/files/dm9601-2.6/dm9601.c: v0.0.6 2001/05/24 (C) 1999-2000 Petko Manolov (petkan@dce.bg)
/mnt/ide2/files/dm9601-2.6/dm9601.c: eth%d: Davicom USB-100
usbcore: registered new driver dm9601
pxafb: Power mode 0
pxafb: Power mode 480
No interface is brought up automatically, but I can bring up eth0, and it has a hwaddress, but dhcpcd-ing it hangs for a while then fails.

Any ideas?

Thanks.

[pelrun]

That "eth%d" certainly looks suspicious; a printf gone wrong. Wonder if it's also trying to use that string to configure the ethernet support?

[Capn_Fish]

Hmm...I don't see "eth%d" in dm9601.c or .h, but it doesn't look right.

[Capn_Fish]

No ideas?

[pelrun]

I don't use 2.6 or the drivers, so I'm pretty much stumped by what you're seeing.

[Capn_Fish]

Anybody else have any ideas? Would e-mailing Davicom help (since the ZT6688 is a rebranded DM9601)?