Ack-by: matthieu castet
Le Wed, 25 Jul 2012 14:32:50 -0600,
Tim Gardner a écrit :
> Cc: Matthieu CASTET
> Cc: Stanislaw Gruszka
> Cc: Greg Kroah-Hartman
> Cc: linux-usb@vger.kernel.org
> Signed-off-by: Tim Gardner
> ---
> drivers/usb/atm/ueagle-atm.c | 79
> ++
Hi Dmitry,
>> +config INPUT_EBEAM_USB_CLASSIC
>> +bool "eBeam Classic Projection support"
>> +depends on INPUT_EBEAM_USB
>> +default y
>
> Will there be support for other eBean devices (are there any)? If there
> will how soon? How different are they? If not the we probably do not
> n
On 23.07.2012 17:04, Sarbojit Ganguly wrote:
> On 23 July 2012 20:17, Alan Stern wrote:
>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>>
>>> Hello Daniel,
>>>
>>> That is why I provided two stacks,
>>>
>>> 1st one is when I tried to remove the USB hub (which connects a webcam
>>> + microphone)
>
Daniel Mack writes:
> On 23.07.2012 16:47, Alan Stern wrote:
>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
>>> That is why I provided two stacks,
>>>
>>> 1st one is when I tried to remove the USB hub (which connects a webcam
>>> + microphone)
>>> 2nd one is when I tried to remove an USB powered
On 28.07.2012 14:27, Bjørn Mork wrote:
> Daniel Mack writes:
>> On 23.07.2012 16:47, Alan Stern wrote:
>>> On Mon, 23 Jul 2012, Sarbojit Ganguly wrote:
That is why I provided two stacks,
1st one is when I tried to remove the USB hub (which connects a webcam
+ microphone)
2
Daniel Mack writes:
> On 28.07.2012 14:27, Bjørn Mork wrote:
>
>> The reason is this change:
>>
>> 0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
>>
>>
>> It will make bugs like this suddenly 100% reproducible. But the bugs
>> *are* in the drivers, and may have been ther
On 28.07.2012 15:25, Bjørn Mork wrote:
> Daniel Mack writes:
>> On 28.07.2012 14:27, Bjørn Mork wrote:
>>
>>> The reason is this change:
>>>
>>> 0998d0631 device-core: Ensure drvdata = NULL when no driver is bound
>>>
>>>
>>> It will make bugs like this suddenly 100% reproducible. But the bugs
>
On Fri, 27 Jul 2012, Rafael J. Wysocki wrote:
> > > > > + if (parent)
> > > > > + pm_runtime_put(parent);
> > > >
> > > > You should use pm_runtime_put_sync(), not pm_runtime_put().
> > >
> > > Hmm, why exactly?
> >
> > Because it's more efficient to do something directly than t
On Fri, 27 Jul 2012, Damjan wrote:
> >> Maybe I read the kernel OOPS wrong. Was &ep->desc NULL or not?
> >
> > It's hard to tell from the information in the oops. You'd have to get
> > an assembly listing of usb_submit_urb() and figure out what source code
> > statement corresponds to offset 0x75
On Fri, 27 Jul 2012, Sadasivan Shaiju wrote:
> Hi Peter,
>
> I see the following error in our system . Any idea why this is
> happening ?
>
> .
>
> [ 87.929163] hub 1-0:1.0: state 7 ports 6 chg evt 0004
> [ 87
On Sat, 28 Jul 2012, Daniel Mack wrote:
> Hmm, interesting. Thanks for sharing this. I personally never saw this
> bug kicking in, but if I understand your findings correctly, we would
> need something like the following patch for snd-usb and the storage driver?
>
> Sarbojit, could you give this
Alexey Filin wrote:
> On Fri, Jul 27, 2012 at 5:04 PM, Peter Stuge wrote:
>> If you require consumer interfaces and you want neither USB nor
>> Ethernet then I guess there is only FireWire left to choose from.
>
> "The FireWire host interface supports DMA and memory-mapped devices"
This is the in
Hi Alan,
I am not worried about the stack trace . I am worried is the
USB is getting disconnected automatically.
Then it debounce back to Highspeed .
Regards,
Shaiju.
-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Saturday, July 28,
On Saturday, July 28, 2012, Alan Stern wrote:
> On Fri, 27 Jul 2012, Rafael J. Wysocki wrote:
>
> > > > > > + if (parent)
> > > > > > + pm_runtime_put(parent);
> > > > >
> > > > > You should use pm_runtime_put_sync(), not pm_runtime_put().
> > > >
> > > > Hmm, why exactly?
> > >
> >
On Sat, 28 Jul 2012, shaiju shaiju wrote:
> Hi Alan,
>
> I am not worried about the stack trace . I am worried is the
> USB is getting disconnected automatically.
> Then it debounce back to Highspeed .
The log you posted didn't say anything about a USB device getting
disc
On Sat, 28 Jul 2012, Rafael J. Wysocki wrote:
> On Saturday, July 28, 2012, Alan Stern wrote:
> > On Fri, 27 Jul 2012, Rafael J. Wysocki wrote:
> >
> > > > > > > + if (parent)
> > > > > > > + pm_runtime_put(parent);
> > > > > >
> > > > > > You should use pm_runtime_put_sync(), not pm_run
I have 3.5.0+
How can I find out what the problem is with my USB UPS?
It noticeably slows down booting.
This happened on my previous motherboard so I wouldn't be surprised if the UPS
doesn't follow the USB spec exactly.
dmesgs:
--
after boot
--
usb 4-1: new low-speed USB device n
17 matches
Mail list logo
