From: David Miller <davem@davemloft.net>
To: linux@rainbow-software.org
Cc: simon@fire.lp0.eu, dbrownell@users.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] [RFC] introduce cx82310_eth: Conexant CX82310-based ADSL router USB ethernet driver
Date: Wed, 08 Sep 2010 13:11:53 -0700 (PDT) [thread overview]
Message-ID: <20100908.131153.246543999.davem@davemloft.net> (raw)
In-Reply-To: <201009041439.37101.linux@rainbow-software.org>
From: Ondrej Zary <linux@rainbow-software.org>
Date: Sat, 4 Sep 2010 14:39:34 +0200
> This patch introduces cx82310_eth driver - driver for USB ethernet port of
> ADSL routers based on Conexant CX82310 chips. Such routers usually have
> ethernet port(s) too which are bridged together with the USB ethernet port,
> allowing the USB-connected machine to communicate to the network (and also
> internet through the ADSL, of course).
>
> This is my first driver, so please check thoroughly. As there's no protocol
> documentation, it was done with usbsnoop dumps from Windows driver, some
> parts (the commands) inspired by cxacru driver and also other usbnet drivers.
> The driver passed my testing - some real work and also pings sized from 0 to
> 65507 B.
>
> The only problem I found is the ifconfig error counter. When I return 0 (or 1
> but empty skb) from rx_fixup(), usbnet increases the error counter although
> it's not an error condition (because packets can cross URB boundaries). Maybe
> the usbnet should be fixed to allow rx_fixup() to return empty skbs (or some
> other value, e.g. 2)?
>
> The USB ID of my device is 0x0572:0xcb01 which conflicts with some ADSL modems
> using cxacru driver (they probably use the same chipset but simpler
> firmware). The modems seem to use bDeviceClass 0 and iProduct "ADSL USB
> MODEM", my router uses bDeviceClass 255 and iProduct "USB NET CARD". The
> driver matches only devices with class 255 and checks for the iProduct string
> during init. I already posted a patch for the cxacru driver to ignore these
> devices.
>
> Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
Applied, thanks.
prev parent reply other threads:[~2010-09-08 20:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 21:17 [PATCH] [RFC] introduce cx82310_eth: Conexant CX82310-based ADSL router USB ethernet driver Ondrej Zary
2010-09-03 22:14 ` Simon Arlott
2010-09-04 11:57 ` Ondrej Zary
2010-09-04 16:12 ` Simon Arlott
2010-09-04 12:01 ` [PATCH] [RFC] cxacru: ignore ADSL routers Ondrej Zary
2010-09-04 16:30 ` [PATCH] cxacru: ignore cx82310_eth devices Simon Arlott
2010-09-05 4:03 ` Greg KH
2010-09-05 17:01 ` Ondrej Zary
2010-09-05 19:14 ` Greg KH
2010-09-05 20:12 ` Ondrej Zary
2010-09-05 21:04 ` Greg KH
2010-09-06 11:45 ` Simon Arlott
2010-09-06 13:01 ` Ondrej Zary
2010-09-08 20:56 ` Ondrej Zary
2010-09-08 20:12 ` David Miller
2010-09-08 20:52 ` [PATCH v3] " Ondrej Zary
2010-09-09 3:35 ` Greg KH
2010-09-09 6:07 ` David Miller
2010-09-09 6:25 ` Greg KH
2010-09-09 4:29 ` David Miller
2010-09-04 12:39 ` [PATCH v2] [RFC] introduce cx82310_eth: Conexant CX82310-based ADSL router USB ethernet driver Ondrej Zary
2010-09-08 20:11 ` David Miller [this message]
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=20100908.131153.246543999.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=netdev@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/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;
as well as URLs for NNTP newsgroup(s).