linux-kernel - Re: 2.6.20-rc4-mm1 USB (asix) problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <1168893137.19899.109.camel@dhollis-lnx.sunera.com>
Date:	Mon, 15 Jan 2007 20:32:17 +0000
From:	David Hollis <dhollis@...ehollis.com>
To:	ebuddington@...leyan.edu
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc4-mm1 USB (asix) problem

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 <dhollis@...ehollis.com>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/