question
uses bulk transfers.
xhci-hcd, on the other hand, does not use these tasklets (it doesn't
set the HCD_BH bit in the hc_driver's .flags member).
Alan Stern
ost says that the testing was done on an x86_64
machine.
> Gesendet: Montag, 08. Januar 2018 um 17:31 Uhr
> Von: "Alan Stern" <st...@rowland.harvard.edu>
> An: "Josef Griebichler" <griebichler.jo...@gmx.at>
> Cc: "Mauro Carvalho Chehab"
s additional tcp load on raspberry.
>
> Unfortunately there's no usbmon or tshark on libreelec so I can't provide
> further logs.
Can you try running the same test on an x86_64 system?
Alan Stern
admin choice before).
>
> Can't the ksoftirq patch be modified to only apply to the networking
> IRQ handling? That sounds less risky of affecting unrelated subsystems[1].
That might work. Or more generally, allow drivers to specify which
softirq sources should be deferred to ksoftirqd and wh
On Mon, 8 Jan 2018, Mauro Carvalho Chehab wrote:
> Em Sun, 7 Jan 2018 10:41:37 -0500 (EST)
> Alan Stern <st...@rowland.harvard.edu> escreveu:
>
> > On Sun, 7 Jan 2018, Mauro Carvalho Chehab wrote:
> >
> > > > > It seems that the original patch were de
latency instead of
> throughput.
It can't be done without pervasive changes to the USB subsystem, which
I would greatly prefer to avoid. Besides, this wouldn't really solve
the problem. Decreasing the latency for one device will cause it to be
increased for others.
Alan Stern
sbmon, running on a vanilla kernel that gets plenty of video glitches?
Overall, this may be a very difficult problem to solve. The
4cd13c21b207 commit was intended to improve throughput at the cost of
increased latency. But then what do you do when the latency becomes
too high for the video subsystem to handle?
Alan Stern
On Thu, 30 Mar 2017, Oliver Neukum wrote:
> Am Donnerstag, den 30.03.2017, 11:55 -0400 schrieb Alan Stern:
> >
> > I'm pretty sure that usb-storage does not do this, at least, not when
> > operating in its normal Bulk-Only-Transport mode. It never tries to
> > rea
On Thu, 30 Mar 2017, Mauro Carvalho Chehab wrote:
> Em Thu, 30 Mar 2017 10:26:32 -0400 (EDT)
> Alan Stern <st...@rowland.harvard.edu> escreveu:
>
> > On Thu, 30 Mar 2017, Oliver Neukum wrote:
> >
> > > > Btw, I'm a lot more concerned about USB storage
Mauro wrote "the buffer can be
continuous", but that is certainly not what he meant.
Alan Stern
> powered on ?
No, it doesn't, and neither does pm_runtime_put(). After all, if the
user has told the system not to do runtime PM on that device, it
doesn't make sense to call the runtime-suspend handler. But you can
always blame the user when this happens. :-)
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, 25 Nov 2016, Laurent Pinchart wrote:
> Hi Alan,
Hello.
> On Friday 25 Nov 2016 10:21:21 Alan Stern wrote:
> > On Fri, 25 Nov 2016, Sakari Ailus wrote:
> > > On Thu, Nov 24, 2016 at 09:15:39PM -0500, Alan Stern wrote:
> > >> On Fri, 25 Nov 2016, Laurent P
On Fri, 25 Nov 2016, Sakari Ailus wrote:
> Hi Alan and others,
>
> On Thu, Nov 24, 2016 at 09:15:39PM -0500, Alan Stern wrote:
> > On Fri, 25 Nov 2016, Laurent Pinchart wrote:
> >
> > > Dear linux-pm developers, what's the suggested way to ensure that a
> >
t ways to ensure this are (1) audit the code, and
(2) actually try it.
I have a feeling this doesn't quite answer your question, however. :-)
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
Mor
On Thu, 15 Sep 2016, Wade Berrier wrote:
> On Thu Sep 15 15:13, Alan Stern wrote:
> > On Sat, 10 Sep 2016, Wade Berrier wrote:
> >
> > > On Thu Aug 11 16:18, Alan Stern wrote:
> > > > I never received any replies to this message. Should the
ms.
Signed-off-by: Alan Stern <st...@rowland.harvard.edu>
Tested-by: Wade Berrier <wberr...@gmail.com>
CC: <sta...@vger.kernel.org>
---
[as1812]
drivers/usb/core/config.c | 28 +---
1 file changed, 17 insertions(+), 11 deletions(-)
Index: usb-4.
=mythtv-users=144131333703197=2
You should a check for ep_out to the probe routine.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, 10 Sep 2016, Wade Berrier wrote:
> On Thu Aug 11 16:18, Alan Stern wrote:
> > I never received any replies to this message. Should the patch I
> > suggested be merged?
> >
>
> Hello,
>
> I applied this updated patch to the fedora23 4.7.2 kernel a
On Sun, 21 Aug 2016, Matwey V. Kornilov wrote:
> In both cases (with or without HCD_BH), usb_hcd_giveback_urb is called
> every 0.01 sec. It is not clear why behavior is so different.
What behavior are you asking about? The difference between HCD_BH set
and not set?
Alan
I never received any replies to this message. Should the patch I
suggested be merged?
Alan Stern
On Tue, 12 Jul 2016, Alan Stern wrote:
> On Sat, 9 Jul 2016, Mauro Carvalho Chehab wrote:
>
> > C/C linux-usb Mailing list:
> >
> >
> > Em Wed, 18 May 2016 0
--
> >
> > Is this change appropriate to be pushed upstream? Where to go from
> > here?
>
> This issue is at the USB core. So, it should be reported to the
> linux-usb mailing list.
>
> The people there should help about how to proceed to get
On Wed, 9 Sep 2015, Laurent Pinchart wrote:
> On Wednesday 09 September 2015 10:30:12 Hans de Goede wrote:
> > On 08-09-15 16:36, Alan Stern wrote:
> > > On Tue, 8 Sep 2015, Hans de Goede wrote:
> > >> On 09/07/2015 06:23 PM, Mian Yousaf Kaukab wrote:
> > >
en the long term goal is
> to use tasklets for URB completion anyway.
I'm not sure that this is a long-term goal for every HCD. For
instance, there probably isn't much incentive to convert a driver if
its host controllers can only run at low speed or full speed.
Alan Stern
--
To unsubscribe
On Wed, 9 Sep 2015, Hans de Goede wrote:
> Hi,
>
> On 08-09-15 16:36, Alan Stern wrote:
> > On Tue, 8 Sep 2015, Hans de Goede wrote:
> >
> >> Hi,
> >>
> >> On 09/07/2015 06:23 PM, Mian Yousaf Kaukab wrote:
> >>> urb completion call
s this then
> still needed ?
We moved to handling URB completions in a tasklet, not a threaded
handler. (Similar idea, though.) And the change was made in only one
or two HCDs, not in all of them.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-media" i
:
Acked-by: Alan Stern st...@rowland.harvard.edu
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
;
This seems wrong. The uvc driver is bound to intf, not to intf's
parent. So it would be okay for the driver to set
intf-dev.power.force_direct_complete, but it's wrong to set
intf-dev.parent-power.force_direct_complete.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux
).
Alan Stern
Jan 29 21:26:51 plattpcn kernel: [ 17.322493] input: UVC Camera (05ca:1812)
as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input10
Jan 29 21:26:51 plattpcn kernel: [ 17.322621] usbcore: registered new
interface driver uvcvideo
Jan 29 21:26:51 plattpcn kernel
On Mon, 14 Apr 2014, Ezequiel Garcia wrote:
On Apr 14, Alan Stern wrote:
On Mon, 14 Apr 2014, Ezequiel Garcia wrote:
Currently stk1160_read_reg() uses a stack-allocated char to get the
read control value. This is wrong because usb_control_msg() requires
a kmalloc-ed buffer
.
This isn't right either. The buffer must be allocated in its own cache
line; it must not be part of a larger structure.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
the address to usb_control_msg(). But usb_control_msg() requires the
buffer to be allocated by kmalloc, not on the stack.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
large. Other people, using audio
only (no video), find that EHCI can work well with latencies as low as
2 ms or so. (That's using 3.13-rc, which includes some changes in the
snd-usb-audio driver.)
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body
when the interface setting
gets switched never really arises. Each usb_host_endpoint structure is
referenced from only one altsetting. If the driver wants the new
parameters applied to an endpoint in several altsettings, it will have
to change each altsetting separately.
Alan Stern
are correct, but the driver wants to use something
different for its own reasons (for example, to get lower latency or
because it knows that it will never use packets as large as the
descriptor allows). Right.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media
size. It requires you to
specify only the number of packets, not their sizes. Therefore it
doesn't matter whether you call usb_change_ep_bandwidth() before or
after usb_alloc_urb().
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message
to altsetting
0 when a driver unbinds.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2 Oct 2013, Alan Stern wrote:
Ok, so it sounds like we want to keep the changes the endpoints across
alt setting changes.
No, just the opposite. That was the point I was trying to make. Any
changes to ep5 in altsetting 0 (for example) will have no effect on ep1
/driver.c before the first #include line.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, 22 Sep 2013, Marc MERLIN wrote:
On Sun, Sep 22, 2013 at 12:38:56PM -0400, Alan Stern wrote:
gandalfthegreat:/sys/bus/usb/devices/3-1.6/power# grep . *
active_duration:61227648
async:enabled
autosuspend:2
autosuspend_delay_ms:2000
connected_duration:66830880
On Sun, 18 Aug 2013, Geert Uytterhoeven wrote:
On Thu, Jul 11, 2013 at 1:12 AM, Arnd Bergmann a...@arndb.de wrote:
On Wednesday 10 July 2013, Alan Stern wrote:
This isn't right. There are USB host controllers that use PIO, not
DMA. The HAS_DMA dependency should go with the controller
would use phy1 or phy2, and the PHY
consumers would use host1 or host2.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
not a layering violation for one region of the kernel to store
private data in a structure defined by another part of the kernel.
This happens all the time (e.g., dev_set_drvdata).
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord
.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
, this was simply meant to be a suggestion to show that it
is relatively easy to do what you need without using name or ID
strings.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
?
phy_create is the API by which the PHY's driver (the supplier) hook into the
PHY framework. It's like the controller driver will always interact with the
PHY driver through the PHY framework.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body
does phy_create() fit into this picture?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the name string. Have the
consumer pass the data structure's address when it calls phy_create,
instead of passing the name. Then you don't have to worry about two
PHYs accidentally ending up with the same name or any other similar
problems.
Alan Stern
--
To unsubscribe from this list: send
On Thu, 11 Jul 2013, Geert Uytterhoeven wrote:
On Thu, Jul 11, 2013 at 3:01 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 11 Jul 2013, Arnd Bergmann wrote:
On Wednesday 10 July 2013, Alan Stern wrote:
This isn't right. There are USB host controllers that use PIO, not
DMA
.
To fix the latter, instead of adding lots of depends on HAS_DMA, make
those drivers depend on USB, instead of depending on USB_ARCH_HAS_HCD and
selecting USB. Drivers for other busses (e.g. MOUSE_SYNAPTICS_I2C) already
handle this in a similar way.
That seems reasonable.
Alan Stern
On Thu, 11 Jul 2013, Arnd Bergmann wrote:
On Wednesday 10 July 2013, Alan Stern wrote:
This isn't right. There are USB host controllers that use PIO, not
DMA. The HAS_DMA dependency should go with the controller driver, not
the USB core.
On the other hand, the USB core does call
not a hack; it's a normal use for a quirk flag. Of course, if you
can figure out what's wrong with the camera and see how to fix it, that
would be best.
How does the camera perform on a Windows system after being put to
sleep and then woken up?
Alan Stern
--
To unsubscribe from this list: send the line
request.
The USB core is not PM-QOS aware. It relies on the PM core to tell it
when devices may safely be runtime-suspended.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Sun, 21 Oct 2012, Artem S. Tashkinov wrote:
dmesg messages up to a crash can be seen here:
https://bugzilla.kernel.org/attachment.cgi?id=84221
The first problem in the log is endpoint list corruption. Here's a
debugging patch which should provide a little more information.
Alan Stern
On Mon, 22 Oct 2012, Daniel Mack wrote:
On 22.10.2012 17:17, Alan Stern wrote:
On Sun, 21 Oct 2012, Artem S. Tashkinov wrote:
dmesg messages up to a crash can be seen here:
https://bugzilla.kernel.org/attachment.cgi?id=84221
The first problem in the log is endpoint list corruption
.
Alan Stern
P.S.: It will help if you unplug as many of the other USB devices as
possible before running this test.
Index: usb-3.6/drivers/usb/core/hcd.c
===
--- usb-3.6.orig/drivers/usb/core/hcd.c
+++ usb-3.6/drivers/usb/core
/log/messages
Is it possible to use netconsole? The screenshot above appears to be
the end of a long series of error messages, which isn't too useful.
The most important information is in the first error.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media
the xHCI controller is
highly unlikely to be involved.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
driver bug:
Does the same thing happen with earlier kernel versions?
What about if you unload snd-usb-audio or ehci-hcd?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
already present. There is no reason to keep them.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
callers
all seem to be okay in this respect, however I don't understand the
video drivers well enough to be certain about them.
Signed-off-by: Alan Stern st...@rowland.harvard.edu
CC: Dmitry Torokhov dmitry.torok...@gmail.com
CC: Kyungmin Park kyungmin.p...@samsung.com
CC: Andy Walls awa
On Sat, 26 Nov 2011, Johann Klammer wrote:
Alan Stern wrote:
This is probably a low-level hardware error. Interference between the
two ports of some kind.
This is quite possible. Have been able to produce a more verbose logfile
snippet.
The log shows that your EHCI controller reports
the event. I can mail this, but it's rather large and the mailing
list won't accept the message.
Can you put the usbmon trace on a web server like pastebin.com?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
amount of time on this, we might just as well
go for the best solution we can come up with even if that is some
more work.
Okay, go ahead. I have no objection.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
retained control the entire time, the program should be able to assume
the device's state hasn't changed.
I'm not claiming that this is a better solution than putting everything
in the kernel. Just that it is a workable alternative which would
involve a lot less coding.
Alan Stern
--
To unsubscribe
implement this control will take the lock
forever.
No, because there is no lock. Programs that haven't been changed will
continue to behave as they do today -- they will unbind the webcam
driver and assume full control of the device.
Alan Stern
--
To unsubscribe from this list: send the line
result.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
will attend the Linux
Plumbers conference in Santa Rosa.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 9 Aug 2011, Hans de Goede wrote:
Hi,
On 08/09/2011 04:19 PM, Alan Stern wrote:
On Tue, 9 Aug 2011, Hans de Goede wrote:
According to Theodore, we have developed 5 drivers for them because the
stillcam modes in different devices use four different vendor-specific
drivers
think?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
it really make sense to combine 5 drivers into one? I
think some sort of sharing protocol would work out better.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
uninformative unless you enable
CONFIG_USB_DEBUG in the kernel build.
Have you tried running these tests on a different computer, preferably
one using a different chipset?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord
... then tomorrow we would have to merge two others
and then later on even more. Before you know it, we would end up with
a single gigantic kernel driver to manage every USB device! Obviously
not a sustainable approach in the long run.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux
On Mon, 8 Aug 2011, Theodore Kilgore wrote:
On Mon, 8 Aug 2011, Alan Stern wrote:
On Sun, 7 Aug 2011, Theodore Kilgore wrote:
This indirectly answers my question, above, about whatever device there
may or may not be. What I get from this, and also from a bit of snooping
around
support is in userspace is a red herring.
No, this has some significant implications. In particular, there's no
good way for the kernel driver to ask the userspace driver if it is
busy. If both drivers were in the kernel, this would be easy to
arrange.
Alan Stern
--
To unsubscribe from this list
and completely unrelated devices don't work if they are later plugged into
the
same USB port.
That's a rather incomprehensible run-on sentence, but as near as I can
tell, it is wrong.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message
On Fri, 15 Jul 2011, Ming Lei wrote:
Hi,
On Thu, Jul 14, 2011 at 11:03 PM, Alan Stern st...@rowland.harvard.edu
wrote:
More likely, the reset erases some device setting that uvcvideo
installed while binding. �Evidently uvcvideo does not re-install the
setting during reset-resume
On Fri, 15 Jul 2011, Ming Lei wrote:
Hi,
On Fri, Jul 15, 2011 at 10:27 PM, Alan Stern st...@rowland.harvard.edu
wrote:
This is fine with me. �However, it is strange that the Set-Interface
request is necessary. �After being reset, the device should
automatically be in altsetting 0
On Thu, 14 Jul 2011, Ming Lei wrote:
Hi,
On Wed, Jul 13, 2011 at 11:59 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Wed, 13 Jul 2011, Ming Lei wrote:
Almost same.
Come on. �Almost same means they are different. �That difference is
clearly the important thing you need
On Wed, 13 Jul 2011, Ming Lei wrote:
Hi,
On Tue, Jul 12, 2011 at 11:44 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Tue, 12 Jul 2011, Ming Lei wrote:
Hi Laurent,
After resume from sleep, �all the ISO packets from camera are like below:
880122d9f400 3527230728 S Zi:1
On Wed, 13 Jul 2011, Ming Lei wrote:
Hi,
On Wed, Jul 13, 2011 at 11:20 PM, Alan Stern st...@rowland.harvard.edu
wrote:
Why should system suspend be different from runtime suspend? �Have you
This is also my puzzle, :-)
compared usbmon traces for the two types of suspend?
Almost
:004:1 0:1:2600:0 32 0:0:12
0:1600:12 0:3200:12 0:4800:12 0:6400:12 51200 = 0c8c fa7e
012f1b05
All are headed with 0c8c, see attached usbmon captures.
Maybe this device needs a USB_QUIRK_RESET_RESUME entry in quirks.c.
Alan Stern
the point? If you want to use less than 80% of your bandwidth
for periodic transfers, go ahead and do so. You don't need to change
the limit.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo
with the documentation, so we should fix one
of them.
Under the circumstances, the documentation file should be changed.
Sarah, can you do that along with the change to xhci-hcd?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord
that URB_SHORT_NOT_OK is set, but no
others.
And I wasn't aware of that last one... Host controller drivers should
report -ESHUTDOWN to mean the device has been disconnected, not
-EPROTO. But usually HCD don't take these events into account when
determining URB status codes.
Alan Stern
status field to -EPROTO, no matter whether the device is connected or
not and no matter whether the host controller is alive or not.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Thu, 16 Jun 2011, Sarah Sharp wrote:
On Thu, Jun 16, 2011 at 03:39:11PM -0400, Alan Stern wrote:
That's appropriate. But nobody should ever set an isochronous URB's
status field to -EPROTO, no matter whether the device is connected or
not and no matter whether the host controller
is currently in use -- at least, not in the way you mean.
I'm not saying this can't be done. But it would be a bigger job than
you think, and this isn't the appropriate thread to discuss it.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body
the place
to start.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, 10 Jun 2011, Mauro Carvalho Chehab wrote:
Em 10-06-2011 11:48, Alan Stern escreveu:
On Fri, 10 Jun 2011, Hans de Goede wrote:
As Felipe has mentioned, this sounds like the sort of problem that
can better be solved in userspace. A dual-mode device like the one
you
driver that handles streaming. No ?
No. Something else is needed.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
and makes permanent high speed usb
connections unusable on Linux,
at least with this VIA hardware.
No debug parms in modules, we need to ask linux-usb how to debug this.
You can start by building a kernel with CONFIG_USB_DEBUG enabled.
Alan Stern
--
To unsubscribe from this list: send
On Sun, 13 Jun 2010, thomas schorpp wrote:
Am 13.06.2010 15:57, schrieb Alan Stern:
On Sun, 13 Jun 2010, thomas schorpp wrote:
ehci-hcd is broken and halts silently or disconnects after hours or a few
days, with the wlan usb adapter
How do you know the bug is in ehci-hcd
figured out how to patch the gspca driver, but not uvcvideo. The
patch looks a bit hackish; can with experience with that driver look it
over? Can anyone tell me where to look for the usb_set_interface() in
uvcvideo?
Not at the moment, sorry.
Alan Stern
--
To unsubscribe from this list: send
they are
powered down and after they are powered up.
This patch is not correct as it stands. If you use runtime PM then the
system PM resume method has to be changed. See the discussion in
section 6 of Documentation/power/runtime_pm.txt.
Alan Stern
--
To unsubscribe from this list: send the line
On Tue, 9 Feb 2010, Guennadi Liakhovetski wrote:
On Tue, 9 Feb 2010, Alan Stern wrote:
On Mon, 8 Feb 2010, Guennadi Liakhovetski wrote:
To save power soc-camera powers subdevices down, when they are not in
use,
if this is supported by the platform. However, the V4L standard
On Mon, 4 Jan 2010, Sean wrote:
Alan Stern wrote:
Um, when you say it does the job, what do you mean?
It traps the error and prevents the kernel from crashing.
As did some of the earlier patches, right?
The job it was _intended_ to do was to prove that your problems are
caused
On Tue, 5 Jan 2010, Sean wrote:
Thanks so much for your help Alan. I also think this is definitely a bug
in the hardware. Let's leave it at that, I'm happy.
Okay. You should mark the Bugzilla report as REJECTED and close it
out.
Alan Stern
--
To unsubscribe from this list: send the line
On Mon, 4 Jan 2010, Sean wrote:
Alan Stern wrote:
Try inserting a line saying:
td_check(ohci, hash, #2c);
two lines above the #2b line, i.e., just after the wmb(). That'll help
narrow down the search for the bug.
Alan,
I put the extra line in and ran capture-example twice
on a different computer?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
Or it could be some bizarre timing problem with the memory bus, or
something else equally obscure. You didn't mention before that this
was a SoC rather than an ordinary PC.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord
1 - 100 of 127 matches
Mail list logo
