29 Oct, 2005
40 commits
-
Freecom seems to be one of those vendors that can't get the GET CAPACITY
thing right. This expands the US_FL_FIX_CAPACITY flag for the entire
range of their fccd product line.This is based on a patch sent by Stuart Black
.Signed-off-by: Phil Dibowitz
Signed-off-by: Greg Kroah-Hartman -
Signed-off-by: Alexey Dobriyan
Signed-off-by: Greg Kroah-Hartman -
This patch is originally from Alan Stern (as569). It has been rediffed
against a current tree.This patch converts usb-storage to use the kthread API for creating its
control and scanning threads. The new code doesn't use kthread_stop
because the threads need (or will need in the future) to exit
asynchronously.Signed-off-by: Alan Stern
Signed-off-by: Matthew Dharm
Signed-off-by: Greg Kroah-Hartman -
This patch from Alan Stern started as as568. It has been rediffed against
a current tree.This patch adds minimal suspend/resume support to usb-storage. Just enough
for it to qualify as PM-aware.Signed-off-by: Alan Stern
Signed-off-by: Matthew Dharm
Signed-off-by: Greg Kroah-Hartman -
This patch is from Alan Stern (as560). It has been rediffed against a
current tree.This patch allocates a separate buffer for usb-storage to use when
auto-sensing. Up to now we have been using the sense buffer embedded in a
scsi_cmnd struct, which is dangerous on hosts that (a) don't do
cache-coherent DMA or (b) have DMA alignment restrictions.Signed-off-by: Alan Stern
Signed-off-by: Matthew Dharm
Signed-off-by: Greg Kroah-Hartman -
This patch is originally from Alan Stern (as557). It has been re-diffed
against a current tree, and I also corrected a minor merging error.Some time ago we introduced a delay before device scanning, because many
devices do not like to receive SCSI commands right after enumeration.
Now it turns out there's a device that doesn't like to receive
Get-Max-LUN right after enumeration either. Accordingly this patch
delays the Get-Max-LUN request until the beginning of the scanning
procedure. This fixes Bugzilla entry #5010.Three things are worth noting. First, I removed the locking code from
usb_stor_acquire_resources. It's not needed, because the locking is to
protect against disconnect events and acquire_resources is only called
during probe (so the disconnect routine can't be called). Second, I
initialized to 0 the buffer used for the Get-Max-LUN response. It's not
really necessary, but it will prevent random values from showing up in
the debugging log when the request fails. Third, I added a test against
the SINGLE_LUN flag. This will allow us to use the flag to indicate
Bulk-only devices that can't handle Get-Max-LUN.Signed-off-by: Alan Stern
Signed-off-by: Matthew Dharm
Signed-off-by: Greg Kroah-Hartman -
This patch (as577) adds a Clear-Halt call on the Interrupt-in endpoint
during input device configuration. Without it my HP USB keyboard doesn't
work.Vojtech says it's worth trying, since it might help with some recalcitrant
devices. On the other hand, it might interfere with others. I'm
submitting it so that it can get tested by a range of users.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
This revised patch (as586b) makes usb-handoff permanently true and no
longer a kernel boot parameter. It also removes the piix3_usb quirk code;
that was nothing more than an early version of the USB handoff code
(written at a time when Intel's PIIX3 was about the only motherboard with
USB support). And it adds identifiers for the three PCI USB controller
classes to pci_ids.h.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
another one to use kzalloc. Please apply.
Signed-off-by: Oliver Neukum
Signed-off-by: Greg Kroah-Hartman -
This is a patch improving the set of vendor/product IDs used in the
"ipaq" USB serial device driver. The patch size is because I sorted the
ids this time, forgot about that last time.Changes:
- Added vendor/product identifiers for Psion Teklogix devices
- Restored Microsoft's identifier pair 045e/00ce
- Sorted list of vendor/product identifiersSigned-off-by: David Eriksson
Signed-off-by: Ganesh Varadarajan
Signed-off-by: Greg Kroah-Hartman -
On some arch (like arm) udelay cannot be called with value greater that
2000.Signed-off-by: Guillaume GOURAT / guillaume.gourat@nexvision.fr
Signed-off-by: Oliver Neukum -
here is another one to use kzalloc. Please apply.
Signed-off-by: Oliver Neukum
Signed-off-by: Greg Kroah-Hartman -
On Tue, 18 Oct 2005, Simeon Simeonov wrote:
> Attached is a patch that solves mounting problems for
> LEICA D-LUX camera with FC4 2.6.13 kernel.
>
> Let me know if you have some questions.Looks okay to me. Given that the previous entry uses the full 0000 -
9999 range, I guess this one can also. The vendor name is a little odd
(it will give us three different vendor names all in entries with the
same vendor ID) but that doesn't really matter either.Signed-off-by: Alan Stern
Signed-off-by: Phil Dibowitz
Signed-off-by: Greg Kroah-Hartman -
This fixes a problem with some cdc acm devices that were not getting
automatically loaded as the module alias was not being reported
properly.This check was for back in the days when we only reported hotplug events
for the main usb device, not the interfaces. We should always give the
interface information for MODALIAS/modalias as it can be needed.Signed-off-by: Greg Kroah-Hartman
-
These numbers are pointless, as they have not been changed in _years_,
so we should just remove them to stop pretending there is an actual
"version number" for these drivers.This should also help reduce confusion when people try to ask for
support of a specific driver version, as there has been no way to tell
what they are talking about.Signed-off-by: Greg Kroah-Hartman
-
This fixes up a lot of problems in sysfs with some of the usb serial
drivers, they had incorrect driver names. Also saves a tiny ammount
of memory.Signed-off-by: Greg Kroah-Hartman
-
Create a new file just for these things, as they just get in the
way in the source files.Signed-off-by: Greg Kroah-Hartman
-
Don't duplicate something that's already in struct driver.
Signed-off-by: Greg Kroah-Hartman
-
I'm tired of trying to explain why a "device_type" is really a driver.
This better describes exactly what this structure is.Signed-off-by: Greg Kroah-Hartman
-
We have a real Bluetooth system in Linux, lets finally delete this driver as no
one is using it (and if they are, they are using a closed source bluetooth
stack, which I can't support anyway.)Marcel, you owe me a beer :)
Signed-off-by: Greg Kroah-Hartman
-
Dell supplied me with the following test:
#include
#include
#include
#include
#includemain(int argc,char*argv[])
{
struct usbdevfs_hub_portinfo hubPortInfo = {0};
struct usbdevfs_ioctl command = {0};
command.ifno = 0;
command.ioctl_code = USBDEVFS_HUB_PORTINFO;
command.data = (void*)&hubPortInfo;
int fd, ret;
if(argc != 2) {
fprintf(stderr,"Usage: %s /proc/bus/usb//\n",argv[0]);
fprintf(stderr,"Example: %s /proc/bus/usb/001/001\n",argv[0]);
exit(1);
}
errno = 0;
fd = open(argv[1],O_RDWR);
if(fd < 0) {
perror("open failed:");
exit(errno);
}
errno = 0;
ret = ioctl(fd,USBDEVFS_IOCTL,&command);
printf("IOCTL return status:%d\n",ret);
if(ret
Signed-off-by: Greg Kroah-Hartman -
This also removes 2 usbmon callbacks.
Signed-off-by: Greg Kroah-Hartman
-
Signed-off-by: Greg Kroah-Hartman
-
Signed-off-by: Greg Kroah-Hartman
-
This should let us get rid of all of the different hooks in the USB core for
when something has changed.Also, some other parts of the kernel have wanted to know this kind of
information at times.Signed-off-by: Greg Kroah-Hartman
-
It's only used locally.
Signed-off-by: Greg Kroah-Hartman
-
This patch (as582) adds a missing transfer_flags setting to the usbtest
driver.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
Add .owner initialisation to the device drivers
in drivers/usb/host so that when built as module
the device_driver refers to the owning moduleSigned-off-by: Ben Dooks
Signed-off-by: Greg Kroah-Hartman -
Ensure the the device_driver and usb_gadget_driver
have their .owner fields initialised to associate
the module owner to the driver.Signed-off-by: Ben Dooks
Signed-off-by: Greg Kroah-Hartman -
Initialise the .owner field of the driver with
the module that owns it, to aid in linking
drivers to modules.Signed-off-by: Ben Dooks
Signed-off-by: Greg Kroah-Hartman -
When a USB device is put into suspend mode, the current drawn from VBUS
has to be less than 500 uA. Some transceivers need to be put into a
special power-saving mode to accomplish this, and won't have a separate
OTG driver handling that.This adds a suspend method to the "otg_transceiver" struct -- misnamed,
it's not only for OTG -- and calls it from the OMAP UDC driver.Signed-off-by: Juha Yrj?l?
Signed-off-by: David Brownell
Signed-off-by: Greg Kroah-Hartman -
This patch (as581) changes the assignments to hcd->state in the uhci-hcd
driver. It fixes part of bugzilla entry #5227. The problem was revealed
by David's large suite of USB suspend/resume patches; this patch should go
to Linus at the same time those do.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
The change to make DMA work two bytes at a time omitted an important
tweak that affects the file_storage gadget: it needs to recognize when
the host writes an odd number of bytes. (The network layer ignores
such extra bytes.)This patch resolves that issue by checking the relevant bit and adjusting
the rx byte count, so that for example a legal 13 byte request doesn't
morph into an illegal 14 byte one any more.Signed-off-by: David Brownell
Signed-off-by: Greg Kroah-Hartman -
usb/core/buffer.c doesn't export any symbols, so it should use
!I instead of !E to eliminate this warning message:Warning(/var/linsrc/linux-2614-rc4//drivers/usb/core/buffer.c): no structured comments found
Signed-off-by: Randy Dunlap
Signed-off-by: Greg Kroah-Hartman -
Just a small patch that fixes a small parameter validation bug.
drivers/usb/input/map_to_7segment.h:
This patch fixes the broken parameter validation in the char to seg7
conversion. This could cause out-of-bounds memory references.MAINTAINERS:
Yealink maintainer info now in sorted order.Documentation/input/yealink.txt:
Added a Q&A section that answers some common questions.Signed-off-by: Henk
Signed-off-by: Greg Kroah-Hartman006491df1a13f85ad245d1039dfdf20e49c394fd
-
The uhci-hcd driver is fairly lax about the way it handles isochronous
transfers. This patch (as579) improves it in three respects:TDs for a new URB aren't added to the schedule until all of
them have been allocated. This way there's no risk of the
controller executing some of them when an allocation fails.TDs for an unlinked URB are removed from the schedule as soon
as the URB is unlinked, rather than waiting until the URB is
given back. This way there's no risk of the controller still
executing a TD after the URB completes.The urb->error_count values are now reported correctly.
Although since they aren't used in any drivers except for
debug messages in the system log, probably nobody cares.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
This patch (as580) is perhaps the only result from the long discussion I
had with David about his changes to the root-hub suspend/resume code. It
renames the hub_suspend and hub_resume methods in struct usb_hcd to
bus_suspend and bus_resume. These are more descriptive names, since the
methods really do suspend or resume an entire USB bus, and less likely to
be confused with the hub_suspend and hub_resume routines in hub.c.It also takes David's advice about removing the layer of bus glue, where
those methods are called. And it implements a related change that David
made to the other HCDs but forgot to put into dummy_hcd.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
This patch (as574) updates the PCI BIOS usb-handoff code for UHCI
controllers, making it work like the reset routines in uhci-hcd. This
allows uhci-hcd to drop its own routines in favor of the new ones
(code-sharing).Once the patch is merged we can turn the usb-handoff option on
permanently, as far as UHCI is concerned. OHCI and EHCI may still have
some issues.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
This patch (as575) fixes an unlikely race in the g_file_storage driver.
The problem can occur only when the driver is unbound before its
initialization routine has finished.I also took the opportunity to replace kmalloc/memset with kzalloc.
Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
add two more device IDs from eGalax' programming guide.
thanks to Jonathan Hopper for pointing out.Signed-off-by: Daniel Ritz
Signed-off-by: Greg Kroah-Hartmandrivers/usb/input/touchkitusb.c | 2 ++
1 file changed, 2 insertions(+)
