From: David Brownell <david-b@pacbell.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-usb-devel@lists.sourceforge.net,
David Hollis <dhollis@davehollis.com>,
support@moschip.com, dbrownell@users.sourceforge.net,
linux-kernel@vger.kernel.org, Michael Helmling <supermihi@web.de>
Subject: Re: [PATCH 1/3] driver for mcs7830 (aka DeLOCK) USB ethernet adapter
Date: Wed, 27 Sep 2006 18:28:57 -0700 [thread overview]
Message-ID: <200609271828.58205.david-b@pacbell.net> (raw)
In-Reply-To: <200609170102.50856.arnd@arndb.de>
On Saturday 16 September 2006 4:02 pm, Arnd Bergmann wrote:
> This driver adds support for the DeLOCK USB ethernet adapter
> and potentially others based on the MosChip MCS7830 chip.
>
> It is based on the usbnet and asix drivers as well as the
> original device driver provided by MosChip, which in turn
> was based on the usbnet driver.
>
> It has been tested successfully on an OHCI, but interestingly
> there seems to be a problem with the mcs7830 when connected to
> the ICH6/EHCI in my thinkpad: it keeps receiving lots of
> broken packets in the RX interrupt. The problem goes away when
> I'm using an active USB hub, so I assume it's not related to
> the device driver, but rather to the hardware.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
... yes, I'd assume it's a hardware issue too. Try different
cables; if you have a fast 'scope, you might see what kind of
eye diagram you get. The hub might improve the signal quality.
Do you know how the remote wakeup mechanism works for this chip?
It'd be interesting to see "usbnet" be taught how to autosuspend
chips which will wake up the USB host when they get the right
kind of packet ... for example, passing the multicast/broadcast
filter, or addressed directly to that adapter.
Such an autosuspend mechanism would let the host controller stop
polling a mostly-idle network link, getting rid of one source of
periodic DMA transfers and thus allowing deeper sleep states for
many x86 family CPUs. And also, I'd expect, giving fewer
opportunities for those broken RX packets. :)
- Dave
next prev parent reply other threads:[~2006-09-28 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 23:02 [PATCH 1/3] driver for mcs7830 (aka DeLOCK) USB ethernet adapter Arnd Bergmann
2006-09-28 1:28 ` David Brownell [this message]
2006-09-28 11:07 ` Arnd Bergmann
2006-10-07 18:58 ` Arnd Bergmann
2006-10-07 20:16 ` [linux-usb-devel] " David Brownell
2006-10-08 2:39 ` Greg KH
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=200609271828.58205.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=arnd@arndb.de \
--cc=dbrownell@users.sourceforge.net \
--cc=dhollis@davehollis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=supermihi@web.de \
--cc=support@moschip.com \
/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