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. > In the ax88772_bind() function, there is a spot where we read the PHYSID1 and validate that it's 0x003b. If it's not, we bail out and don't complete the initialization. As it turns out, with the B1 rev, they use an external PHY that has a different identifier so this check is no longer valid. Simply removing that check, or getting rid of the "goto out2;" part, the device appears to operate with no issues. -- David Hollis <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- D-Link DUB-E100 Revision B1
- From: Bernhard Rosenkraenzer <[email protected]>
- D-Link DUB-E100 Revision B1
- Prev by Date: Re: AVR32 architecture patch against Linux 2.6.18-rc1 available
- Next by Date: [git pull] jfs update
- Previous by thread: Re: D-Link DUB-E100 Revision B1
- Next by thread: PROBLEM: crashes of 2.4.31hf2.6 kernel (oops included)
- Index(es):