On Sat, 20 Dec 2003 17:07:10 -0800, Greg KH [EMAIL PROTECTED] said:
Greg On Fri, Dec 19, 2003 at 05:52:00PM -0800, David Mosberger
Greg wrote:
The ipaq USB driver in 2.6.0 didn't work for me. I got the
attached Badness in local_bh_enable backtrace when ppp tried to
connect to my
$B%a%kM'[EMAIL PROTECTED](B(>_<)$BCgNI$/$J$C$?$i2q$C$?$j$G$-$^$9$%!A!)!)(B
(B
(B
(B
(B
(B---
(BThis SF.net email is sponsored by: IBM Linux Tutorials.
(BBecome an expert in LINUX or just sharpen your skills. Sign up for IBM's
(BFree
Some people have suggested that the ADU200 can be accessed
from user space thru the bulk endpoint routines in libusb.
Here is what prevents an ADU200 from using libusb-0.1.7
from uhci_submit_bulk() function of uhci-hcd.c
/* Can't have low speed bulk transfers */
if
On Sun, Dec 21, 2003 at 01:40:05PM -0500, John Homppi wrote:
Some people have suggested that the ADU200 can be accessed
from user space thru the bulk endpoint routines in libusb.
Here is what prevents an ADU200 from using libusb-0.1.7
from uhci_submit_bulk() function of uhci-hcd.c
Thanks Sergey,
I will try it with USBDEVFS_URB_TYPE_INTERRUPT.
--
From: Sergey Vlasov
Sent: Sunday, December 21, 2003 2:33 PM
To: '[EMAIL PROTECTED]'
Subject:Re: [linux-usb-devel] ADU200 (PIC16C745) incompatible with libusb
devio.c does NOT provide ioctls for interrupt
Hi David,
as you might remember we discussed moving memory allocations from
the usb_submit_urb() path to usb_alloc_urb() to speed up the former
codepath.
Should an URB be bound to a specific device, or to an endpoint at
allocation time?
Regards
Oliver
Hello,
I just acquired usb-storage enabled digital camera and I get below message on
the console when I tryed to attatch it to my computer:
==
hub 2-2:1.0 new USB device on port 2, assigned address 3
Initializing USB
John Homppi wrote:
libusb-0.1.7 does NOT provide interrupt endpoint handling.
devio.c does NOT provide ioctls for interrupt writes and reads.
I can't get to SourceForge's CVS server to verify the details right now,
but there is a thread entitled Bulk Write Problem on libusb-devel (at
Hi all, and thanks for the heads up on the side, John!
On Sun, Dec 21, 2003 at 10:33:06PM +0300, Sergey Vlasov wrote:
On Sun, Dec 21, 2003 at 01:40:05PM -0500, John Homppi wrote:
libusb-0.1.7 does NOT provide interrupt endpoint handling.
Yes, this is a problem.
What is the reason for this?
Hello,
I recommend that you look mailing list for libusb:
https://sourceforge.net/mailarchive/forum.php?forum_id=5425
Into CVS you have a new version with functions to handle interruption
USB, I think.: http://cvs.sourceforge.net/viewcvs.py/libusb/libusb/linux.c
Regards,
Josep
En/na Peter
I want to preface this by saying I've posted this on many lists, forums and
so on... I'm only resorting to the developers because I've exahusted all
other resources The following is the post that I put to my distrobutions
forum
But first my stats:
Gentoo/PPC
266Mhz G3 PPC
USB Keyboard:
On Mon, 22 Dec 2003, Anthony de Almeida Lopes wrote:
I want to preface this by saying I've posted this on many lists, forums and
so on... I'm only resorting to the developers because I've exahusted all
other resources The following is the post that I put to my distrobutions
forum
12 matches
Mail list logo
