public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: David Brownell <david-b@pacbell.net>
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: Thu, 28 Sep 2006 13:07:21 +0200	[thread overview]
Message-ID: <200609281307.22923.arnd@arndb.de> (raw)
In-Reply-To: <200609271828.58205.david-b@pacbell.net>

On Thursday 28 September 2006 03:28, David Brownell wrote:
> ... 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.

Unfortunately, I don't have anything I could use to test this.

> 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.  :)

No, don't know. I did not find anything about this in the public
spec.

	Arnd <><

  reply	other threads:[~2006-09-28 11:07 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
2006-09-28 11:07   ` Arnd Bergmann [this message]
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=200609281307.22923.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=david-b@pacbell.net \
    --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