mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Hollis <dhollis@davehollis.com>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org, pchang23@sbcglobal.net
Subject: Re: D-Link DUB-E100 Revision B1
Date: Tue, 04 Jul 2006 07:20:43 -0400	[thread overview]
Message-ID: <1152012043.2494.13.camel@dhollis-lnx.sunera.com> (raw)
In-Reply-To: <200607040333.13649.bero@arklinux.org>

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

On Tue, 2006-07-04 at 03:33 +0200, Bernhard Rosenkraenzer wrote:
> 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.
> 

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

That's my guess as well.  It probably has a different GPIO configuration
than the other AX88772 devices.  Unfortunately, I haven't been able to
find out what that configuration is.  A USB trace of the Windows driver
initializing the device would be extremely helpful to determine what is
necessary.  I've tried to contact DLink, but it seems to get in depth
technical info like that may take a lot of work.
  
-- 
David Hollis <dhollis@davehollis.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-07-04 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  1:33 Bernhard Rosenkraenzer
2006-07-04 11:20 ` David Hollis [this message]
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=1152012043.2494.13.camel@dhollis-lnx.sunera.com \
    --to=dhollis@davehollis.com \
    --cc=bero@arklinux.org \
    --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

all inboxes | Powered by JetHome®