I found several SMP and UP locking errors in usb-storage, attached is a
patch:
Changes:
* srb->result is a bitfield, several << 1 were missing.
* further sg[].address conversions. I've added a macro to facilitate
code sharing between 2.4 and 2.5. What are your plans for that?
* add scsi_lock c
Sorry, this is the third attempt of trying to know more
about the sopport state of creative webcam go plus. Perhaps you haven't read the other
mails.
I only want to know if this webcam is supported (I've heard video could be seen in
black & white), and
where i can find the latest code (I've t
> Sorry, this is the third attempt of trying to know more
> about the sopport state of creative webcam go plus. Perhaps you
> haven't read the other mails.
I have not been reading this list so often. Can not have fun everyday,
also have to make money :-)
> I only want to know if this webcam is
Hi,
> I tried using kernel 2.5.15 and I still get the same oops message.
I suspected you would, but that's good to confirm (given how
much changed since 2.5.8).
> There's no high speed device connected to the host controller. You
> said end_unlink_async function should never be called when
Earlier in the 2.5 development cycle a patch was applied that changed
the reference counting behaviour for USB devices.
There are a couple of problems with the change:
- It made the USB code more complicated as a whole with the introduction
of an additional cleanup path for devices. Using the t
On Sun, 12 May 2002 16:59:53 +0200
Stefan Nilsen <[EMAIL PROTECTED]> escribió:
> > Sorry, this is the third attempt of trying to know more
> > about the sopport state of creative webcam go plus. Perhaps you
> > haven't read the other mails.
>
> I have not been reading this list so often. Can not
Greetings,
I tried to jump to kernel 2.5.15 today, but with not much success... After
the usual boot I load the USB modules. The attached webcams are detected, but
when I try to get a picture, the program hangs. I can ^C it, but a second
attempt causes a 'D' process that's hanging in "down_i"
On Mon, May 13, 2002, Nemosoft Unv. <[EMAIL PROTECTED]> wrote:
> I tried to jump to kernel 2.5.15 today, but with not much success... After
> the usual boot I load the USB modules. The attached webcams are detected, but
> when I try to get a picture, the program hangs. I can ^C it, but a second
On Sunday 12 May 2002 22.33, Diego Calleja wrote:
> Well, I'm learning C now, I don't know a lot about kernel
> programming, but I think it's the time to starti'll try to port
> to a newer kernel. I'll let you know if I've some success. I hope I
> can ask you if I've some doubt ;) If you know
Playing with some strange device with vendor protocol,
I find that alt-uhci crashes the kernel without any messages
or information. (No oops, just dead.)
On the other hand, uhci comes back with an error message
usb-uhci.c: uhci_submit_urb: pipesize for pipe c0030400 is zero
Since an error mes
On Mon, May 13, 2002, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Playing with some strange device with vendor protocol,
> I find that alt-uhci crashes the kernel without any messages
> or information. (No oops, just dead.)
> On the other hand, uhci comes back with an error message
>
> usb-u
On Tue, 7 May 2002, Greg KH wrote:
| # This patch includes the following deltas:
| #ChangeSet1.447.73.1 -> 1.447.73.2
| # drivers/usb/input/hid-core.c1.23-> 1.24
| #
| # The following is the BitKeeper ChangeSet Log
| #
|
> The patch is simple enough and I've attached it
Good. Now both drivers survive.
The next step is making this device actually do something.
Andries
___
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the ha
Can someone give any advice for it ?
- Original Message -
From: "jchen@ptopa" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 09, 2002 7:43 PM
Subject: [linux-usb-devel] usb microphone not work
> Hello everyone :
>
> 1
> I have problem with my usb microphone that plug
Hello All,
I have a USB device which has 16 bytes FIFO at
the Bulk endpoint while the MaxPacketSize for that endpoint is 64
bytes. Won't sending a data payload of size bigger than 16 bytes,
result in buffer overflow?
I assume that 16 bytes FIFO is nothing but the
endpoint buffer size.
On Mon, May 13, 2002, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > The patch is simple enough and I've attached it
>
> Good. Now both drivers survive.
Excellent.
> The next step is making this device actually do something.
Well, if you need to talk to that endpoint, then you'll need to klu
On Sun, 2002-05-12 at 23:22, jchen@ptopa wrote:
> Can someone give any advice for it ?
No. There are no attachments, and therefore anyone reading your message
would have no clue what is the problem!
The programming interface for /dev/audio* is here:
http://www.opensound.com/pguide/index.html
On Sun, 2002-05-12 at 23:22, Latha wrote:
> I have a USB device which has 16 bytes FIFO at the Bulk
> endpoint while the MaxPacketSize for that endpoint is 64 bytes.
> Won't sending a data payload of size bigger than 16 bytes,
> result in buffer overflow?
>
> I assume that 16 bytes FIFO is nothi
On Mon, 13 May 2002 16:22, [EMAIL PROTECTED] wrote:
> Can someone give any advice for it ?
I originally ignored this because I thought that it should have gone to the
-users mailing list. Perhaps it should have, but the error tells you to come
here, so I guess that the first part of your posting
Brad Hards wrote:
> The problem appears to be broken descriptors. You need a real developers to
> help you with this:
> usbaudio: warning: found 2 of 1 logical channels.
> usbaudio: no idea what's going on..., contact
> [EMAIL PROTECTED]
doesn't look like a message I coded 8-)
Anyway, if you su
20 matches
Mail list logo
