- 12 Jul, 2002 1 commit
-
-
Vojtech Pavlik authored
This cset is update of the HID drivers to the latest version, as a part of the Input merge. It finally includes ForceFeedback support by Johann Deneux, enabling ForceFeedback on new Logitech and Microsoft devices.
-
- 07 Jul, 2002 10 commits
-
-
David Brownell authored
This patch fixes two problems that have already been discussed on this list: - USB_QUEUE_BULK is rather pointless (and UHCI-specific). If drivers really want only one bulk urb queued at a time, they just shouldn't issue such urbs till others complete. FIX: remove it entirely. - USB_DISABLE_SPD is horribly named (based on a UHCI flag). What it really does is turn non-ISO short reads into errors. FIX: rename it. Now it's URB_SHORT_NOT_OK. I changed all the drivers using these two flags, including corresponding changes in the "usbfs" API. Most of the patch by volume is doc updates: - Documentation/usb/URB.txt hadn't been updated in two years (!) and was pretty out of date. It also had many details that were inappropriately specific to usb-uhci. - Most of the URB flags weren't even commented as to intent. - DISABLE_SPD was often documented as if it were SHORT_IS_OK. - There was still some doc saying how iso should use urb->next. There are also some related updates: - Some of the submit sanity checks for transfer flags were overly broad ... SHORT_NOT_OK is only for reads, NO_FSBR is for non-periodic requests, ZERO_PACKET only for writes. - The ohci-hcd code thought SHORT_NOT_OK worked for ISO. - The uhci-hcd code thought QUEUE_BULK applied to non-bulk Note that this patch doesn't update any of the "old" HCDs, including usb-ohci-hcd. In the case of usb-uhci{,-hcd} it'd have been painful to fix the QUEUE_BULK logic. That logic was, I think, the original reason to have that flag! So I count switching to "uhci-hcd" as a win already ... :)
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
into kroah.com:/home/linux/linux/BK/gregkh-2.5
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Matthew Dharm authored
This patch fixes some spelling errors and adds some BUG_ON() calls so we can make sure that all this new code is working properly.
-
Matthew Dharm authored
This patch changes how the exit code works to be cleaner, fixes the OOPS on rmmod, consolidates some anti-race code from several places to just one, and also eliminates some theoretical race conditions.
-
Matthew Dharm authored
This patch unifies all the bit tests and various flags into a single, unified system. Matt
-
Brad Hards authored
Part 2, printk fixups for a the tiglusb and emi26 drivers.
-
- 06 Jul, 2002 6 commits
-
-
Brad Hards authored
This is the first of a few janitorial fixes for printk() usage in the USB tree.
-
Linus Torvalds authored
table lock
-
Matthew Wilcox authored
Whoever did the strsep patches didn't check that ips still compiles. here's a patch.
-
Brad Hards authored
-
Brad Hards authored
Found a few typos in the input changes. Fixup patch attached.
-
Linus Torvalds authored
-
- 05 Jul, 2002 17 commits
-
-
Greg Kroah-Hartman authored
-
David Brownell authored
This fixes a couple issues I noted when I finally spent some time looking at the first version of driverfs support for usb: - "name" fields (really descriptions) aren't very useful. * for devices, they always said "USB device 0000:0000" --> Now they'll only say that when there's nothing better to be said ... --> ... and it's really device 0000:0000! It was using device descriptor fields before they were fetched from the device. --> Uses product and/or manufacturer strings, which most devices have, much like PCI uses the PCI ID database (when it's compiled in) * for interfaces, it was "figure out some name..." --> Now it combines the strings used in the usb_make_path() call with interface number --> Or in the remote chance a device provides an interface string, that's preferred. --> In general, I think the driver for each interface is best suited to describe it; I modified the hub driver to do so. - "bus_id" field * For hub ports, it was wasting code: we know the port already, no need to search for it. Plus, it used 0-index ids not the 1-index ones matching physical labels on hubs, and other user-visible diagnostics. * For interfaces, it mixed the device address with the interface number ... producing unstable IDs that were moreover rather cryptic. Changed: "if0" now, using the interface ID (not index). * For busses, left "usb_bus" alone ... :) - Adds two files exposing current configuration (for devices) and altsetting (for interfaces). - I was getting a useless diagnostic from the hub driver, now it's less useless (it fully identifies the hub)
-
Linus Torvalds authored
-
Petr Vandrovec authored
drivers/ide/probe.c initializes gd->de_arr and gd->flags twice. Except that it is unnecessary it also leaks memory.
-
Mark Kettenis authored
Edition 4.1 of the System V Application Binary Interface says that "The first namesz bytes in name contains a null-terminated representation of the entry's owner or originator". This implies that the terminating null is included in namesz, which is corroborated by the example that follows the description. However, this is not what the Linux kernel does when it writes its notes into an ELF core dump. The attached patch fixes this.
-
Linus Torvalds authored
HACK ALERT! This needs to be fixed to do what reiserfs actually thinks it _should_ do.
-
Linus Torvalds authored
-
Orjan Friberg authored
In usb_bluetooth_probe, the transfer buffers for the write pool urbs are allocated with size 0, because bluetooth->bulk_out_buffer_size isn't set until after the loop.
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Moved the file ops and minor number stuff out of the usb structure, Now usb_register_dev() and usb_deregister_dev() must be called if you want to use the USB major number.
-
Greg Kroah-Hartman authored
into kroah.com:/home/linux/linux/BK/gregkh-2.5
-
Linus Torvalds authored
-
Paul Menage authored
This patch removes BKL protection from the invocation of the super_operations ->statfs() method, and shifts it into the filesystems where necessary. Any out-of-tree filesystems may need to take the BKL in their statfs() methods if they were relying on it for synchronisation. All ->statfs() implementations have been modified to take the BKL, except for those that don't reference any external mutable data or that already have their own locking. Additionally, capifs is changed to use simple_statfs rather than its own home-grown version. The BKL change has been flagged at the end of Documentation/filesystems/porting, along with the recent change to ->permission BKL usage.
-
http://linux-ntfs.bkbits.net/ntfs-tng-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://linux-input.bkbits.net/linux-inputLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Kai Germaschewski authored
into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make
-
- 04 Jul, 2002 6 commits
-
-
Petko Manolov authored
I chose a little bit more restrictive license for my drivers. Rx skb pool introduced in pegasus driver and the pool locking in rtl8150 is refined.
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Alexander Viro authored
* ->i_dev followed the example of ->s_dev - it's dev_t now. All remaining uses of ->i_dev either outright want dev_t (stat()) or couldn't care less (printing major:minor in /proc/<pid>/maps, etc.)
-
Alexander Viro authored
* JFS uses its ->logdev only twice - one of the places assigns it to_kdev_t(le32_to_cpu(...)), another uses kdev_t_to_nr() of it. Switched to u32 - it's just a place where we store device number we'd got from superblock. * several reiserfs_fs.h function prototypes removed - functions in question don't exist anymore. * smbfs doesn't support device nodes; ->f_rdev removed.
-
Alexander Viro authored
* svc_export ->ex_dev turned into dev_t. It's a pure search key and all places that set it actually do to_kdev_t(some_dev_t_expression).
-
Alexander Viro authored
* ->dev killed for md/linear.c (same as previous parts)
-