On Mon, 2007-01-15 at 14:50 -0500, Eric Buddington wrote:
> The asix_write_cmd argument in question did indeed change from 0 to 1
> between 2.6.20-rc3-mm1 and -rc4-mm1. I'll change it back, rebuild,
> and test. Probably tomorrow.
>
Interesting. It would really be something if your devices happen to
work better with 0. Wouldn't make much sense at all unfortunately. If
0 works, could you also try setting it to 2 or 3? The PHY select value
is a bit field with the 0 bit being to select the onboard PHY, and 1 bit
being to 'auto-select' the PHY based on link status. The data sheet
indicates that 3 should be the default, but all of the literature I have
seen from ASIX says to write a 1 to it.
And FWIW, that change for setting it to 1 fixed a bunch of broken
adapters, including mine.
--
David Hollis <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
