- 12 Nov, 2004 13 commits
-
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
Hanna Linder <hannal@us.ibm.com> Signed-off-by:
Greg Kroah-Hartman <greg@kroah.com>
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away soon I have converted this file to use pci_get_device instead. for_each_pci_dev is a macro wrapper around pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. for_each_pci_dev is a macro wrapper around pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I have replaced this call with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I have replaced this call with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
As pci_find_device is going away I've replaced it with pci_get_device. Signed-off-by:
-
Hanna V. Linder authored
Signed-off-by:
-
Hanna V. Linder authored
Signed-off-by:
-
Tim Hockin authored
On Thu, Nov 11, 2004 at 09:54:19AM -0800, Greg KH wrote: > I'll wait till you test this on 2.6 before applying it. OK. Tested now on real hardware in 32 bit and 64 bit kernels. 32 bit found another dumbness, that we can fix up. Some PCI bridges default their UPPER prefetch windows to an unused state of base > limit. We should not use those values if we find that. It might be nice to reprogram them to 0, in fact. Yes, BIOS should fix that up, but apparently, some do not. Signed-Off-By:
Tim Hockin <thockin@google.com> Signed-off-by:
-
- 11 Nov, 2004 27 commits
-
-
Jan Dittmer authored
This adds the ability to rescan the pci bus for newly inserted, reprogrammed or previously disabled pci devices. To initiate a rescan you need to write '1' to any of the /sys/bus/pci/slots/*/power control files. No known pci devices will be touched. Additionally this fixes a bug, when someone tries to disable a device with subfunctions. The subfunctions will be disabled first now. Short demo: # modprobe fakephp # ls /sys/bus/pci/slots | grep "0000:04" 0000:04:02.0 0000:04:02.1 0000:04:02.2 0000:04:03.0 0000:04:03.1 # echo -n 0 > /sys/bus/pci/slots/0000\:04\:02.0/power # ls /sys/bus/pci/slots | grep "0000:04" 0000:04:03.0 0000:04:03.1 # echo -n 1 > /sys/bus/pci/slots/0000\:03\:01.0/power # ls /sys/bus/pci/slots | grep "0000:04" 0000:04:02.0 0000:04:02.1 0000:04:02.2 0000:04:03.0 0000:04:03.1 # lspci | grep "0000:04" 0000:04:02.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) 0000:04:02.1 Input device controller: Creative Labs SB Audigy MIDI/Gameport (rev 03) 0000:04:02.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port 0000:04:03.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01) 0000:04:03.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01) Signed-off-by:
Jan Dittmer <jdittmer@ppp0.net> Signed-off-by:
-
Jan Dittmer authored
fakephp needs to add newly discovered devices to the global pci list. Therefore seperate out the appropriate chunk from pci_bus_add_devices to pci_bus_add_device to add a single device to sysfs, procfs and the global device list. Signed-off-by:
-
Greg Kroah-Hartman authored
-
Greg Kroah-Hartman authored
Signed-off-by: -
bk://gkernel.bkbits.net/net-drivers-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Andrew Morton authored
The patch below fixes a problem with shutting down 802.3ad bonds on the 2.6 kernel. Taking the interface down or removing the module causes a stack dump if spinlock debugging is enabled. This patch was generated from the 2.6.9 kernel. This patch has been peer reviewed by our Linux software engineering team, and the fix has been verified by our test labs. Signed-off-by:
Mitch Williams <mitch.a.williams@intel.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Jeff Garzik <jgarzik@pobox.com>
-
Andrew Morton authored
This patch undoes a change that we believe will impact performance adversely, by creating possibly too long a delay between servicing completions. The comment pretty much explains it. We need to call both cleanup routines each pass through the loop, this time we have a comment explaining why. Signed-off-by:
Jesse Brandeburg <jesse.brandeburg@intel.com> Signed-off-by:
-
Andrew Morton authored
Obviously pci_enable_device should be called after pci_restore_state. Signed-off-by:
Li Shaohua <shaohua.li@intel.com> Signed-off-by:
-
Andrew Morton authored
This fixes a bug where netpoll can dereference a null ifa_list pointer when not supplied an IP address at module load and the interface is up but no IP is configured. Bonus: unrelated netif_running cleanup Signed-off by: Jeff Moyer <jmoyer@redhat.com> Signed-off by: Matt Mackall <mpm@selenic.com> Signed-off-by:
-
Linus Torvalds authored
It seems to result in unexplained memory corruption. Matt is working on it. Cset exclude: Matt_Domsch@dell.com[torvalds]|ChangeSet|20041020153622|50713
-
Andrew Morton authored
Limit the number of legacy ptys to 256. pty_line_name() isn't capable of generating more than 256 unique names. Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Arjan van de Ven authored
task_nice() was exported for binfmt_elf, however that's no longer modular. normalize_rt_tasks() is used by the sysreq code only, which isn't modular. Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Signed-off-by:
-
Arjan van de Ven authored
- cdev_get is only used in fs/char_dev.c; move it up, make it static and unexport it. - cdev_put is used in one more place (fs/file_table.c) but never in modules; unexport it. Signed-off-by:
-
Domen Puncer authored
Code looks like it intended to parse "%%" in pattern string as "%". Fix it, so it really does that. Compile and run tested. Signed-off-by:
Domen Puncer <domen@coderock.org> Signed-off-by:
-
Randy Dunlap authored
Convert MODULE_PARM() to module_param(). Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Randy Dunlap authored
Convert MODULE_PARM() to module_param(). Signed-off-by:
-
James Nelson authored
Updates to Documentation/md.txt - included some extra info I found out while digging deeper into init/do_mounts_md.c Signed-off-by:
James Nelson <James4765@gmail.com> Signed-off-by:
-
Neil Brown authored
The 'faulty' personality provides a layer over any block device in which errors may be synthesised. A variety of errors are possible including transient and persistent read and write errors, and read errors that persist until the next write. There error mode can be changed on a live array. Accessing this personality requires mdadm 2.8.0 or later. Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
As the unplug timer can potentially fire at any time, and and it access data that is released by the md ->stop function, we need to del_timer_sync before releasing that data. (After much discussion, we created blk_sync_queue() for this) Signed-off-by:
-
Neil Brown authored
Sometimes it didn't read all (working) drives before a parity calculation. Signed-off-by:
-
Neil Brown authored
Some size fields were "int" instead of "sector_t". Signed-off-by:
-
Antonino Daplas authored
This patch fixes some of the drivers' fb_blank() implementation which got the usage of the VESA_* constants incorrectly and converts them to use the new FB_BLANK-* constants. I'm not sure if what I did is correct for all drivers, so maintainers, please review. (Note: For most of the drivers, FB_BLANK_NORMAL is treated as FB_BLANK_UNBLANK, but returns a nonzero so fbcon will do a soft_blank). Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
This patch converts most drivers to use the new FB_BLANK_* constants. These drivers have correct fb_blank() implementations. Signed-off-by:
-
Antonino Daplas authored
The VESA_* constants in fb.h used for power management of the display is confusing to use. The constants seems to be meant for userspace, because within the kernel (vt and fbdev), the constants have to be incremented by 1. Implementation of fb_blank() varies from driver to driver: - if-else on blank/!blank - switch case on hardcoded numbers - switch case on the constants + 1 - switch -1, case on constants as is - switch case on the constants as is (broken) To make usage clearer, new constants are defined in fb.h: FB_BLANK_UNBLANK = VESA_UNBLANKING = 0; FB_BLANK_NORMAL = VESA_UNBLANKING + 1 = 1; FB_BLANK_VSYNC_SUSPEND = VESA_VSYNC_SUSPEND + 1 = 2; FB_BLANK_HSYNC_SUSPEND = VESA_HSYNC_SUSPEND + 1 = 3; FB_BLANK_POWERDOWN = VESA_POWERDOWN + 1 = 4; Other changes: - generic blanking code in fbcon.c (for drivers without an fb_blank hook) which either sets the palette to all black, or clear the screen with black. - make fb_display an unexportable symbol Signed-off-by:
-
Antonino Daplas authored
The function set_con2fb_map() is getting very big. Split it into its component functions. Signed-off-by:
-
Antonino Daplas authored
Set color depth to 8 if in pseudocolor in vesafb. The CLUT size, previously saved as {red|green|blue}.length, is now private to vesafb. Signed-off-by: -
Antonino Daplas authored
The hardware cursor implementation in i810fb broke sometime during 2.6. Until this is fixed, temporarily use soft_cursor(). Signed-off-by:
-
