[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200609281307.22923.arnd@arndb.de>
Date: Thu, 28 Sep 2006 13:07:21 +0200
From: Arnd Bergmann <arnd@...db.de>
To: David Brownell <david-b@...bell.net>
Cc: linux-usb-devel@...ts.sourceforge.net,
David Hollis <dhollis@...ehollis.com>, support@...chip.com,
dbrownell@...rs.sourceforge.net, linux-kernel@...r.kernel.org,
Michael Helmling <supermihi@....de>
Subject: Re: [PATCH 1/3] driver for mcs7830 (aka DeLOCK) USB ethernet adapter
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 <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists