On Thu, 4 Apr 2002 17:45, Kashif Rajput wrote:
> I am facing problem with resetting a USB 2.0 compliant
> device(ACOM HARD DRIVE).
> The problem is that "usb_reset_device(..)" returns a
> negative value.i.e -32. The log shows that the error
You understand that negative numbers are errors?
errno 3
I am facing problem with resetting a USB 2.0 compliant
device(ACOM HARD DRIVE).
The problem is that "usb_reset_device(..)" returns a
negative value.i.e -32. The log shows that the error
comes when reprogramming of device address occurs with
in the implementation of usb_reset_device() in usb.c.
i.e
Then you can probably generate the patch you need by using "diff -u".
$ diff -u 2.4.2/drivers/usb/uhci.c 2.4.18/drivers/usb/uhci.c > PATCH
$ diff -u 2.4.2/drivers/usb/uhci.h 2.4.18/drivers/usb/uhci.h >> PATCH
By the way, when you know "it's already fixed in 2.4.18", it's worth
mentioning
On Thu, 4 Apr 2002 09:54, Greg KH wrote:
> On Thu, Apr 04, 2002 at 09:31:55AM +1000, Brad Hards wrote:
> > Not very orthogonal. Can you explain the rationale for each directory?
>
> Um, didn't the descriptions of the directories help explain that?
I like things to be explicit. Saves confusion and
On Thursday 04 April 2002 00:48, Daniel Cruz wrote:
> Hello Gentlemen,
>
> I'm new in this mailing group, also new at USB and I will start writing a
> driver for a USB device, my device only uses INT transactions and my Kernel
> is 2.4.17.
>
> Any idea for a good start point?, should I use usb-ske
On Thursday 04 April 2002 00:43, Greg KH wrote:
> On Wed, Apr 03, 2002 at 09:36:09PM +0200, Oliver Neukum wrote:
> > Should we not have a seperate directory for input devices ?
>
> They go in the class/ directory, as they are HID drivers.
Not all of them. Thus you seperate HID proper from things
Your email is to a list so your "disclaimer" is a little late.
On Thu, 4 Apr 2002, Avinash natarajan wrote:
> hi...
> We are developing a linux usb device driver for usb adsl modem.
> We are facing some problem.
> While our driver is working well for OHCI hostcontroller (SiS, Compaq chip
On Thu, Apr 04, 2002 at 10:16:31AM +1000, Brad Hards wrote:
> On Thu, 4 Apr 2002 09:54, Greg KH wrote:
> > On Thu, Apr 04, 2002 at 09:31:55AM +1000, Brad Hards wrote:
> > > Not very orthogonal. Can you explain the rationale for each directory?
> >
> > Um, didn't the descriptions of the directories
hi...
We are developing a linux usb
device driver for usb adsl modem.
We are facing some problem.
While our driver is working well
for OHCI hostcontroller (SiS, Compaq chipsets), it is not fully
functional with UHCI host controller(VIA chipset).
The problem seems to be in the
d
Hello,
I saw a posting on the list on a short
write problem. I have been seeing that a few
times on my setup as well, with a csr
module. But I don't quite get what a short
write is , and who flags it off.. I read the
exhange but did not quite get the reason
behind short writes. a preliminary ch
I can't answer you directly, and perhaps my information is old, but my
understanding is that there is a sample device driver (dabusb) which is part
of the latest kernel tree. Features:
- Supporting multiple devices:
- Claiming an interface
- Setting configuration and alternate settings
- S
On Wed, Apr 03, 2002 at 07:21:21PM -0700, Patrick J. Kobly wrote:
>
> I'm sending this out now, so that I can get comments, recommendations and
> device ID's for Samsung MP3 players that I may be able to support.
Is there any reason this has to be a kernel driver? Can't you just use
usbfs or l
On Wed, 2002-04-03 at 20:06, Daniel Cruz wrote:
> Please enlight me on that, why is USB time critical?... I understand is not
> greatly fast, but there si anything else?..
If you use Isoc pipe it will probably be serviced around few
milliseconds, but in theory the request can be just dropped on
Hello,
The included patch (against 2.4.18 - a 2.5 one will be coming along soon) adds
support for the Samsung Uproar MP3 phone, and the YP-20S MP3 player. It
appears that the same protocol is used in all of Samsung's USB MP3 devices, so
anyone with such a device not supported by this code shou
On Thu, 4 Apr 2002 11:26, Greg KH wrote:
> Ok, that's fine. I will create a README in the main drivers/usb/
> directory pointing people to what is in each directory.
nice
> So let's try this again:
> core/ - this is for all of the core USB code,
> includ
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.581 -> 1.582
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.582 -> 1.583
# drivers/usb/usb-ohc
On Wed, Apr 03, 2002 at 06:10:34PM -0800, Daniel Cruz wrote:
>
> The firmware in the microcontroller is written to be used with a HID driver,
> so that is the driver I'm using now, however since timing is very important
> in my application, I think is better to go with a device-specific driver.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.583 -> 1.584
#CREDIT
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.571 -> 1.572
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.579 -> 1.580
#MAINTAINER
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.580 -> 1.581
# drivers/usb/usbnet.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.574 -> 1.575
# include/linux/hidde
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.570 -> 1.571
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.578 -> 1.579
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.568 -> 1.569
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.576 -> 1.577
# drivers/usb/hid.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.559 -> 1.560
# include/linux/hidde
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.555 -> 1.556
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.577 -> 1.578
# drivers/usb/rtl8150
> On Wed, Apr 03, 2002 at 06:10:34PM -0800, Daniel Cruz wrote:
> >
> > The firmware in the microcontroller is written to be used with a HID
driver,
> > so that is the driver I'm using now, however since timing is very
important
> > in my application, I think is better to go with a device-s
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.575 -> 1.576
# drivers/usb/konicaw
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.573 -> 1.574
# drivers/usb/hcd.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.567 -> 1.568
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.569 -> 1.570
# drivers/usb/uhci.
Pull from: bk://linuxusb.bkbits.net/linus-2.5
CREDITS |1
Documentation/usb/hiddev.txt | 60 ++
Documentation/usb/proc_usb_info.txt | 185 +++-
Documentation/usb/silverlink.txt | 76 +++
MAINTAINERS | 16
driv
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.572 -> 1.573
#drivers/usb/audio.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.558 -> 1.559
# drivers/usb/Config.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.553 -> 1.554
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.566 -> 1.567
# drivers/usb/usb.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.562 -> 1.563
# drivers/usb/hcd/ohc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.565 -> 1.566
# drivers/usb/hcd/ohc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.548 -> 1.549
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.564 -> 1.565
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.563 -> 1.564
# drivers/usb/pegasus
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.551 -> 1.552
# drivers/usb/hpusbsc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.556 -> 1.557
# drivers/usb/kaweth.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.561 -> 1.562
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.554 -> 1.555
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.560 -> 1.561
# drivers/usb/serial/
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.544 -> 1.545
# Documentation/usb/p
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.551 -> 1.551.1.1
# drivers/usb/hu
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.557 -> 1.558
# drivers/usb/pegasus
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.546 -> 1.547
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.549 -> 1.550
# drivers/usb/devices
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.543 -> 1.544
# drivers/usb/hcd/ehc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.542 -> 1.543
# drivers/usb/usb-ohc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.541 -> 1.542
#include/linux/usb.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.550 -> 1.551
# Documentation/usb/p
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.547 -> 1.548
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.540 -> 1.541
# drivers/usb/hcd/ehc
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.545 -> 1.546
# drivers/usb/uhci.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.539 -> 1.540
# drivers/usb/hcd
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet1.538 -> 1.539
# drivers/usb/printe
Note, there are 47 patches in this thread, if you don't want to see them
all, kill this thread now :)
thanks,
greg k-h
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
On Mon, Apr 01, 2002 at 04:55:46PM -0800, Greg KH wrote:
> On Mon, Apr 01, 2002 at 04:45:20PM -0800, Greg KH wrote:
> >
> > Ok, here's a patch that does it.
>
> That patch was for 2.5, here's one for 2.4:
Yes, both of them are OK. Thanks.
>
> thanks,
>
> greg k-h
>
>
> diff -Nru a/drivers/
On Thu, 4 Apr 2002 12:20, Daniel Cruz wrote:
> I'm using a Microchip microcontroller with low speed USB support, the
> microcontroller with a minimum set of peripherals will conform a board for
> a
> robotics application so basically the board will read information from
> encoders and analog i
On Wed, 3 Apr 2002, Greg KH wrote:
>Do you have to write a kernel driver? Can you just use usbfs or libusb
>to talk to your device from userspace? It handles INT transactions
>pretty well.
libusb supports INTs? Do you mean via BULK calls, I looked at the
CVS code and it doesn't look like the
On Wed, 3 Apr 2002 15:09, Greg KH wrote:
> Hi all,
> drivers/usb will have the following subdirectories:
> class/ all USB class drivers
> net/all USB network drivers
> class:
> acm.caudio.h hid-core.c hiddev.c hid-input.c usbkbd.c
> audio.c bluetoo
> On Wed, Apr 03, 2002 at 02:48:00PM -0800, Daniel Cruz wrote:
> >
> > Hello Gentlemen,
> >
> > I'm new in this mailing group, also new at USB and I will start writing
a
> > driver for a USB device, my device only uses INT transactions and my
Kernel
> > is 2.4.17.
> >
> > Any idea for a
Oliver Neukum wrote:
> On Wednesday 03 April 2002 20:21, you wrote:
>
drivers/usb will have the following subdirectories:
class/ all USB class drivers
controller/ all USB device controller drivers
core/ the USB core code (both for devices and hos
On Wed, Apr 03, 2002 at 02:48:00PM -0800, Daniel Cruz wrote:
>
> Hello Gentlemen,
>
> I'm new in this mailing group, also new at USB and I will start writing a
> driver for a USB device, my device only uses INT transactions and my Kernel
> is 2.4.17.
>
> Any idea for a good start point?, should
On Wed, Apr 03, 2002 at 09:36:09PM +0200, Oliver Neukum wrote:
>
> Should we not have a seperate directory for input devices ?
They go in the class/ directory, as they are HID drivers.
thanks,
greg k-h
___
[EMAIL PROTECTED]
To unsubscribe, use the l
Date: Mon, 25 Mar 2002 15:22:50 -0500
From: Chris Hanson <[EMAIL PROTECTED]>
From: David Brownell <[EMAIL PROTECTED]>
Date: 2002-03-25 18:52:29
> Meanwhile, though, if eliminating the 4k limit seems like a good idea,
> may I suggest applying this patch to the kernel
--
Tom Rushworth
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Hello Gentlemen,
I'm new in this mailing group, also new at USB and I will start writing a
driver for a USB device, my device only uses INT transactions and my Kernel
is 2.4.17.
Any idea for a good start point?, should I use usb-skeleton as a start
point, cause I read it only supports Bulk tran
On Wednesday 03 April 2002 20:21, you wrote:
> >>drivers/usb will have the following subdirectories:
> >>class/ all USB class drivers
> >>controller/ all USB device controller drivers
> >>core/ the USB core code (both for devices and hosts)
> >>fs/
On Wed, Apr 03, 2002 at 11:06:22AM -0800, David Brownell wrote:
> > Ok, here's a first cut at a directory restructure for the drivers/usb
> > directory. Please let me know if you like it or not (if no one
> > responds, I'll assume you like it :)
>
> Seems good to me except that I'd put "fs" into
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:59:57-08:00, [EMAIL PROTECTED]
Sorry, I messed up on the email address, Vojtech did this patch.
> USB
>
> fixes for 64bit processors
>
> drivers/usb/catc.c |4 ++--
> drivers/usb/hcd
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 17:01:20-08:00, [EMAIL PROTECTED]
> USB uhci
>
> bugfixes
>
> drivers/usb/uhci.c | 34 ++
> 1 files changed, 22 insertions(+), 12 deletions(-)
# This is a BitKeeper
On Wed, Apr 03, 2002 at 09:47:50AM -0800, Stephen J. Gowdy wrote:
> Hi Greg,
> Would "device" be better than "controller"? I would find that less
> confusing (and would help the tab completion issue that Oliver mentioned).
Yes, that sounds good.
thanks,
greg k-h
_
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:58:32-08:00, [EMAIL PROTECTED]
> USB pegasus driver
>
> semaphore cleanup and proper link detection
>
> drivers/usb/pegasus.c | 16 +++-
> 1 files changed, 7 insertions(+), 9 deletion
> Ok, here's a first cut at a directory restructure for the drivers/usb
> directory. Please let me know if you like it or not (if no one
> responds, I'll assume you like it :)
Seems good to me except that I'd put "fs" into "core". Sure
it's optional, but when it's around it's always part of usb
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:55:38-08:00, [EMAIL PROTECTED]
> USB hcd core
>
> update with the 2.5 version of hcd
>
> drivers/usb/hcd.c | 394 ++
> drivers/usb/hcd.h |2
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:57:23-08:00, [EMAIL PROTECTED]
> USB ohci driver fixes
>
>- An oopsable bug affecting unlink of interrupt
> transfers. Fix mirrors one done ages ago for ISO.
> (Original pat
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:52:19-08:00, [EMAIL PROTECTED]
> USB CDCEther driver update
>
> 1. adds support for devices that don't have the interrupt endpoint, which is
>basically Sharp Zaurus SL-5000D support. Untest
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 17:02:31-08:00, [EMAIL PROTECTED]
> USB
>
> Configure.help, Config.in, and Makefile update for all of the recent changes
>
> Documentation/Configure.help | 66 ++-
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:38:48-08:00, [EMAIL PROTECTED]
> USB visor driver
>
> added support for the palm i705.
> Thanks to Thomas Riemer for the device information.
>
> drivers/usb/serial/visor.c |8 +++-
> driv
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:53:51-08:00, [EMAIL PROTECTED]
> USB
>
> added rtl8150 driver
>
> CREDITS |1
> drivers/usb/rtl8150.c | 762 ++
> 2 files changed
On Wed, Apr 03, 2002 at 10:45:09AM -0800, Greg KH wrote:
> [EMAIL PROTECTED], 2002-04-02 16:43:50-08:00, [EMAIL PROTECTED]
> USB HID driver fixes
>
> - several fixes from 2.5 that are needed in 2.4 <[EMAIL PROTECTED]>
> - allow driver to work without hid-input <[EMAIL PROTECTED]>
> - re
Pull from: bk://linuxusb.bkbits.net/marcelo-2.4
The individual patches will be sent in follow up messages to this email.
thanks,
greg k-h
CREDITS |1
Documentation/Configure.help | 66 ++-
drivers/input/joydev.c |8
drivers/usb/CDCEther.c | 664
>>drivers/usb will have the following subdirectories:
>> class/ all USB class drivers
>> controller/ all USB device controller drivers
>> core/ the USB core code (both for devices and hosts)
>> fs/ usbfs code
>> host/ all USB ho
On Tue, Apr 02, 2002 at 09:51:49PM -0800, Stuart Lynne wrote:
> On Tue, Apr 02, 2002 at 09:12:25PM -0800, Greg KH wrote:
> > On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> >
> > I can create a linux-usb-devices list on linux-usb.org if Stuart doesn't
> > mind. Might as well ke
Hi Greg,
Would "device" be better than "controller"? I would find that less
confusing (and would help the tab completion issue that Oliver mentioned).
regards,
Stephen.
On Tue
The April 2002 issue of Embedded Systems Programming mag.
has an article on "USB Debug Tips."
It's at http://www.embedded.com/story/OEG20020321S0027
Not aimed at Linux though. :(
--
~Randy
___
[EMAIL PROTECTED]
To unsubscribe, use the last form
On Tue, Apr 02, 2002 at 02:35:52PM -0800, Stuart Lynne wrote:
> On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> > > The arm port has a USB host and client driver (or so I've been told, the
> > > client might be this one for all I know :) I've seen the host driver,
> > > and it w
On Wednesday 03 April 2002 01:21, Alan Cox wrote:
> > So all things being equal, bus was shorter than peripheral, in common
> > use, and seemed to allow us to consider them as separate entities.
>
> Wouldn't longer names be clearer. Disk space is cheap 8)
>
> controllers/
> devices/
>
On Tue, Apr 02, 2002 at 09:12:25PM -0800, Greg KH wrote:
> On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
>
> I can create a linux-usb-devices list on linux-usb.org if Stuart doesn't
> mind. Might as well keep all of the relevant lists in the same place :)
Sure or we can leave
On Tue, Apr 02, 2002 at 01:56:21PM -0800, Stuart Lynne wrote:
> > - can I add the safe_serial driver to the tree? I have had some
> > people ask me about something like this in the past, thanks
> > for writing it.
>
> Yes.
I added the safe_serial driver to the existing 2.5 tree,
Hi all,
Ok, here's a first cut at a directory restructure for the drivers/usb
directory. Please let me know if you like it or not (if no one
responds, I'll assume you like it :)
drivers/usb will have the following subdirectories:
class/ all USB class drivers
controller/
1 - 100 of 108 matches
Mail list logo
