> If we imagine a scenario where host sends a IN/OUT token and device
> consistenly responds with NAK. what does the driver do in that case ?
Whatever it wants. Usually it's correct to keep waiting for the
deice to provide the data.
> Does the driver timeout and abandaon the transaction in such
On Friday 15 December 2006 11:31 am, Jonathan Fletcher wrote:
> Hello, I'm developing a driver for a board with the OMAP2430, and I
> understand that:
>
> " For Texas Instruments parts including the DaVinci tms320dm644x, TUSB
> 6010, and OMAP 2430, there's a much more robust fork of that Mentor
Am Sonntag, 19. November 2006 21:19 schrieb Alex Girchenko:
> Hello.
> We've developed a kernel module (aka driver) to support a portable
> data collector Argox PT-12
> (http://www.argox.com/en/Product3.aspx?ProductID=35). It's been tested
> and is in production now. I see a point in including this
On 10/15/06, Ville Syrjälä <[EMAIL PROTECTED]> wrote:
> Why isn't this an input driver?
Because I didn't know about them ;)
Am I wrong in thinking that there is no handler for remote controls?
Should I use the general-purpose one?
Marc-Antoine Avon-Charreyron
--
On Sun, Oct 15, 2006 at 07:06:34PM -0400, Marc-Antoine Avon Charreyron wrote:
> This is the full post I sent on the linux-kernel list earlier today
> (but with the fixed a memory leak, thanks Oliver).
>
>
> Hello, the following is a driver for a usb remote control with product
> id 13ec and vendo
This is the full post I sent on the linux-kernel list earlier today
(but with the fixed a memory leak, thanks Oliver).
Hello, the following is a driver for a usb remote control with product
id 13ec and vendor id 000a (it came with a Asus tv card). I'm
looking for comments and people to help tes
Am Sonntag, 15. Oktober 2006 18:51 schrieb Marc-Antoine Avon Charreyron:
> struct urb *urb;
> struct urb *urb2;
> urb = usb_alloc_urb(0, GFP_KERNEL);
> if (!urb) {
> return -ENOMEM;
> }
> urb2 = usb_alloc_urb(0, GFP_KERNEL);
>
On Fri, Jun 30, 2006 at 08:47:13PM -0300, Manuel Naranjo wrote:
> Hi:
> I have made a driver that uses usb-serial to make AIRcable USB Devices
> work. The device is released under the GPL license. What I would like to
> know if there is any way to report this hardware as compatible, with
> Linux
> > > First of all, are driver versions located anywhere in the sysfs tree?
> > > I've looked through the code of some devices and didn't see any. What
> > > I'ld like to do is add a software driver version to the sysfs tree but
> > > don't know the proper location to do so. I'm thinking of
> > >
On Wed, 28 Sep 2005, Randy.Dunlap wrote:
> On Wed, 28 Sep 2005, Bill Rees wrote:
>
> > Hi All,
> >
> > First of all, are driver versions located anywhere in the sysfs tree?
> > I've looked through the code of some devices and didn't see any. What
> > I'ld like to do is add a software driver ve
(btw, Bill, reply-to-all is customary on almost all Linux-related
mailing lists)
On Wed, 28 Sep 2005 23:01:01 -0400 (EDT) Alan Stern wrote:
> On Wed, 28 Sep 2005, Bill Rees wrote:
>
> > Randy.Dunlap wrote:
> >
> > >On Wed, 28 Sep 2005, Bill Rees wrote:
> > >
> > >>Hi All,
> > >>
> > >>First of
On Wed, 28 Sep 2005, Bill Rees wrote:
> Randy.Dunlap wrote:
>
> >On Wed, 28 Sep 2005, Bill Rees wrote:
> >
> >
> >
> >>Hi All,
> >>
> >>First of all, are driver versions located anywhere in the sysfs tree?
> >>I've looked through the code of some devices and didn't see any. What
> >>I'ld like
Randy.Dunlap wrote:
On Wed, 28 Sep 2005, Bill Rees wrote:
Hi All,
First of all, are driver versions located anywhere in the sysfs tree?
I've looked through the code of some devices and didn't see any. What
I'ld like to do is add a software driver version to the sysfs tree but
don't know t
Randy.Dunlap wrote:
On Wed, 28 Sep 2005, Bill Rees wrote:
Hi All,
First of all, are driver versions located anywhere in the sysfs tree?
I've looked through the code of some devices and didn't see any. What
I'ld like to do is add a software driver version to the sysfs tree but
don't know t
On Wed, 28 Sep 2005, Bill Rees wrote:
> Hi All,
>
> First of all, are driver versions located anywhere in the sysfs tree?
> I've looked through the code of some devices and didn't see any. What
> I'ld like to do is add a software driver version to the sysfs tree but
> don't know the proper locati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Many thanks for having inspected the code.
I hadn't worried about memory leaks yet.
> + trust_table[0] = dev;
>
> 6. Why have a table if only one is allowed?
Only one is allowed because there is no table management yet
> In
> +static void trust_
Am Sonntag, 15. Mai 2005 15:41 schrieb Gabriele Giacone:
> This is a patch against a mISDN patched 2.6.10 kernel.
> I had also CCed i4l developers list but posts by non-members must be
> approved by moderator Karsten Keil.
+static void trust_disconnect(struct usb_interface *interface)
+{
+ t
Am Sonntag, 15. Mai 2005 04:27 schrieb Gabriele Giacone:
>
> Hello to everybody,
>
> At http://digilander.libero.it/trustusbta I published a first partially
> working version of a driver for Trust ISDN USB TAs. It should also work
> for Billion, Dex, Microcom and Hamlet tas.
>
> Excluding the pa
Am Donnerstag, 28. April 2005 22:29 schrieb Roberto Roccatello:
> Hi
> I'm trying to get this "U.S. Robotics 56K Faxmodem USB" working
> with cdc-acm driver but with no results.
> I would like to know what do you think about this output:
>
> [EMAIL PROTECTED]:~$ tail -f /var/log/messages
> usb 1-1
Thanks Greg and Pete for the replies.
As far as I can see, the device is working properly in both bulk and iso mode,
as I managed to write a simular driver for the (sorry to mention) windows os.
But things are getting allong now on Linux as well.
Sorry for being a noob, but I didn't realize tha
On Thu, 24 Mar 2005 16:37:21 +0100 Paul Koster <[EMAIL PROTECTED]> wrote:
> When I disable the iso URB submitting, the bulk works well for
> about 2 minutes. Unloading the
> driver results most of the time in kernel panics, but only when I actively
> used the driver in a open/close session.
I
On Thu, Mar 24, 2005 at 04:37:21PM +0100, Paul Koster wrote:
> Hi guys,
>
> I'm currently making my first steps in USB driver development as I am
> developping a linux driver for an optical fiber to USB convertor. I managed
> to successfully write a driver for the 2.6.9 kernel, but when I upgrad
what is in /proc/bus/usb/devices? (I find that easier to read).
On Wed, 26 Jan 2005, Nick Sillik wrote:
> Linux USB-Gurus
>
> I am writing in search of a little help on a kernel module/patch to add
> functionality to the Maxtor OneTouch[1] external hard drive's user
> programmable button. It will
It works like a charm. Unfortunately I can't get ahold of the original
author to see if he's still working on it... Do you have any idea's on
how to contact him?
Otherwise, I'll take over it's development and maintain-ment and such.
Nick Sillik
[EMAIL PROTECTED]
Matthew Dharm wrote:
You may want to
Wow,
Thanks a lot, this is exactly what i was looking for. Such a huge help.
I can hopefully have this done in a few weeks. I'm sure you'll be
hearing from me again for help.
Nick Sillik
[EMAIL PROTECTED]
Matthew Dharm wrote:
You may want to take a look at the attached e-mail I got a while
You may want to take a look at the attached e-mail I got a while back...
it's a hack to connect the onetouch button to the input subsystem as an
extension of the usb-storage driver.
It's old, and likely suffering from bitrot, but should be useful to
somebody.
Matt
On Wed, Jan 26, 2005 at 04:15:0
To be honest, I had not considered a usbserial interface. But after
taking some time to look at other drivers in the serial group, I think
it would be a good fit. The only have one concern at this time. When
copying data into to the tty buffer for the user to read, it looks
like it can drop data if
>
> Fair enough. What's the difference becides the usb-serial vs. char
> interface?
>
garmin has changed its communication protocol when they switched
from rs232 to usb, dropping checksums handshakes etc.
my driver can operate in both protocol modes. It can translate
the garmin older serial protoc
On Sat, Nov 06, 2004 at 07:22:42AM +0100, Hermann Kneissel wrote:
> On Wednesday 03 November 2004 17:12, Greg KH wrote:
> >
> > I thought this driver used the usb-serial interface, not it's own minor
> > number interface. Why would that interface not work properly for this
> > type of device?
> >
On Wednesday 03 November 2004 17:12, Greg KH wrote:
>
> I thought this driver used the usb-serial interface, not it's own minor
> number interface. Why would that interface not work properly for this
> type of device?
>
Its a different driver, developt independently from my version.
Hermann
--
On Wed, Nov 03, 2004 at 05:51:50AM +, Marty Boos wrote:
> Hello,
>
> I have attached a patch to the 2.6.9 kernel containing a driver for
> Garmin GPS devices (www.garmin.com). I have only tried it with a GPS18
> so far and I would invite others with different devices to join me in
> developmen
On Fri, Jul 30, 2004 at 02:43:06PM +0200, Florian Echtler wrote:
>
> - Will it be incorporated into one of the next kernel releases?
If you sent it to me (and cc: the list) in patch form with the proper
"Signed-off-by:" line as the Documentation/SubmittingPatches file
describes, I'll consider it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again, everyone..
> open is much less of an issue because after open I can fork and issue
> two reads anyway. Quite a few drivers simply use a semaphore to
> serialize read operations.
http://www.fs.tum.de/~echtler/idmouse/linux-2.6.7-idmouse.pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> open is much less of an issue because after open I can fork and issue
> two reads anyway. Quite a few drivers simply use a semaphore to
> serialize read operations.
Hmm.. I updated the driver and fixed most issues (indentation and open()).
See http
On Iau, 2004-07-29 at 00:10, Florian Echtler wrote:
> once at the same time. I was planning to have open() update the buffer
> with the current picture (and block when already opened) and read() just
> return the current buffer contents, at whatever position desired (and
> I know that the offset p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > // reset the buffer position
> > dev->buffer_pos = 0;
> > If you are allowing multiple openers you cannot reset the buffer.
> > And run it through indent.
> I don't see how you can do this with a single opener since it can
> then be threaded a
On Mer, 2004-07-28 at 19:39, Oliver Neukum wrote:
> // reset the buffer position
> dev->buffer_pos = 0;
>
> If you are allowing multiple openers you cannot reset the buffer.
> And run it through indent.
I don't see how you can do this with a single opener since it can
then be threaded and is
Am Mittwoch, 28. Juli 2004 15:23 schrieb Florian Echtler:
> Andreas Deresch and I have written a driver for the fingerprint
> sensor in the Siemens ID USB Mouse (a FingerTIP sensor, also from
> Siemens). The mouse is cheaply available (ours did cost 15 Euro),
> and provides a decent grayscale image
Linux drivers don't differentiate between USB1 and USB2 for much... there
are a couple of places (max packet size, IRQ intervals, etc.), but you
should be pretty safe for most things.
Matt
On Tue, Apr 20, 2004 at 11:59:42PM +0100, Michael Pacey wrote:
> Hi,
>
> I'm need some advice on reverse en
On Wed, 14 Apr 2004, Duncan Sands wrote:
> Hi Alan, things were going fine until windows crashed (my disassembler
> runs on windows) and the disassembly got corrupted.
I blame it all on Bill Gates. :-)
> Since it is in a
> proprietary format, I am having some trouble recovering it. Maybe I
> n
On Tue, 13 Apr 2004, Duncan Sands wrote:
> proc_setintf contains the following line:
>
> if (interface->dev.driver) {
>
> Doesn't that mean that a lock needs to be
> taken to protect against a change in the driver?
Yes it does. As discussed recently on this list, the usb bus subsystem
> Have you made any headway trying to decipher the VIA UHCI filter driver?
> I think the one you were looking at must have been their USB-1.1 driver;
> maybe it would be better to examine the USB-2.0 driver, which is the one
> that would be installed for a VT6202. That chip makes a good prototype
On Tuesday 13 April 2004 21:29, David Brownell wrote:
> Duncan Sands wrote:
> > proc_setintf contains the following line:
> >
> > if (interface->dev.driver) {
> >
> > Doesn't that mean that a lock needs to be
> > taken to protect against a change in the driver?
>
> Looks like it. The patch
Duncan Sands wrote:
proc_setintf contains the following line:
if (interface->dev.driver) {
Doesn't that mean that a lock needs to be
taken to protect against a change in the driver?
Looks like it. The patches I sent in (now in Greg's tree and -mm)
didn't cover all the missing locks in us
Christian,
On Fri, Oct 17, 2003 at 05:35:46PM +0200, Christian Grigis wrote:
> We are developing a board based on a PPC405 processor, and we are using
> a Philips ISP1160 USB host controller.
I also had such a beast under my fingers some time ago (PPC405+ISP1160)
and run into the same mess. Ther
I re-submit the urbs in the completion handlers. Is
that a good idea? I read some posts that mentioned
resubmitting urbs in a tasklet. If I have such a
tasklet for the resubmission as well as for the error
recovery, can I expect much performance gain? Thanks.
Resubmitting requests in completion h
On Thu, 25 Sep 2003, Neil Whelchel wrote:
> > What kind of endpoints are these? Bulk?
>
> These are interrupt transfer endpoints, yet anoter jacked up way of doing
> things.. (Tons of bus chatter sending empty packets at a syncronous time
> base for an asyncronous data protocol.) This thing must
Hello,
First off, thank you very much for writing back to me..
I have included my comments (answers to your questions) within the
message..
On Tue, 23 Sep 2003, Greg KH wrote:
> On Mon, Sep 22, 2003 at 05:44:49PM -0700, Neil Whelchel wrote:
> > Hello,
> > I am in the middle of writing a driver f
> Different host controller silicon reports different
> faults for I/O attempts during that 1/8+ second.
> I don't know any host controller that will report
> an -EOVERFLOW in that situation though.
Sorry, I was bulls***ing before. The error status is
-EPROTO.
> See the Linux 2.6 kerneldoc for U
ZHOU DX wrote:
In my completion handler, I called usb_clear_halt if
urb->status<0. When the cable is unplugged, the
completion handler is called with urb->status =
-EOVERFLOW (why is it called before "disconnect"?),
The disconnect() callback is issued when khubd gets
around to it. Which will be o
> Hook up a serial console, likely you'll see a kernel
> oops trace appear on that console. Analyse it with
> ksymoops on 2.4 kernels; 2.6 is easier to develop
> with
> since "kksymoops" is built in.
Thanks. I will follow your suggestion in the near
future.
Last night, I found the problem causi
When the system hangs, the
"Caps lock" and "Scroll lock" lights on the keyboard
turn on. After reboot, I can not find any trace from
the syslog. Can anyone give me some hints about how to
debug this kind of situation and which part of the
code I should pay more attention to ? Thanks.
Hook
On Tue, Sep 23, 2003 at 10:37:48PM -0700, ZHOU DX wrote:
> Hi,
>
> I am working on an USB2 camera driver on Linux RH9,
> kernel 2.4.20-xx. The driver works OK except that it
> hangs the kernel when I hot-unplug the cable.
Without seeing the source for your driver, it is very difficult to
determi
On Mon, Sep 22, 2003 at 05:44:49PM -0700, Neil Whelchel wrote:
> Hello,
> I am in the middle of writing a driver for the Cypress M8. This is a
> way-too-goofy USB to serial converter.
> I have a fairly clear understanding of what I need to do to make it work,
> but here is where I run into issues..
On Thu, 29 May 2003, Oliver Neukum wrote:
>
> ax_control_msg: sleeping broken. You cannot set your task's state
> before calling usb_submit_urb because it may allocate memory, which
> may sleep and change the state to TASK_RUNNING
Any suggestions on how to best fix that? I haven't dealt much wi
Ok, well it's not perfect. I'm getting the following error quite often:
NETDEV WATCHDOG: eth1: transmit timed out
ax8817x.c: eth1: Transmit timeout, URB cec65e40 status 0
>>> "David Rippel" <[EMAIL PROTECTED]> 05/29/03 08:59AM >>>
I just wanted to thank everyone for making an effort to get this d
I just wanted to thank everyone for making an effort to get this driver put together!
I got it working with no complications on 2.4.20-gentoo-r5. I'll be doing some more
testing and report any problems.
Regards,
David.
>>> Oliver Neukum <[EMAIL PROTECTED]> 05/29/03 08:22AM >>>
> I've thrown u
> I've thrown up a new rev of the driver that now includes some basic
> ethtool & mii-tool support. The mii output isn't quite correct just
> yet, but it does know link status which helps with RedHat init scripts
> so it knows whether or not to run DHCP.
>
> http://www.davehollis.com/~dhollis/ax8
David T Hollis wrote:
I have now thrown up a port of the TiVo driver that builds cleanly and
installs though I have not tested it with my device since I don't have
it handy. For those really daring folks, it's available at
http://www.davehollis.com/~dhollis/ax8817x.tar.gz.
There aren't subst
David Rippel wrote:
Does anyone have a working driver for (or willing to put one together?) for the ASIX AX88172 usb-to-ethernet controller & RealTek RTL8201 PHY (better known as the linksys usb200m nic, also seen as a netgear product)?
There's documentation available at the following urls:
http
Kevin Cernekee wrote:
On Wed, 28 May 2003, David Rippel wrote:
Does anyone have a working driver for (or willing to put one together?)
for the ASIX AX88172 usb-to-ethernet controller & RealTek RTL8201 PHY
(better known as the linksys usb200m nic, also seen as a netgear
product)?
TiVo appa
On Wed, 28 May 2003, David Rippel wrote:
> Does anyone have a working driver for (or willing to put one together?)
> for the ASIX AX88172 usb-to-ethernet controller & RealTek RTL8201 PHY
> (better known as the linksys usb200m nic, also seen as a netgear
> product)?
TiVo apparently wrote a GPL dr
David Rippel wrote:
Does anyone have a working driver for (or willing to put one together?) for the ASIX AX88172 usb-to-ethernet controller & RealTek RTL8201 PHY (better known as the linksys usb200m nic, also seen as a netgear product)?
There's documentation available at the following urls:
http
On Wed, 10 Jul 2002 11:34, shino korah wrote:
> To make sure the driver got loaded correctly I tried
> connecting a USB mouse to the system. (I'm using a NEC
> PCI card for USB 2.0)
>
> I ran mouseconfig it detects only the PS/2 mouse not
> the USB mouse?
Two points:
1. mouseconfig might not be a
Hi
Finally I succesfully loaded all USB related
drivers
my lsmod gives
Module Size Used by
usb-uhci-hcd 20432 0 (unused)
ohci-hcd 23216 0 (unused)
ehci-hcd 26640 0 (unused)
usbcore75584 1 [usb-uhci-hcd
ohci-hcd
On Mon, 8 Jul 2002 11:08, shino korah wrote:
> Hi
>
> I have my 2.5.24 kernel with USB 2.0 modules ready
> (ehci-hcd). I have these modules in
> /lib/modules/2.5.24/kernel/usb directory. But when I
> boot the computer modprobe doesn't seem to detect
> these .o files.
> I can use insmod to load t
Hi
I have my 2.5.24 kernel with USB 2.0 modules ready
(ehci-hcd). I have these modules in
/lib/modules/2.5.24/kernel/usb directory. But when I
boot the computer modprobe doesn't seem to detect
these .o files.
I can use insmod to load these modules but modprobe is
not detecting it.maybe modprobe
On Sat, 2002-06-29 at 20:27, shino korah wrote:
> I want to use EHCI-HCD driver for my NEC USB 2.0 PCI
> card. I chose to use 2.5.12 kernel( I was using 2.4.2)
> but when I boots 2.5.12 gets stuck at
> Serial driver version 5.02 (2000-08-09)
First off, the 2.5 kernel series is the development tr
You seen to pick strange kernels... why did you choose 2.5.12 over the
latest version (2.5.24)? I don't actually know which is better thoug.
On Sat, 29 Jun 2002, shino korah wrote:
> Hi
>
> I want to use EHCI-HCD driver for my NEC USB 2.0 PCI
> card. I chose to use 2.5.12 kernel( I was using 2
Hi
I want to use EHCI-HCD driver for my NEC USB 2.0 PCI
card. I chose to use 2.5.12 kernel( I was using 2.4.2)
but when I boots 2.5.12 gets stuck at
Serial driver version 5.02 (2000-08-09) with
MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP
enabled
Jun 29 17:17:38 shino_korah kernel: ttyS00 at
> Do I need to write a device driver for such a device or can I mount it and
> simply use the "open" "read" "write" command to send commands back and
> forth? If yes how do I find where the it is mounted (/dev/??)?
You detail is a little thin but Possibly/probably, have you looked
at the dr
Am Freitag, 8. Februar 2002 03:25 schrieb Simon Evans:
> Hi,
>
> I have written a driver for the Konica webcam chip found in the
> Intel YC76 webcam. It uses the usbvideo, so it just acts as a
> miniport driver.
This looks like well written code.
Regards
Oliver
_
On Wed, Feb 06, 2002 at 03:01:25PM +0530, Ravi Kumar B S wrote:
> hi i found why the driver is not listed as being used. when i connect
> the device. the probe function is getting called. in that first it makes
> check on the device class signature. there it is immediately returning
> as i am g
Dmitri wrote:
>Quoting Ravi Kumar B S <[EMAIL PROTECTED]>:
>
>>Dmitri wrote:
>>
>
>>>In worst case, presence of printk's moves the memory around, and you have
>>>a stray pointer somewhere that reads or writes past the allocated
>>>memory. With printks in place, this pointer happens to point to a
Quoting Ravi Kumar B S <[EMAIL PROTECTED]>:
> Dmitri wrote:
> >In worst case, presence of printk's moves the memory around, and you have
> >a stray pointer somewhere that reads or writes past the allocated
> >memory. With printks in place, this pointer happens to point to a safe
> >place; withou
Dmitri wrote:
>Quoting Ravi Kumar B S <[EMAIL PROTECTED]>:
>
>>i am using the usb bluetooth driver. i have configured the usb bluetooth
>>driver as a module. i have two versions of the driver. one with the
>>comments, extensive debug statements(printks) etc. the other one is the
>>one which is
Quoting Ravi Kumar B S <[EMAIL PROTECTED]>:
> i am using the usb bluetooth driver. i have configured the usb bluetooth
> driver as a module. i have two versions of the driver. one with the
> comments, extensive debug statements(printks) etc. the other one is the
> one which is cleaned does not
On Wed, Jan 23, 2002 at 09:12:55PM +, Simon Evans wrote:
>
> I have written a driver for the above device. It is still not completely
> finished (multicast and stats dont work) however it survives heavy
> traffic for long periods.
>
> Although the device is based on a CATC board and has the
On Thu, 7 Jun 2001, Greg KH wrote:
> On Tue, Jun 05, 2001 at 10:27:22PM +0200, Kai Germaschewski wrote:
> > The first question is about where to put the source. AFAICS, all USB
> > drivers are kept in drivers/usb. So I'd suggest to put the USB interface
> > module there, too. The main part, the e
On Tue, Jun 05, 2001 at 10:27:22PM +0200, Kai Germaschewski wrote:
> The first question is about where to put the source. AFAICS, all USB
> drivers are kept in drivers/usb. So I'd suggest to put the USB interface
> module there, too. The main part, the extension to the hisax module needs
> to be i
On Sat, May 12, 2001 at 12:36:25PM +0200, Sancho Dauskardt wrote:
>
> If you want to use Firmware that ReEnumerates, don't do this from a
> usb-storage device !
I don't have choice. The firmware used is the same than windows. I have no spec,
and no source code at all. I prefer to load the firmw
>I've the same problem, my device driver ue a carry chips too. In november,
>i've
>ask how to solve this problem. For my driver (HH501, look last week archive),
>you load the firmware and the driver renumerate itsef. Then you can use
>it. For
>using this device, you can boot under windows, reb
On Fri, May 11, 2001 at 04:57:16PM +0200, Sancho Dauskardt wrote:
>
> At the moment finding a solution for the firmware problem (windows/nda/..)
> is more important; nobody can really test it without. Possibly somebody can
> convince carry to release binary firmware for us (basically they alrea
> The HCD developers are
>trying pretty hard to fix all the bulk urb queuing bugs, so your help
>would be much appreciated. Have you applied the recently posted patches
>for uhci and usb-ohci. I think there might have been a usb-uhci patch,
>too,
>but I'm not sure.
Of course i'm using all th
Sancho Dauskardt wrote:
>
> Hi all,
>
> attached is a patch against 2.4.4. for the 0x7CC Vendor ID family of card
> readers (www.carry.com.tw).
> These things are sold under all sorts of names (Lexar, PSI, Pixo-media...).
>
> WARNING: kernel hacking & usb experience needed to get this going !
85 matches
Mail list logo
