From: Mark Lord <kernel@teksavvy.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: asix usb network driver: nfg
Date: Wed, 26 Oct 2011 21:23:15 -0400 [thread overview]
Message-ID: <4EA8B283.3010105@teksavvy.com> (raw)
In-Reply-To: <20111026.194045.2019668159403582571.davem@davemloft.net>
On 11-10-26 07:40 PM, David Miller wrote:
> From: Mark Lord <kernel@teksavvy.com>
> Date: Wed, 26 Oct 2011 19:36:18 -0400
>
>> So, the in-kernel asix driver seems badly broken for a lot of hardware,
>> and the vendor driver also has a slight race somewhere that is cured
>> by enabling debug logging.
>>
>> Is there an asix driver maintainer, or anyone else with the time
>> to step up and try to fix these issues?
>
> The issues you speak of are well known for at least two years but
> nobody wants to work on this.
Okay, that's useful to know.
I think I may be able to get some funding to take a crack at perhaps
figuring out the "DEBUG" race thing in the vendor's copy of the driver,
since that one seems to be in the better shape of the two.
Any strong advance objections to replacing the in-kernel version
with a (fixed) vendor open source version?
It appears that the two share a common heritage, but somewhere along the
line the in-kernel one stopped being maintained as well as the external one.
Assuming I get approval, I'll try and fix the vendor version,
tidy it up to pass checkpatch.pl with flying colours,
and then submit the resulting diff to you.
Hopeless, or would you perhaps accept such a wholesale change?
Thanks David.
next prev parent reply other threads:[~2011-10-27 1:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 23:36 asix usb network driver: nfg Mark Lord
2011-10-26 23:40 ` David Miller
2011-10-27 1:23 ` Mark Lord [this message]
2011-10-27 2:17 ` David Miller
2011-10-27 18:48 ` Mark Lord
2011-11-02 19:36 ` [PATCH] drivers/net/usb/asix: resync from vendor's copy Mark Lord
2011-11-02 19:48 ` Mark Lord
2011-11-02 20:42 ` Ben Hutchings
2011-11-02 22:44 ` Mark Lord
2011-11-09 16:25 ` Mark Lord
2011-11-09 16:34 ` Ben Hutchings
2011-11-09 16:47 ` Mark Lord
2011-11-09 16:57 ` Mark Lord
2011-11-09 17:20 ` Mark Lord
2011-11-09 17:31 ` Ben Hutchings
2011-11-09 17:40 ` Mark Lord
2011-11-09 17:48 ` Ben Hutchings
2011-11-09 18:22 ` Mark Lord
2011-12-05 14:41 ` Mark Lord
2011-12-05 15:18 ` Ben Hutchings
2011-12-06 12:44 ` Mark Lord
2011-12-06 17:45 ` Ben Hutchings
2011-12-07 16:21 ` Mark Lord
2011-12-07 16:27 ` Ben Hutchings
2011-12-07 16:59 ` Mark Lord
2011-12-07 17:03 ` Ben Hutchings
2011-11-07 16:09 ` Michal Marek
2011-11-09 17:31 ` [PATCH v2] " Mark Lord
2011-11-09 17:41 ` Mark Lord
2011-11-09 17:43 ` Mark Lord
2011-11-09 17:47 ` Ben Hutchings
2011-11-09 18:27 ` Mark Lord
2011-11-09 17:49 ` [PATCH v3] " Mark Lord
2011-11-10 14:01 ` [PATCH v2] " Mark Lord
2011-11-10 16:54 ` Grant Grundler
2011-11-10 20:17 ` Mark Lord
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=4EA8B283.3010105@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.