Re: OS independent , Platform independent USB device driver
- From: Janaka <janakas@xxxxxxxxxxxx>
- Date: Sun, 11 Jan 2009 19:42:57 -0800 (PST)
Hi Tim,
I have to disgree with you, because this kind of assertion ....Ok. We'll agree to disagree on this.
Libusb provides an interface that is much like WinUSB on Windows. NeitherWhat you are describing here is the standard USB communications and
of them are extra-friendly easy access wrappers. Both are just mappings of
the kernel-level interfaces to user-mode. In order to use either libusb or
WinUSB successfully, you really do have to write a user-mode device driver.
You have to understand descriptors, classes, interfaces, endpoints, pipes,
packets, frames, URBs, and control messages. It requires a level of
expertise that I associate with "device drivers", not "easy access
wrappers".
infrastructure formats as described in Chapter 8 (as I could remember)
on the USB spec. Who ever uses Libusb surely needs to understand how
USB works. But as far as I am concerned that code does NOT become a
"User space device driver" just because it has to comply with USB
communications spec. As far as I know libUsb based user code does not
have Hardware specific interactions nor time critical response needs
nor interrupts. All of these gets handled on the lower level native
device driver.
Cheers
Janaka
.
- Follow-Ups:
- Re: OS independent , Platform independent USB device driver
- From: Tim Roberts
- Re: OS independent , Platform independent USB device driver
- Prev by Date: Re: Kernel should not handle my ICMP Request
- Next by Date: gathering tx/rx Stats
- Previous by thread: Kernel should not handle my ICMP Request
- Next by thread: Re: OS independent , Platform independent USB device driver
- Index(es):
Relevant Pages
|
