- 13 Aug, 2003 6 commits
-
-
Mark W. McClelland authored
This patch adds some read-only files to ov511's sysfs directory. The read/write attributes will be added in a future patch. For now, the read/write-related code is #if'd out to prevent warnings.
-
Mark W. McClelland authored
This patch converts ov511 to dynamically allocate struct video_device, using the new interfaces in videodev.[ch]. This is required to safely support sysfs without races.
-
Mark W. McClelland authored
This is the first in a series of three patches to convert the ov511 driver's /proc/video interface to sysfs. All V4L drivers must undergo this conversion now that /proc/video has been removed from the core. This patch removes ov511's /proc/video support, which allows it to compile again.
-
Greg Kroah-Hartman authored
Again, I messed up the usage, now we are safe from devices being removed. This fixes a number of error reports from users.
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
This fixes the kobject messages when disconnecting a usb serial device that people have been complaining about.
-
- 11 Aug, 2003 8 commits
-
-
David Brownell authored
Unfortunately, usb_set_configuration() is widely mis-used as a lightweight device reset. That's trouble because setting a configuration must sometimes involve things that don't relate at all to a light reset, and can't be done in contexts like driver probe() calls. This patch updates most usb_set_configuration() users to use a call that provides more appropriate functionality: - Adds a new usb_reset_configuration() call, which never needs to change very much usbcore state. - Uses it to replace most usb_set_configuration() calls, in many serial drivers, hisax, dvb, irda, and so on. - Modifies usb_reset_device() so it issues the control request directly. It's both more of a reset (hides a USB reset) and less of one (altsettings are unchanged). - Makes usbfs return the error code instead of discarding it. Once this goes in, then usb_set_configuration() can be made to work properly (including from sysfs).
-
David Brownell authored
This resolves the annoyance that dabusb claims devices it shouldn't (and hotplugs for them), because of wrongly including the device IDs used by an21xx devices that don't have an ID prom. Mostly affects developers. Deti OK'd such a patch ages ago.
-
Oliver Neukum authored
this can oops. - check for mem alloc failure
-
Oliver Neukum authored
- fail if second interface is already claimed
-
Oliver Neukum authored
- update commentary
-
Oliver Neukum authored
this function races with itself, doesn't return errors and races with releasing interfaces. This patch fixes it by changing the function prototype, introducing locking and having a correct order in releasing interfaces. - API change to check errors in usb_driver_claim_interface and fix a race condition between releasing and reclaiming an interface
-
Oliver Neukum authored
it seems that I've broken usblp. This reverts to the old behaviour. Please apply. - revert to old timeout handling
-
Oliver Neukum authored
- in interrupt usb_submit_urb must use GFP_ATOMIC
-
- 09 Aug, 2003 14 commits
-
-
Thomas Molina authored
The following patch has been floating around forever. It is required for several ARM framebuffer drivers, and several other drivers. James has indicated that this is the correct fix back in May.
-
Benjamin Herrenschmidt authored
This provides the necessary infrastructure for PowerMac specific drivers (and actually some Open Firmware platform drivers on non-PowerMacs as well provided somebody port them) to be properly probed & referenced via the new driver model and be part of sysfs. As-is, this patch doesn't break anything nor change any driver. I'll send you individual driver patches as I clean them up & get them tested on as many machines as possible, though I don't expect much problems.
-
Jeff Garzik authored
While reviewing my 2.4 backport of the 2.6 cpu capabilities (including the Via RNG support), Mikael Pettersson noticed a bug in both my backport, and 2.6: when NCAPINTS (x86_capability array size) is increased, one must adjust the offset in arch/i386/kernel/head.S also. Contributed by Mikael Pettersson.
-
Herbert Xu authored
This makes the HISAX ST5481 driver build again with 2.6.0-test3 where the usb_host_config structure has changed.
-
Wim Van Sebroeck authored
some small clean-ups: do correct errorhandling
-
Wim Van Sebroeck authored
added WDIOC_SETTIMEOUT and WDIOC_GETTIMEOUT ioctls made timeout (the emulated heartbeat) a module_param made the keepalive ping an internal subroutine
-
Wim Van Sebroeck authored
add CONFIG_WATCHDOG_NOWAYOUT support changed watchdog_info to correctly reflect what the driver offers added WDIOC_GETSTATUS, WDIOC_GETBOOTSTATUS and WDIOC_SETOPTIONS ioctls use module_param
-
Wim Van Sebroeck authored
cleanup comments and trailing spaces eliminate extra spin_unlock add KERN_* tags to printks added extra printk's to report what problem occured
-
Wim Van Sebroeck authored
some small clean-ups (use PFX + report default timeout as it's value in the MODULE_PARM_DESC)
-
Wim Van Sebroeck authored
some last clean-ups
-
Wim Van Sebroeck authored
added extra printk's to report what problem occured
-
Wim Van Sebroeck authored
make wdt_stop and wdt_start module params
-
Wim Van Sebroeck authored
report default timeout as a number
-
Wim Van Sebroeck authored
general cleanup of trailing spaces and comments fix possible wdt_is_open race add KERN_* to printk's changed watchdog_info to correctly reflect what the driver offers added WDIOC_GETSTATUS, WDIOC_GETBOOTSTATUS, WDIOC_SETTIMEOUT, WDIOC_GETTIMEOUT, and WDIOC_SETOPTIONS ioctls made timeout (the emulated heartbeat) a module_param made the keepalive ping an internal subroutine added MODULE_AUTHOR and MODULE_DESCRIPTION info
-
- 08 Aug, 2003 12 commits
-
-
Linus Torvalds authored
-
Jeff Garzik authored
Contributed by VIA, via Jean Tourrilhes.
-
Jean Tourrilhes authored
ir260_tekram-sir.diff : ~~~~~~~~~~~~~~~~~~~~~ <Patch from Martin Diehl> o [CORRECT] Update tekram-sir dongle driver to common power-settling
-
Jean Tourrilhes authored
ir260_usb_probe-4.diff : ~~~~~~~~~~~~~~~~~~~~~~ <Patch from Oliver Neukum and Daniele Bellucci> o [CORRECT] minor fix to the probe failure path of irda-usb.
-
Jean Tourrilhes authored
ir260_lap_retry_count.diff : ~~~~~~~~~~~~~~~~~~~~~~~~~~ o [CORRECT] add interoperability workaround for 2.4.X IrDA stacks
-
Jean Tourrilhes authored
ir260_donau_cleanup.diff : ~~~~~~~~~~~~~~~~~~~~~~~~ <Patch from Christian Gennerat> o [CORRECT] Disable chip probing that fail too often o [FEATURE] Cleanup STATIC
-
bk://kernel.bkbits.net/gregkh/linux/linus-2.6Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
bk://kernel.bkbits.net/gregkh/linux/i2c-2.5Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/pci-2.6
-
Ivan Kokshaysky authored
Bug #1 (found by Jay Estabrook). On Alpha, under certain circumstances the firmware may close the IO window of PCI-to-PCI bridge even if there is IO behind. This wouldn't be a problem - linux PCI setup code does set up this window properly, but in addition the firmware clears the IO-enable bit in the PCI_COMMAND register of the bridge. Since we don't call pci_enable_* routines for bridges in non-hotplug path, we end up with disabled IO. Fixed by adding pci_enable_bridges() to pci_assign_unassigned_resources(). Architectures which don't use the latter, but do use other setup-bus code (parisc?) also should call pci_enable_bridges() for each root bus. Bug #2 (closely related to #1). As it turns out, pci_enable_device() doesn't work for bridges at all, only for regular devices (header type 0) due to 0x3f mask passed to pci_enable_device_bars(). The mask should be (1 << PCI_NUM_RESOURCES) - 1. Bug #3 (quite a few archs, including i386). pcibios_enable_device() does only check first 6 resources (regardless of the mask) to decide whether or not to enable IO and MEM. Bridge resources start at 7. #2 and #3 affect hotplug. I wonder, has anybody ever tried *bridged* PCI card behind a hot-plug controller?
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/gregkh-2.6
-
Sean Estabrooks authored
This patch adds another P4B motherboard subsystem identifier to the recent asus sensor patch for the 2.6 kernel.
-