my usb camera works fine under linux.
but in linux it can not get the data.
i custom the V4L2 driver for the camera.
everything seems good,but just can not
read data from the camera.
i use the Isochronous mode to get the data
from the camera. in the complete handler of
the struct urb that been su
Hi,
Joerg Hoener wrote:
1.) Sometimes the initialization, returned one byte 0xFF. The remote works in
any case, but could it be that the initialization is not correct? What does
this return value states?
I did not look at this and I would not know what this would mean. Since
the remote seems
On Mon, Jun 06, 2005 at 10:37:28AM +0800, Enzo Chen (?h) wrote:
> > I list the code below.
> > Please understand it is under development and so there should be many
> > bugs in it.
> > However, the point is why usb_unlink_urb() in mxu2s_close() function
> > blocked?
>
> If you enable d
On Sun, 5 Jun 2005, Phil Dibowitz wrote:
> > What does bother me is preventing people from using the last sector of a
> > disk when they already have valid data stored there. Assuming the updated
> > PL-3507 chips don't get used in a context where the last disk sector could
> > be written (for
On Sun, 5 Jun 2005, Phil Dibowitz wrote:
> Mariusz Muszynski wrote:
> > diff -urNp linux-2.4.31/drivers/usb/storage/unusual_devs.h
> > linux-2.4.31-bzyk/drivers/usb/storage/unusual_devs.h
> > --- linux-2.4.31/drivers/usb/storage/unusual_devs.h Wed Nov 17 12:54:21
> > 2004
> > +++ linux-2.4.3
On Mon, 6 Jun 2005, Alan Stern wrote:
On Sun, 5 Jun 2005, Phil Dibowitz wrote:
What does bother me is preventing people from using the last sector of a
disk when they already have valid data stored there. Assuming the updated
PL-3507 chips don't get used in a context where the last disk secto
On Mon, 6 Jun 2005, Alex Butcher wrote:
> > Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
> > design geniuses at Prolific we're caught in a "damned if you do, damned if
> > you don't" situation.
>
> Is it possible to do something in user space, based on a unique device
>
On Wed, Jun 01, 2005 at 12:12:58AM +0200, Harald Welte wrote:
> > > Wouldn't it help to associate the URB with the file (instaed of the
> > > task), and then send the signal to any task that still has opened the
> > > file? I'm willing to hack up a patch, if this is considered a sane fix.
> >
>
On Mon, 6 Jun 2005, Harald Welte wrote:
> On Wed, Jun 01, 2005 at 12:12:58AM +0200, Harald Welte wrote:
>
> > > > Wouldn't it help to associate the URB with the file (instaed of the
> > > > task), and then send the signal to any task that still has opened the
> > > > file? I'm willing to hack up
On Mon, Jun 06, 2005 at 12:24:25PM -0400, Alan Stern wrote:
> > > Ok, I'll get something coded shortly.
> >
> > Unfortunately this approach is not feasible, since there is no 'reverse
> > mapping' from a file to a process. So for every URB delivery, we would
> > have to walk that task_list and ch
Hi,
I'm running linux 2.6.11 (vanilla) on a custom board, with a
Sharp LH7A404.
.config:
CONFIG_ARCH_LH7A40X=y
CONFIG_ARCH_LH7A404=y
I've been having problems with a USB storage chip connected to the
USB host interface (ST72F65, soldered on to the board).
To detect media presence, I have a
On Mon, 6 Jun 2005, Jamie Guinan wrote:
> Hi,
>
> I'm running linux 2.6.11 (vanilla) on a custom board, with a
> Sharp LH7A404.
>
> .config:
> CONFIG_ARCH_LH7A40X=y
> CONFIG_ARCH_LH7A404=y
>
> I've been having problems with a USB storage chip connected to the
> USB host interface (ST72F65,
On Mon, 6 Jun 2005, Alan Stern wrote:
> On Mon, 6 Jun 2005, Jamie Guinan wrote:
>
> > Hi,
> >
> > I'm running linux 2.6.11 (vanilla) on a custom board, with a
> > Sharp LH7A404.
> >
> > .config:
> > CONFIG_ARCH_LH7A40X=y
> > CONFIG_ARCH_LH7A404=y
> >
> > I've been having problems with a US
On Monday 06 June 2005 12:03 pm, Jamie Guinan wrote:
>
> 2) Does the 0x30101 look like a sane response? I'm seeing 0x30100
> when I remove an IOGEAR media reader connected through via a
> standard USB TypeA port.
What's a bit curious is that the connect status bit change
is set (CSC)
On Mon, 6 Jun 2005, Jamie Guinan wrote:
> > That's odd. While I'm not familiar with the details of OHCI or the
> > LH7A404 driver, normally a host controller driver does not check the port
> > status when communicating with a device. Port status is checked
> > asynchronously by the hub driver
On Mon, 6 Jun 2005, David Brownell wrote:
> Thing is, other folk have been complaining recently about cases
> where devices seem to be spontaneously disconnecting from Linux.
> (Often storage devices, for that matter.) And I'm wondering if
> your setup can be used to turn up more information on t
This smoothes two imperfections:
- Increase number of LUNs per device from 4 to 9. The best solution
would be to remove this limit altogether, but that has to wait until
the time when more than 26 hosts are allowed.
- Replace mdelay with msleep in a probing routine.
Signed-off-by: Pete Zaitcev
On Monday 06 June 2005 1:37 pm, Alan Stern wrote:
> On Mon, 6 Jun 2005, David Brownell wrote:
> >
> > What I'm curious about is whether there's something that usbcore
> > is doing to the poor root hubs that make them disconnect devices.
>
> What could usbcore possibly do to make a hub disconnect
Hello USB hackers,
I would like to (belatedly) register a complaint concerning this patch:
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110313153001002&w=2>
Dave Brownell writes, "the only penalty is increased power consumption
(from OHCI clocks) on boards/chips that don't work right." Sadly
This patch does two things to help reset recovery. It started life as
as496 and was rediffed by me.
First, the patch checks the result of a CLEAR_HALT request and doesn't reset
the
endpoint's data toggle unless the request succeeded.
Second, it reduces the timeout for a device reset from 20 se
This patch causes a port reset whenever there's a transport error or abort.
If that fails it reverts back to doing a mass-storage device reset. It
started life as as497 and was rediffed by me.
This makes error recovery a lot quicker and more reliable.
Greg, please apply.
Matt
Signed-off-by: Al
This patch started life as as527, and was rediffed by me.
Since the IDE interface doesn't convey much information about types of
errors, many USB-IDE adapters report all low-level errors with SK = 0x04,
which is supposed to be used only for non-recoverable errors. As a result
the SCSI midlayer do
Adam Kropelin wrote:
Alan Stern wrote:
On Thu, 2 Jun 2005, Adam Kropelin wrote:
It would certainly help to know exactly where the blockage occurs. Is
it in the HID queuing code, in the HCD (unlikely), or in the UPS
device? Suitable debugging statements ought to settle that pretty
easily.
Alan Stern wrote:
> On Sun, 5 Jun 2005, Phil Dibowitz wrote:
>
>
>>>What does bother me is preventing people from using the last sector of a
>>>disk when they already have valid data stored there. Assuming the updated
>>>PL-3507 chips don't get used in a context where the last disk sector coul
Alan Stern wrote:
> On Sun, 5 Jun 2005, Phil Dibowitz wrote:
>
>
>>Mariusz Muszynski wrote:
>>
>>>diff -urNp linux-2.4.31/drivers/usb/storage/unusual_devs.h
>>>linux-2.4.31-bzyk/drivers/usb/storage/unusual_devs.h
>>>--- linux-2.4.31/drivers/usb/storage/unusual_devs.h Wed Nov 17 12:54:21
>>>
Alan Stern wrote:
> On Mon, 6 Jun 2005, Alex Butcher wrote:
>
>
>>>Ultimately we may want to remove the FIX_CAPACITY flag. Thanks to the
>>>design geniuses at Prolific we're caught in a "damned if you do, damned if
>>>you don't" situation.
>>
>>Is it possible to do something in user space, based
On Tue, 07 Jun 2005 11:24:25 +0800, Martin Kessler <[EMAIL PROTECTED]> wrote:
> > I'm relying on the afflicted users to send debug traces. Sticking in a
> > printk might be a quicker way for Martin and Christian to get infoif
> > usbmon is proving troublesome. How's it going, guys?
> Any activ
On Monday 06 June 2005 10:05 pm, Pete Zaitcev wrote:
> On Tue, 07 Jun 2005 11:24:25 +0800, Martin Kessler <[EMAIL PROTECTED]> wrote:
>
>
> > > I'm relying on the afflicted users to send debug traces. Sticking in a
> > > printk might be a quicker way for Martin and Christian to get infoif
> > >
On Mon, 06 Jun 2005 20:50:28 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
> >>>--- linux-2.4.31/drivers/usb/storage/unusual_devs.h Wed Nov 17
> >>>12:54:21 2004
> >>>+++ linux-2.4.31-bzyk/drivers/usb/storage/unusual_devs.hWed Jun 1
> >>>21:18:28 2005
> >>>@@ -255,6 +255,15 @@ UNU
David Brownell wrote:
On Monday 06 June 2005 10:05 pm, Pete Zaitcev wrote:
On Tue, 07 Jun 2005 11:24:25 +0800, Martin Kessler <[EMAIL PROTECTED]> wrote:
I'm relying on the afflicted users to send debug traces. Sticking in a
printk might be a quicker way for Martin and Christian to ge
Pete Zaitcev wrote:
> On Mon, 06 Jun 2005 20:50:28 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
>
>--- linux-2.4.31/drivers/usb/storage/unusual_devs.h Wed Nov 17
>12:54:21 2004
>+++ linux-2.4.31-bzyk/drivers/usb/storage/unusual_devs.hWed Jun 1
>21:18:28 2005
>>
On Monday 06 June 2005 5:21 pm, Matthew Dharm wrote:
> This patch causes a port reset whenever there's a transport error or abort.
> If that fails it reverts back to doing a mass-storage device reset. It
> started life as as497 and was rediffed by me.
>
> This makes error recovery a lot quicker a
32 matches
Mail list logo
