LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Buddington <ebuddington@verizon.net>
To: David Hollis <dhollis@davehollis.com>
Cc: ebuddington@wesleyan.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.6.20-rc4-mm1 USB (asix) problem
Date: Mon, 15 Jan 2007 14:50:29 -0500 [thread overview]
Message-ID: <20070115195024.GA8135@pool-71-123-103-45.spfdma.east.verizon.net> (raw)
In-Reply-To: <1168889276.19899.105.camel@dhollis-lnx.sunera.com>
On Mon, Jan 15, 2007 at 07:27:56PM +0000, David Hollis wrote:
> Do you happen to have a Rev. B1 DLink adapter? If so, the only change
> that was put in (PHY Select fix) should actually make these devices
> work. Can you check the top of the ax88772_bind() call in your file and
> see if it has this bit:
>
> if ((ret = asix_write_cmd(dev, AX_CMD_SW_PHY_SELECT,
> 1, 0, 0, buf)) < 0) {
> dbg("Select PHY #1 failed: %d", ret);
> goto out2;
> }
>
>
> That '1' after the AX_CMD_SW_PHY_SELECT was the key to that patch. If
> yours is 1, you could try setting it to 0, though that should make
> things not work. I'd very interested if it made things work for you.
> BTW, the ramifications of this bug were similar to what you describe:
> the interface would come up, look fine but just wouldn't send or receive
> any packets. The hard lock-ups and such are likely from something else.
I don't know the Rev number of the adapter; I can't get to it physically
today, and I don't see it in dmesg.
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.
Thanks.
-Eric
next prev parent reply other threads:[~2007-01-15 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 20:31 Eric Buddington
2007-01-15 19:27 ` David Hollis
2007-01-15 19:50 ` Eric Buddington [this message]
2007-01-15 20:32 ` David Hollis
2007-01-16 22:59 ` Eric Buddington
2007-01-17 12:00 ` David Hollis
2007-01-17 13:54 ` Eric Buddington
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=20070115195024.GA8135@pool-71-123-103-45.spfdma.east.verizon.net \
--to=ebuddington@verizon.net \
--cc=dhollis@davehollis.com \
--cc=ebuddington@wesleyan.edu \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: 2.6.20-rc4-mm1 USB (asix) problem' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).