On Tue, 2007-01-16 at 17:59 -0500, Eric Buddington wrote:
> On Mon, Jan 15, 2007 at 08:32:17PM +0000, David Hollis wrote:
> > 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.
>
> My hardware is ver. B1.
>
> 0, 2, and 3 all worked for me. 1, as before, does not.
>
That's good to hear. Some other patches have started floating around to
deal with these cases of internal vs. external PHY's and also seem to
work.
> 'rmmod asix' takes a really long time (45-80s) with any setting, and
> sometimes coincides with ksoftirqd pegging (99.9% CPU) for several
> seconds.
This I haven't seen before. Does it occur even when the device is able
to work (using 0 or the like from above)? This may be due to something
else in the USB subsystem or something.
--
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]
