- 27 Dec, 2002 21 commits
-
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
This was done to make the next reference count patch easier, and because almost everyone was already calling usb_put_dev() anyway...
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
change dev_set_drvdata() and dev_get_drvdata() to usb_set_intfdata() and usb_get_intfdata()
-
Greg Kroah-Hartman authored
into kroah.com:/home/linux/linux/BK/gregkh-2.5
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Also added usb_get_intfdata() and usb_set_intfdata() functions to set the struct usb_interface private pointer easier.
-
Pablo Menichini authored
This patch tries to check the return value of kmalloc taking the necesary action to solve the problem.
-
dmitri@users.sourceforge.net authored
> > Ultracam was derived from ibmcam and probably copied the list of > > parameters too. IBM cameras have this parameter, and use it. > > This means that it says "MODULE_PARM(lighting, "i");" and there is no > variable called lightening. The new module code is stricter about > this. Someone please fix. Here is the patch for 2.5.53. It removes parameters that have no use in the ultracam driver (and they were broken anyway).
-
David Brownell authored
Attached is a patch leveraging some of the new generic dma stuff: - Replaces dma mapping calls in usbcore with generic equivalents. This is a minor code shrink (which we'd hoped could happen). - Pass dma mask along, so net drivers can notice it'd be good to set NETIF_F_HIGHDMA; or scsi ones can set highmem_io. (Some Intel EHCI setups are able to support this kind of DMA.) - Updates one net driver (usbnet) to set NETIF_F_HIGHDMA when appropriate, mostly as an example (since I can't test this). - Provides Documentation/usb/dma.txt, describing current APIs. (Unchanged by this patch, except dma mask visibility.) - Converted another info() to dev_info(), and likewise a couple dbg() to dev_dbg() conversions in the modified routine. The number of FIXMEs was conserved: the generic API doesn't yet fix the error reporting bugs in the PCI-specific mapping API.
-
- 26 Dec, 2002 15 commits
-
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
This is to access the private pointer in struct usb_serial
-
Greg Kroah-Hartman authored
[PATCH] USB: fix up the usb-serial drivers due to the removal of the struct usb_serial_port private pointer.
-
Greg Kroah-Hartman authored
The struct device pointer should be used instead.
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
-
Pavel Machek authored
-
Linus Torvalds authored
as "offsetof pp->entries". Which happens to be true on 32-bit platforms, but not on 64-bit ones. From Anton Blanchard.
-
- 24 Dec, 2002 4 commits
-
-
Ingo Molnar authored
In vm86 mode we did not save/restore %gs [and %fs] properly, which breaks new-style threading.
-
Linus Torvalds authored
on x86 - the kernel doesn't really care (as long as it's all flat 32-bit), and it means that the return path for sysenter/sysexit can avoid re-loading the segment registers. NOTE! This means that _all_ kernel code (not just the sysenter path) must be appropriately changed, since the kernel knows the conventions and doesn't save/restore DS/ES internally on context switches etc.
-
Linus Torvalds authored
-
Ganesh Varadarajan authored
The ActiveSync USB "protocol" seems to be the same for all WinCE devices seen so far. So it seems reasonable to pre-emptively support all devices which work with ActiveSync.
-