From: Peter Korsgaard <jacmet@sunsite.dk>
To: Joseph CHANG <josright123@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, joseph_chang@davicom.com.tw,
josright@hotmail.com
Subject: Re: [PATCH 1/1] net: add dm9620 net usb driver
Date: Sun, 23 Jun 2013 22:00:52 +0200 [thread overview]
Message-ID: <87mwqglhqj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1371730801-2288-1-git-send-email-josright123@gmail.com> (Joseph CHANG's message of "Thu, 20 Jun 2013 20:20:01 +0800")
>>>>> "Joseph" == Joseph CHANG <josright123@gmail.com> writes:
Joseph> DM9620 is an USB2.0 network adapter rather than DM9601 USB1.1. This
Joseph> driver processed the RX data 4 bytes header, TX data 2 bytes header,
Joseph> make the control bit exactly right in PHY write function, and optional
Joseph> IFF_ALLMUTLI bit for RX control.
But dm9601.c already supports the dm9620 based devices. Why another
driver for the same hardware?
Please CC me on dm9601 related patches.
Joseph> Tested good for many platforms, include X86 desktop and ARM embedded.
Joseph> +static struct usb_driver dm9620_driver = {
Joseph> + .name = "dm9620",
Joseph> + .id_table = products,
Joseph> + .probe = usbnet_probe,
Joseph> + .disconnect = usbnet_disconnect,
Joseph> + .suspend = usbnet_suspend,
Joseph> + .resume = usbnet_resume,
Joseph> + .disable_hub_initiated_lpm = 1,
Joseph> +};
Joseph> +
Joseph> +module_usb_driver(dm9620_driver);
Joseph> +
Joseph> +MODULE_AUTHOR("Peter Korsgaard <jacmet@sunsite.dk>");
I'm not the author of this file.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-06-23 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:20 Joseph CHANG
2013-06-23 20:00 ` Peter Korsgaard [this message]
2013-07-03 5:49 ` Joseph Chang
2013-07-05 13:49 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2013-06-19 12:36 Joseph CHANG
2013-06-19 13:20 ` Andi Shyti
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=87mwqglhqj.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=gregkh@linuxfoundation.org \
--cc=joseph_chang@davicom.com.tw \
--cc=josright123@gmail.com \
--cc=josright@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®