- 12 Sep, 2005 40 commits
-
-
Ian Abbott authored
ftdi_sio: I messed up the baud_base for custom baud rate support in 2.6.13. The attached one-liner patch fixes it. Signed-off-by:
Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Pete Zaitcev authored
Alan Stern sent me this patch. It goes on top of the patch the adds mon_dmapeek: http://ftp.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb/usb-usbmon-dma-areas.patch Please be warned about ordering requirements or the build may fail. Actually, mon_dmapeek is generic enough to support SETUP packets too. Signed-off-by:
Pete Zaitcev <zaitcev@redhat.com> Signed-off-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
-
Thomas Sailer authored
This patch fixes the long standing schedule with interrupts off problem of the uss720 driver. The problem is caused by the parport layer calling the save and restore methods within a write_lock_irqsave guarded region. The fix is to issue the control transaction requests required by save and restore asynchronously. Signed-off-by:
Thomas Sailer, <sailer@ife.ee.ethz.ch> Signed-off-by:
-
Harald Welte authored
[USBDEVFS] fix inclusion of <linux/compat.h> to avoud header mess Without moving the include of compat.h down, userspace programs that use usbdevice_fs.h end up including half the kernel includes (and eventually fail to compile). Signed-off-by:
Harald Welte <laforge@netfilter.org> Signed-off-by:
-
Daniel Drake authored
Alan Stern wrote: > If the device sometimes reports the correct values, then you should > include NEED_OVERRIDE flag to prevent messages about unnecessary > overrides showing up in the system log. Also, if bInterfaceSubclass > is correct and only bInterfaceProtocol is wrong, then the entry should > say US_SC_DEVICE instead of US_SC_SCSI. Fair points, thanks. When connected over USB2, this device reports a nonsense bInterfaceProtocol value 6 and doesn't work with usb-storage. When connected over USB1, the device reports the correct bInterfaceProtocol value 0x50 (bulk) and works with no problems. Signed-off-by:
Daniel Drake <dsd@gentoo.org> Signed-off-by:
Phil Dibowitz <phil@ipom.com> Signed-off-by:
-
Phil Dibowitz authored
This patch adds entries for several USB floppies that need the US_FL_SINGLE_LUN flag. These were reported by Sebastian Kapfer <sebastian_kapfer@gmx.net> and Olaf Hering <olh@suse.de>, with rediffing and cleaning from me. Reported-by:
Sebastian Kapfer <sebastian_kapfer@gmx.net> Reported-by:
Olaf Hering <olh@suse.de> Signed-off-by:
-
Pete Zaitcev authored
The stick replies to the door lock commands with a check condition (e.g. FAIL status in a normal bulk CSW), but the subsequent REQUEST SENSE returns all-zero sense. The situation is documented in our Bugzilla, including usbmon traces. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=162559 The error is purely cosmetic, data integrity is not in danger. But I thought we might as well do it. It looks nicer that way. I discussed this with Phil and he told me to submit directly. Signed-off-by:
-
Matthew Dharm authored
This is patch as550 from Alan Stern. Apparently someone changed the SCSI core so that it no longer holds the host lock when doing a device or bus reset. usb-storage was updated at the time, but the change was done carelessly. Some of the code depends on that lock being held. This patch reintroduces the host lock where needed and tries to clarify the comments explaining why the lock is necessary. It also moves the code that clears the TIMED_OUT and ABORTING bitflags so that it executes as soon as the timed-out command has completed (and while the host lock is held). Signed-off-by:
Matthew Dharm <mdharm-usb@one-eyed-alien.net> Signed-off-by:
-
David Brownell authored
This appears to help some folk, please merge. This patch relaxes reset timings. There are some reports that it helps make enumeration work better on some high speed devices. Signed-off-by:
David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
-
Randy Dunlap authored
Update Documentation/usb/proc_usb_info.txt: - remove some trailing whitespace - add a blank line before each T: line to match current kernel and to make the text more readable. Signed-off-by:
Randy Dunlap <rdunlap@xenotime.net> Signed-off-by:
-
Robert Spanton authored
This patch adds the product ID and vendor ID for a Nokia CA-42 USB cable to the list of devices handled by the pl2303 driver. The patch is against 2.6.13. Signed-off-by:
Robert Spanton <rds204@zepler.net> Signed-off-by:
-
David Brownell authored
Now that it's in use on other boards, a bug in the original code needs fixing. There is no need for the PXA27x OHCI to set usb power during init, since the hub driver in usbcore handles that. Those platform-specific power control functions are also incorrect, and should therefore be removed. Add a check to clear the OTG pin hold bit until such times OTG is properly implemented. Signed-Off-By:
Richard Purdie <rpurdie@rpsys.net> Signed-off-by:
-
David Brownell authored
Some OHCI implementations have differences in the way the NDP register (in roothub_a) reports the number of ports present. This patch allows the platform specific code to optionally supply the number of ports. The driver just reads the value at init (if not supplied) instead of reading it every time its needed (except for an AMD756 bug workaround). It also sets the value correctly for the ARM pxa27x architecture. Signed-Off-By:
-
David Brownell authored
Evidently there are some boards which care a lot about this, but as a rule it's been hard to notice. OHCI_INTR_RD wasn't always cleared in the ohci irq handler. On some systems this means certain remote wakeup scenarios could seem to hang (in an interrupt storm, RD never clearing). From: "William Morrow" <William.Morrow@amd.com> Signed-off-by:
Jordan Crouse <jordan.crouse@amd.com> Signed-off-by:
-
Pavol Kurina authored
this patch fixes an "Invalid argument" error returned by a write to an endpoint-file after reopening it in the gadgetfs module in the kernel 2.6.12. This was testet only with dummy_hcd module! Signed-off-by:
Pavol Kurina <kurina@gmx.net> Signed-off-by:
-
Nishanth Aravamudan authored
Description: Use schedule_timeout_{,un}interruptible() instead of set_current_state()/schedule_timeout() to reduce kernel size. Signed-off-by:Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by:
-
David Brownell authored
Routine cases like handoff-to-companion shouldn't trigger diagnostics. This gets rid of some recently added log spamming. It's routine for hub_port_wait_reset() to return -ENOTCONN to indicate handoff from highspeed hubs to companions, so an error message is incorrect. Signed-off-by:
-
David Brownell authored
NVidia reports (via Mark Overby) that some of their EHCI controllers don't like certain data structure addresses beyond the 2GB mark. He provided an earlier version of this patch. Signed-off-by:
-
David Brownell authored
One change may improve some S1 or S3 resume cases, and the other seems mostly to explain some strange state "lsusb" would show. Two fixes: - On resume, don't think about resuming any unpowered port, or resetting any port with OWNER set to the OHCI/UHCI companion. This will make some S1 and S3 resume scenarios work better. - PORT_CSC was not being cleared correctly in ehci_hub_status_data. This was visible at least through current versions of "lsusb", and might have caused some other hub related strangeness. The fix addresses all three write-to-clear bits, using the same approach that UHCI happens to use: a mask of bits that are cleared in most writes to that port status register. Original patch seems to have been from from William.Morrow@amd.com and this version (from David) finishes the write-to-clear changes. Signed-off-by: -
Craig Shelley authored
Three new device IDs for CP2101 USB to UART Bridge Signed-off-by:
Craig Shelley <craig@microtron.org.uk> Signed-off-by:
-
Alan Stern authored
This patch (as558) removes from the UHCI driver a kernel timer used for checking Full Speed Bandwidth Reclamation (FSBR). The checking can be done during normal root-hub polling; it doesn't need a separate timer. Signed-off-by:
-
Alan Stern authored
This patch (as549) introduces two small changes in the HCD glue layer. The first simply removes a redundant test. The second allows root-hub polling to continue for a single iteration after a host controller dies; this is needed for the patch that follows. Signed-off-by:
-
Stelian Pop authored
This is a driver for the USB touchpad which can be found on post-February 2005 Apple PowerBooks. This driver is derived from Johannes Berg's appletrackpad driver [1], but it has been improved in some areas: * appletouch is a full kernel driver, no userspace program is necessary * appletouch can be interfaced with the synaptics X11 driver[2], in order to have touchpad acceleration, scrolling, two/three finger tap, etc. This driver has been tested by the readers of the 'debian-powerpc' mailing list for a few weeks now and I believe it is now ready for inclusion into the mainline kernel. Credits go to Johannes Berg for reverse-engineering the touchpad protocol, Frank Arnold for further improvements, and Alex Harper for some additional information about the inner workings of the touchpad sensors. Signed-off-by:Stelian Pop <stelian@popies.net> Signed-off-by:
-
Thomas Winischhofer authored
here is a new and extended version of the sisusbvga (previously: sisusb) driver. The patch is against 2.6.13 and updates the driver to version 0.0.8. Additions include complete VGA/EGA text console support and a build-in display mode infrastructure for userland applications that don't know about the graphics internals. Fixes include some BE/LE issues and a get/put_dev bug in the previous version. Other changes include a change of the module name from "sisusb" to "sisusbvga". The previous one was too generic IMHO. Please note that the patch also affects the Makefile in drivers/video/console as the driver requires the VGA 8x16 font in case the text console part is selected. Heavily tested, as usual. Please apply. One thing though: I already prepared for removal of the "mode" field and the changed "name" field in the usb_class_driver structure. This will perhaps need some refinement depending on whether you/Linus merge the respective core changes before or after 2.6.14. Signed-off-by:
Thomas Winischhofer <thomas@winischhofer.net> Signed-off-by:
-
Greg KH authored
This reverts 22af8878 commit. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
The nodes are not set online yet at this point. Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Andi Kleen authored
Signed-off-by: -
Andi Kleen authored
Also use for_each_node_mask instead of hand crafted loops. Signed-off-by: -
Chuck Ebbert authored
Original patch from Bertro Simul This is probably still not quite correct, but seems to be the best solution so far. Signed-off-by: -
Jan Beulich authored
As mentioned before, the size of the bug frame can be further reduced while continuing to use instructions to encode the information. Signed-off-by:
Jan Beulich <jbeulich@novell.com> Signed-off-by:
-
Andi Kleen authored
Otherwise it will generate warnings and be generated many times. Signed-off-by:
-
Andi Kleen authored
Allow frame pointer and fix help text. Signed-off-by:
-
Al Viro authored
... and with that all instances in arch/x86_64 are gone. Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
-
Chuck Ebbert authored
This is the same patch that went into i386 just before 2.6.13 came out. I still can't build 64-bit user apps, so I tested with program (see below) in 32-bit mode on 64-bit kernel: Before: $ fpsig handler: nr = 8, si = 0x0804bc90, vuc = 0x0804bd10 handler: altstack is at 0x0804b000, ebp = 0x0804bc7c handler: si_signo = 8, si_errno = 0, si_code = 0 [unknown] handler: fpu cwd = 0xb40, fpu swd = 0xbaa0 handler: i387 unmasked precision exception, rounded up After: $ fpsig handler: nr = 8, si = 0x0804bc90, vuc = 0x0804bd10 handler: altstack is at 0x0804b000, ebp = 0x0804bc7c handler: si_signo = 8, si_errno = 0, si_code = 6 [inexact result] handler: fpu cwd = 0xb40, fpu swd = 0xbaa0 handler: i387 unmasked precision exception, rounded up Signed-off-by:
Chuck Ebbert <76306.1226@compuserve.com> Signed-off-by:
-
Chuck Ebbert authored
The x86_64 nmi code is missing a newline in one of its messages. I added a space before the CPU id for readability and killed the trailing space on the previous line as well. Signed-off-by:
-
Jan Beulich authored
While only cosmetic for x86-64, this adjusts the cmpxchg code appearantly inherited from i386 to use more generic constraints. Signed-off-by:
-
Jan Beulich authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
