Phil Dibowitz wrote:
> Alan Stern wrote:
>
>> Does that error string come from usb_strerror()? My copy of libusb is
>> rather old and doesn't seem to include that routine. It would help to see
>> the actual error code returned by usb_interrupt_write().
BTW, the error from usb_interrupt_write()
Ingrese a nuestra web y aprenda todo lo que puede hacer trabajando con
madera...
http://agora.ya.com/carpinteria07
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and yo
On Sat, 2007-03-10 at 15:39 -0800, Phil Dibowitz wrote:
> while (bytes = read((int)fh, buf, SIZE)) {
> printf("writing %d bytes (%d)\n",SIZE,++i);
> if (usb_interrupt_write(udev, OUT_EP, buf, bytes, 2) < 0) {
read can return -1, at which point you stuff -1 i
Thomas Sailer wrote:
> On Sat, 2007-03-10 at 15:39 -0800, Phil Dibowitz wrote:
>> while (bytes = read((int)fh, buf, SIZE)) {
>> printf("writing %d bytes (%d)\n",SIZE,++i);
>> if (usb_interrupt_write(udev, OUT_EP, buf, bytes, 2) < 0) {
>
> read can return -1,
On Sat, 10 Mar 2007, Alan Stern wrote:
> On Sun, 11 Mar 2007, Martin Drab wrote:
>
> > how independent are different endpoints of the same alternate interface?
>
> They are completely independent. In theory anyway; individual devices may
> have specific restrictions.
OK, good to know that at
Begin forwarded message:
Date: Sun, 11 Mar 2007 04:00:06 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 8175] New: ati_remote2 module only supports remote
"channel" 1
http://bugzilla.kernel.org/show_bug.cgi?id=8175
Summary: ati_remote2 module only su
> > Anyone working on support for the Trust WB-5400 webcam?
> Could you please post more information about your device, such as the output
> of lsusb -v ? Thanks.
Can't do that yet: I was informing for a friend if maybe someone new if
there was a driver already. I'll CC him so that he can tell us
Hi Alan,
Thanks for your response. A bit more context... I dont
have a choice in kernel release.
I have the ISP1761 example driver which apparently works in
2.6.9 and I can't verify this as there isn't a
configuration for 2.6.9 for my platform.
I have modified very little to get it to 2.6.14
On Sat, 10 Mar 2007, Phil Dibowitz wrote:
> > Have you tried setting the usbfs_snoop=1 module parameter for usbcore? It
> > will dump your program's I/O activity to the system log.
>
> No, I didn't, but that's a good idea. Is there a way to change this
> on-the-fly through, say, sysfs? I couldn
On Sun, 11 Mar 2007, Phil Dibowitz wrote:
> Sadly, I'm only slightly further. I have two files that generally get
> transfered to the device:
>
> Connectivity.EZHex - this is a 'connectivity test' to transfer to the
> device
> Test.EZHex - this is a config blob for the remote.
>
> The s
On Sun, 11 Mar 2007, Martin Drab wrote:
> > And some devices are definitely known to crash if you send them a
> > control URB while they are busy doing something else.
>
> Hmm, is it just due to the bug in their firmware or is the problem rather
> in their USB chip hardware?
You'll need to ask
On Sun, 11 Mar 2007, Michael Cook wrote:
> Hi Alan,
>
> Thanks for your response. A bit more context... I dont
> have a choice in kernel release.
>
> I have the ISP1761 example driver which apparently works in
> 2.6.9 and I can't verify this as there isn't a
> configuration for 2.6.9 for my pla
Hi!
> > > Even if one doesn't use the fb console at all, radeonfb apparently
> > > is still required on some ThinkPad models to work around BIOS bugs:
> > >
> > > http://www.thinkwiki.org/wiki/Problem_with_high_power_drain_in_ACPI_sleep#Radeon_GPU_not_powered_off
> >
> >
> > s2ram should be ab
* Pavel Machek <[EMAIL PROTECTED]> wrote:
> > Probably tweaking the webpage doesnt help because people dont get
> > there - as the results plainly show it. Maybe some more automation
> > would be useful too, a tool that detects failed resume and tries all
> > those options that makes sense on
Hi!
> > Ok. To be honest, you are the first reporter that seems to have read
> > the documentation above, but not understood what to do.
>
> thanks for the compliment ;-) _I_ very much know what to do (i mailed
> the right person after all ;), but i dont really count and on the 6
(Can we get
Hello,
I noticed that there could potentially be a sort of race condition in
ohci-hcd.c file, related to interrupt handling. This caused Oops when
removing ohci_hcd driver on one device I was working with - OHCI cell on
SAMCOP chip used in ipaq h5000 devices. Please Cc: me as I am not
subscri
On Sun, 11 Mar 2007 12:47:10 +0100 (CET), Martin Drab <[EMAIL PROTECTED]> wrote:
> OK, good to know that at least on the Linux side this should be supported.
> I read some comments on the net (probably describing some ancient version
> of kernel or what), where there were some hints like that it
Thanks Alan,
It is good to get some feedback on how the buffer
manipulation should work. I appreciate you taking the
time.
>
> Did you take care about checking byte-endian issues?
>
Yep, I didn't take enough care. I thought I had, but I
have just found the URB transfer buffer is fragmented i
This patch for the linux-usb-devel tree adds two more
product ids to the dm9601 driver. These ids were found on
rebadged dm9601 devices in the wild.
Signed-off-by: Jon Dowland <[EMAIL PROTECTED]>
---
drivers/usb/net/dm9601.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff
Description: Check the return value of kmalloc() in function
stv680_start_stream(), in file drivers/media/video/stv680.c.
Signed-off-by: Amit Choudhary <[EMAIL PROTECTED]>
diff --git a/drivers/media/video/stv680.c b/drivers/media/video/stv680.c
index 6d1ef1e..f35c664 100644
--- a/drivers/media/v
Alan Stern wrote:
>> But when I transfer 64 bytes at a time, on Connectivity.EZHex, I get 19
>> successful transfers (~1.2k) and the 20th gives me an error of -110, or "No
>> error" (the read was successful).
>
> 110 is ETIMEDOUT (see include/asm-generic/errno*), which means your
> timeout expired
Phil Dibowitz wrote:
> Alan Stern wrote:
>>> But when I transfer 64 bytes at a time, on Connectivity.EZHex, I get 19
>>> successful transfers (~1.2k) and the 20th gives me an error of -110, or "No
>>> error" (the read was successful).
>> 110 is ETIMEDOUT (see include/asm-generic/errno*), which mean
On Sun, 11 Mar 2007, Pete Zaitcev wrote:
> On Sun, 11 Mar 2007 12:47:10 +0100 (CET), Martin Drab <[EMAIL PROTECTED]>
> wrote:
>
> > OK, good to know that at least on the Linux side this should be supported.
> > I read some comments on the net (probably describing some ancient version
> > of ke
> "Jon" == Jon Dowland <[EMAIL PROTECTED]> writes:
Hi,
Jon> This patch for the linux-usb-devel tree adds two more
Jon> product ids to the dm9601 driver. These ids were found on
Jon> rebadged dm9601 devices in the wild.
Jon> Signed-off-by: Jon Dowland <[EMAIL PROTECTED]>
Acked-by: Peter
24 matches
Mail list logo
