public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: linux-kernel@vger.kernel.org
Cc: dhollis@davehollis.com, pchang23@sbcglobal.net
Subject: D-Link DUB-E100 Revision B1
Date: Tue, 4 Jul 2006 03:33:13 +0200	[thread overview]
Message-ID: <200607040333.13649.bero@arklinux.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

Looks like D-Link is getting into the funny "change the chipset but leave the 
product name the same" game again.

DUB-E100 cards up to Revision A4 work perfectly, Revision B1 doesn't work at 
all.

The patch I've attached has the beginnings of a fix; unfortunately this 
trivialty doesn't fix it fully -- with the patch, the module loads, the MAC 
address is detected correctly, the LEDs go on, but pings don't get through 
yet.

After loading the module, dmesg says
eth1: register 'asix' at usb-0000:00:10.3-5, ASIX AX88772 USB 2.0 Ethernet, 
00:80:c8:38:53:a7
usbcore: registered new driver asix
PM: Writing back config space on device 0000:00:0c.0 at offset b (was 3ed173b, 
writing 461025)
PM: Writing back config space on device 0000:00:0c.0 at offset 3 (was 0, 
writing 4010)
PM: Writing back config space on device 0000:00:0c.0 at offset 2 (was 2000000, 
writing 2000003)
PM: Writing back config space on device 0000:00:0c.0 at offset 1 (was 2b00000, 
writing 2b00006)
PM: Writing back config space on device 0000:00:0c.0 at offset 0 (was 3ed173b, 
writing 169c14e4)

Chances are it needs some more messing with the .data and/or .flags 
parameters.

[-- Attachment #2: 2.6.17-D-Link-E100-RevB.patch --]
[-- Type: text/x-diff, Size: 690 bytes --]

--- linux-2.6.17/drivers/usb/net/asix.c.ark	2006-06-30 02:21:07.000000000 +0200
+++ linux-2.6.17/drivers/usb/net/asix.c	2006-06-30 02:23:59.000000000 +0200
@@ -868,7 +868,7 @@
 	USB_DEVICE (0x0846, 0x1040),
 	.driver_info =  (unsigned long) &netgear_fa120_info,
 }, {
-	// DLink DUB-E100
+	// DLink DUB-E100, Revision A
 	USB_DEVICE (0x2001, 0x1a00),
 	.driver_info =  (unsigned long) &dlink_dub_e100_info,
 }, {
@@ -924,6 +924,10 @@
 	USB_DEVICE (0x1557, 0x7720),
 	.driver_info = (unsigned long) &ax88772_info,
-},
+}, {
+	// D-Link DUB-E100 Rev. B
+	USB_DEVICE (0x07d1, 0x3c05),
+	.driver_info = (unsigned long) &ax88772_info,
+},
 	{ },		// END
 };
 MODULE_DEVICE_TABLE(usb, products);

             reply	other threads:[~2006-07-04  1:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  1:33 Bernhard Rosenkraenzer [this message]
2006-07-04 11:20 ` D-Link DUB-E100 Revision B1 David Hollis
2006-07-06 14:17 ` David Hollis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607040333.13649.bero@arklinux.org \
    --to=bero@arklinux.org \
    --cc=dhollis@davehollis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pchang23@sbcglobal.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox