Hi,
> It can be solved for any particular driver just by adding usb(dev)fs ioctl
> support to that driver.
:o)
> Define a structure, say FOO, that encapsulates the
> relevant device ID info ... for /dev files, major/minor and whether it's
> character or block; for network devices, something els
On Mon, 18 Mar 2002 05:57, Greg KH wrote:
> [EMAIL PROTECTED], 2002-03-17 10:14:24-08:00, [EMAIL PROTECTED]
> USB Urefs for hid-core/hiddev
>
> I've written a patch Vojtech and I discussed for enhancing the
> hiddev code to optionally provide more detailed output on read().
> The old fu
Hi,
This updates linux/Documentation/usb/proc_usb_info.txt to:
- refer to "usbfs"
- describe the /proc/bus/usb/BBB/DDD files
- more info about the .../drivers and .../devices
- ... generally, gives more information.
This is ever so slightly forward looking in how it describes
ba
> There is one small problem with uhci.c (patch appended) where it checks
> urb->status after the completion handler. It should only do this if it's
> an auto resubmitting interrupt URB, but we always checked it.
>
> Other than that, it does not touch the URB after calling the completion
> handle
On Sun, Mar 17, 2002, David Brownell <[EMAIL PROTECTED]> wrote:
> > > > Also it's not clear whether completion handler can free urb or not.
> > > > usb-uhci and usb-ohci don't seem to use
> > > > urb after calling completion handler (except interrupt and ring transfers
> > > > where you obviosly m
Unfortunately, I left out one line from my spinlock cleanup patch
recently.
As a result, using interrupt URB's could cause a deadlock on SMP
kernels.
This should fix the deadlock Greg reported.
JE
--- linux-2.4.19-pre3.orig/drivers/usb/uhci.c Sun Mar 17 21:43:12 2002
+++ linux-2.4.19-pre3/dr
Hi Greg,
Here's a patch against 2.5.7-pre1, please merge.
This updates the Philips tweak so that it also applies
to late-model ICH chips from Intel. (Or so I'm told ... :)
That's at least three EHCI implementations known to
behave on Linux. (And one hopes VIA soon too...)
It also cleans up a
Please send me the contents of /proc/bus/usb/devices when the device is
attached to the system.
Matthew Dharm
On Sun, Mar 17, 2002 at 11:28:14AM +0100, Jörg Prante wrote:
> Hi,
>
> here is a Linux Kernel USB definition of the LaCie USB CDRW burner. This
> was missing from linux/drivers/usb/sto
Robin,
Just incase your not already aware of it, the spca50x usb camera driver
supports the intel CS330 camera's since they are apparently based on the
spca501 chipset...
They live here: http://spca50x.sourceforge.net/
Maybe you could shift your focus from getting the camera working at all
wit
On Mon, 18 Mar 2002 08:49, David Brownell wrote:
> > Unfortunately, your problem cannot be solved right now. There is
> > currently no way to register the device info with a USB device, so that
> > it appears somewhere in /proc/bus/usb. There are all sorts of problems
> > with this (driver having
> cs330_send_vendor_control_packet( pcs330_dev, (unsigned long
> int)0x41001000 );
Endianness - also its too many bytes to fit a ulong
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listi
Greetings,
On Sunday 17 March 2002 22:49, David Brownell wrote:
> > Unfortunately, your problem cannot be solved right now. There is
> > currently no way to register the device info with a USB device, so that
> > it appears somewhere in /proc/bus/usb. There are all sorts of problems
> > with this
On Sun, 17 Mar 2002 16:05:43 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> > 1) What does -12 mean when it is returned in purb->status?
> > 2) Is there a function in the kernel API to resolve a numeric error return
> > to a textual description (kinda like perror() in the C library)?
>
> "-1
On Mon, 18 Mar 2002 01:14:44 +0100
Georg Acher <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 17, 2002 at 11:51:35PM +, Robin Cull wrote:
>
> > 1) What does -12 mean when it is returned in purb->status?
>
> According to /usr/include/asm/errno.h, -12 is ENOMEM, out of memory.
> Cool...
I mention
On Sun, Mar 17, 2002 at 11:51:35PM +, Robin Cull wrote:
> 1) What does -12 mean when it is returned in purb->status?
According to /usr/include/asm/errno.h, -12 is ENOMEM, out of memory. Cool...
> 3) Have I got the syntax of the call right in the first place? I am
> unsure what goes in pur
> 1) What does -12 mean when it is returned in purb->status?
> 2) Is there a function in the kernel API to resolve a numeric error return
> to a textual description (kinda like perror() in the C library)?
"-12" on my system == "-ENOMEM" according to ,
as you'd see if you passed the code to userl
Hi all,
I've been lurking this list for a while. I'm writing a device driver for
the Intel PC Camera webcam (aka ViewQuest CS330). I'm attempting to
reverse engineer the protocol using output from a CATC analyser running
from Windows 2000, I'm lucky enough to have access to one at work.
The
> Unfortunately, your problem cannot be solved right now. There is currently
> no way to register the device info with a USB device, so that it appears
> somewhere in /proc/bus/usb. There are all sorts of problems with this
> (driver having multiple configurations, multiple devices per USB devi
> usb_submit_urb should really have well defined semantics for failures:
>
> 1. the completion handler is _not called_ and the result of
> usb_submit_urb indicates _failure_ (the way uhci handles it now),
> ...
> 3. the completion handler is _called_ and the result of usb_submit_urb
> indicates
> > > Also it's not clear whether completion handler can free urb or not.
> > > usb-uhci and usb-ohci don't seem to use
> > > urb after calling completion handler (except interrupt and ring transfers
> > > where you obviosly must not free urb)
> > > but uhci uses bunch of fields in urb after calli
On Mon, Mar 18, 2002 at 12:10:31AM +0100, Stephan Feder wrote:
> To be precise: the failures I am talking about are those that could
> occur while talking to real devices, not errors like OOM and illegal
> URBs (e.g. URBs with transfer_buffer=0 and transfer_buffer_length!=0). I
> do not know in wh
To be precise: the failures I am talking about are those that could
occur while talking to real devices, not errors like OOM and illegal
URBs (e.g. URBs with transfer_buffer=0 and transfer_buffer_length!=0). I
do not know in which category URBs with a bad pipe value fall.
Stephan Feder wrote:
...
Johannes Erdfelt wrote:
>
> uhci.c would call the completion callback when the call to submit_urb
> failed. This is a rare situation.
>
> This patch only calls the completion handler if the URB successfully
> completed immediately (as in the case of talking to the virtual root
> hub).
[patch omi
uhci.c would call the completion callback when the call to submit_urb
failed. This is a rare situation.
This patch only calls the completion handler if the URB successfully
completed immediately (as in the case of talking to the virtual root
hub).
JE
--- linux-2.4.19-pre3.orig/drivers/usb/uhci.
My previous patch which cleaned up some of the spinlocks, moved one of
the spinlocks around a call to kmem_cache_alloc. It would sometimes
erroneously call it with GFP_KERNEL.
This patch fixes the problem by always calling it with GFP_ATOMIC.
Thanks to Greg for pointing this out to me.
JE
--- l
> Anyway, usb-ohci is the type of my usb, (ASUS mobo with alimagik 1 chipset)
> and the problem may not be there at all since my the PC hangs when shutting
> down usb.c host 1 and two.
>
> I have an IBM Xircam usb camera which also freeses the PC when running
I don't think anyone will be able to
The OOPS was line 1142 of slab.c ... the slab code changed
to reject SLAB_POISON in places it previously allowed it.
I agree that poisoning-related errors need to be found and
fixed, but this wasn't one of them. Just initialization of the
"poison everything" mode. Works best with the attached
p
Pull from: http://linuxusb.bkbits.net/linus-2.5
drivers/usb/Config.help |1
drivers/usb/catc.c | 291
drivers/usb/hid-core.c | 72 +++-
drivers/usb/hid.h|3
drivers/usb/hiddev.c | 11
Hi,
On Sunday 17 March 2002 15:05, you wrote:
> Hello,
>
> I'm working on my diploma thesis, writing a java based webcam picture
> grabber. Helpfully I found your website. Thanks for your advices.
> Carefully I read your FAQs. But I didn't get the right answer. So I
> would like to tell you w
Hi,
here is a Linux Kernel USB definition of the LaCie USB CDRW burner. This
was missing from linux/drivers/usb/storage/unusual_devs.h, so the drive was
recognized by USB, but not properly installed by the USB SCSI emulation.
I tested only reading yet, but I think writing works, too. Will be t
30 matches
Mail list logo
