Thomas Schäfer writes:
> Hi Bjørn,
>
> it seems to me that this patch solved some problems.
> ( time out )
Thanks for testing. Let me know if you hit similar issues. There
might still be some we haven't found.
> Some other problems "introduced" in 3.13 are still there.
>
> mbim wwan and dhcp
On Sun, Dec 22, 2013 at 1:47 AM, Greg KH wrote:
> On Sat, Dec 21, 2013 at 08:19:36PM +0800, Yingchun Li wrote:
>> Hi, I have a box presents to PC as a CDC-ACM device. And I write an simple
>> Application to write data to the box by ttyACM0.
>> The application is a loop that write the data to box,
Any response?
> -Original Message-
> From: Hayeswang [mailto:hayesw...@realtek.com]
> Sent: Wednesday, November 20, 2013 5:31 PM
> To: net...@vger.kernel.org
> Cc: nic_swsd; linux-ker...@vger.kernel.org;
> linux-usb@vger.kernel.org; Hayeswang
> Subject: [PATCH net v5 0/4] r8152 bug fixe
On Fri, Dec 20, 2013 at 10:40:01AM +, David Laight wrote:
> > From: Peter Chen
> > Sent: 20 December 2013 07:52
> > Change "high speed" to "HS"
> > Change "non-high speed" to "FS/LS"
> >
> > Implementation of notify_suspend and notify_resume will be different
> > according to mxs_phy_data->fla
On Sun, 22 Dec 2013, Matthias [ISO-8859-1] Bl�sing wrote:
> To give some reference: This is Kernel 3.13.0-rc4 with both patches
> applied.
>
> I now see also a device, that at least works partly now (I can scan with
> scanimage and simple-scan, but xsane fails). I think xsane does some
> more com
On Sun, 22 Dec 2013, Dan Williams wrote:
> > What exactly is the problem you want to solve?
>
> 1/ issue a warm reset to recover ports that have been pm runtime
> powered down. These ports on occasion come back in the SS.inactive
> state, at other times a standard reset resume of the usb_device
On Sat, 2013-12-21 at 20:19 +0800, Yingchun Li wrote:
> before I read the box, it seems
> the ACM driver will read the box automaticly(I find that from the usb
> sniffer). and there
> is a lot of READ-NAK packet.
> So could the box disable the automatic read by someway such as flow
> control, and
Hi Alan,
On Sat, Dec 21, 2013 at 9:34 AM, Alan Stern wrote:
> On Fri, 20 Dec 2013, Dan Williams wrote:
>
>> Both the suspected quirky Synopsys xHC [1] and the
>> port-pm-runtime-resume path need to issue warm resets to reliably bring
>> ports back to an operational state. Per Alan's observation
