- 10 Mar, 2005 6 commits
-
-
Matthew Wilcox authored
Use nonatomic bitops for ext2/3 where possible. Signed-off-by:
Matthew Wilcox <willy@parisc-linux.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Matthew Wilcox authored
Add definition of SHRREG Signed-off-by:
Randolph Chung <tausq@parisc-linux.org> Signed-off-by:
-
Matthew Wilcox authored
- Update stale url to documentation From: Kyle McMartin <kyle@parisc-linux.org> - Make unwinding from modules work, mostly - Fix unwinding from millicode Signed-off-by:
Randolph Chung <tausq@debian.org> Signed-off-by:
-
bk://kernel.bkbits.net/vojtech/for-linusLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Vojtech Pavlik authored
-
bk://drm.bkbits.net/drm-linusLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
- 11 Mar, 2005 9 commits
-
-
Dave Airlie authored
Egbert Eich reported a bug 2673 on bugs.freedesktop.org and tracked it down to a missing memset in the setversion ioctl, this causes X server crashes so I would like to see the fix in a 2.6.11.x tree if possible.. From: Egbert Eich <eich@pdx.freedesktop.org> Signed-off-by:Dave Airlie <airlied@linux.ie>
-
Dave Airlie authored
into starflyer.(none):/foo/airlied/bitkeeper/drm-linus
-
Dave Airlie authored
into starflyer.(none):/foo/airlied/bitkeeper/drm-linus
-
Dave Airlie authored
into starflyer.(none):/foo/airlied/bitkeeper/drm-linus
-
Dave Airlie authored
add support for texture micro tiling on radeon/r200. Add support for r100 cube maps (since it also requires a version bump). From: Roland Scheidegger <rscheidegger_lists@hispeed.ch> Signed-off-by: -
Dave Airlie authored
Cleanup patch for i810/i830 From: Adrian Bunk <bunk@stusta.de> Signed-off-by: -
Dave Airlie authored
This makes a lot of functions static and cleans up a few other minor things. From: Adrian Bunk <bunk@stusta.de> Signed-off-by: -
Dave Airlie authored
fd.o bug #2576: Add support for ATI RN50/ES1000. (ATI Technologies Inc.) From: Michel Daenzer <michel@daenzer.net> Signed-off-by: -
Dave Airlie authored
This patch splits out the main drm structures for future multi-head support. It just sets up the structures and the stub functions for putting/getting heads From: Jon Smirl <jonsmirl@gmail.com> Signed-off-by:
-
- 10 Mar, 2005 25 commits
-
-
Dave Airlie authored
Add myself to MAINTAINERS for drm, and fixup my CREDITS. Signed-off-by: -
Benjamin Herrenschmidt authored
This patch fixes a bug in ppc64 local implementation of iounmap() that would cause it to incorrectly flush the hash table since the changes to set_pte have been applied. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Linus Torvalds authored
-
Linus Torvalds authored
There seems little point in doing otherwise.
-
-
Bartlomiej Zolnierkiewicz authored
* move default_do_request() to ide-default.c * fix drivers to set ide_driver_t->{do_request,end_request,error,abort} * kill setup_driver_defaults() Signed-off-by:Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
* add private /proc/ide/hd?/capacity handlers to ide-{cd,disk,floppy}.c * use generic proc_ide_read_capacity() for ide-{scsi,tape}.c * kill ->capacity, default_capacity() and generic_subdriver_entries[] Signed-off-by: -
Bartlomiej Zolnierkiewicz authored
Add ide_drive_t->post_reset flag and use it to signal post reset condition to the ide-tape driver (the only user of ->pre_reset). Signed-off-by: -
Bartlomiej Zolnierkiewicz authored
Some rare races between ide-default and ide-disk are possible, i.e.: * ide-default is used, I/O request is triggered (ie. /proc/ide/hd?/identify), drive->special is cleared silently (so CHS is not initialized properly), ide-disk is loaded and fails if drive uses CHS * ide-disk is used, drive is resetted, ide-disk is unloaded, ide-default takes control over drive and on the first I/O request silently clears drive->special without restoring settings Fix them by moving idedisk_{special,pre_reset}() and company to IDE core. Signed-off-by: -
Bartlomiej Zolnierkiewicz authored
Move PM code from ide-cd.c and ide-disk.c to IDE core so: * PM is supported for other ATAPI devices (floppy, tape) * PM is supported even if specific driver is not loaded Also s/HWIF(drive)/drive->hwif/ while at it. Signed-off-by: -
Bartlomiej Zolnierkiewicz authored
ATAPI devices ignore DRDY bit so drive->ready_stat must be set to zero. It is currently done by device drivers (including ide-default fake driver) but for PMAC driver it is too late as wait_for_ready() may be called during probe: probe_hwif()->pmac_ide_dma_check()->pmac_ide_{mdma,udma}_enable()-> ->pmac_ide_do_setfeature()->wait_for_ready(). Fixup drive->ready_stat just after detecting ATAPI device. Signed-off-by: -
bram.verweij@wanadoo.nl authored
From: Bram Verweij <bram.verweij@wanadoo.nl> The problem seems to be that ide-disk.c tries to use PIO mode for blocks > 137 GB (which is good), and LBA48 + DMA for blocks <= 137GB (which is known to be a problem, i.e., this is why the no_lba48_dma field was introduced in the first place). Attached is a small patch that makes ide-disk.c use PIO mode for blocks > 137 GB, and LBA28 DMA (instead of LBA48 DMA) for blocks <= 137 GB. bart: argh, I forgot about 'lba48' flag; patch slightly modified by me Signed-off-by: -
Alasdair G. Kergon authored
Rename ctr to create etc. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Alasdair G. Kergon authored
Some multipath code/formatting cleanups Signed-off-by:
-
Alasdair G. Kergon authored
Tag multipath exports GPL. Signed-off-by:
-
Alasdair G. Kergon authored
Outline Hardware Handler for EMC CLARiiON AX/CX-series. Signed-Off-By:
Alasdair G Kergon <agk@redhat.com> From: Lars Marowsky-Bree <lmb@suse.de> Signed-off-by:
-
Alasdair G. Kergon authored
Each multipath instance can use a Hardware Handler with hooks for the particular hardware you're using. This patch provides the hw_handler infrastructure. So far 3 hooks are available: A status function invoked by device-mapper table and status requests. An initialisation function called when a Priority Group is selected for use but before any I/O is sent to it. This function should return straight away, and I/O is queued until dm_pg_init_complete() is called indicating whether or not the initialisation was successful. The are three error flags, any or all of which may be set: MP_FAIL_PATH, MP_BYPASS_PG, MP_ERROR_IO. An error handler which gets the opportunity to decode any error that a bio generated. Patches are pending to make scsi error details available for dm_scsi_err_handler() to decode. Signed-Off-By:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Alasdair G. Kergon authored
A very basic path selector: round-robin. It uses in turn each path that has not been disabled. By default, it instructs core multipath to use each path it supplies for 1000 bios, but a different repeat_count can be set against any path to provide primitive load-balancing across unequal paths. Signed-Off-By:
-
Alasdair G. Kergon authored
The core device-mapper multipath and path-selector code. Paths are grouped into an ordered list of Priority Groups. Each Priority Group has a Path Selector which chooses which of the Priority Group's paths is to be used for each bio e.g. according to some load-balancing algorithm. If a bio generates an error, the path that it used gets disabled and an alternative path is tried. If all the paths in a Priority Group fail, another Priority Group is selected. There are management commands fail_path and reinstate_path. A path tester (currently implemented in userspace) is responsible for monitoring paths that have failed and reinstating them should they come back. Other management commands can be use to switch immediately to a specified Priority Group or to disable a particular Priority Group so it will only be tried after there are no more left. As a last resort there is an option to 'queue_if_no_path' which queues I/O if all paths have failed e.g. temporarily during a firmware update or if the userspace daemon is slow reinstating paths. The userspace multipath tools are available at: http://christophe.varoqui.free.fr/ macroflux.png is a diagram of the current architecture. From: Alasdair G Kergon <agk@redhat.com> Don't requeue I/O repeatedly if there are no paths left and the device is in the process of being suspended, or else the suspend can never complete. Reported-By:
"goggin, edward" <egoggin@emc.com> Signed-Off-By:
-
Alasdair G. Kergon authored
Export map_info (part of bio->bi_private) for targets like multipath to use for storing context. Signed-Off-By:
-
Alasdair G. Kergon authored
Simple functions to record and restore bio state so we can resubmit a bio that returned an error. DM multipath (following shortly) uses this. This patch has it private to device-mapper: is it any use elsewhere? Signed-Off-By:
-
Lars Marowsky-Bree authored
Add a name field to struct dm_dev so we don't have to use format_dev_t() all over the place for informative error messages. Signed-Off-By:
-
Randy Dunlap authored
Fix tdfxfb section references: convert __initdata to __devinitdata. Error: ./drivers/video/tdfxfb.o .text refers to 0000000000000e6f R_X86_64_PC32 .init.data+0xfffffffffffffffc Error: ./drivers/video/tdfxfb.o .text refers to 0000000000000fea R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001006 R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001022 R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000103c R_X86_64_PC32 .init.data+0x00000000000000f4 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001067 R_X86_64_PC32 .init.data+0x00000000000000f4 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000106f R_X86_64_PC32 .init.data+0x00000000000000fc Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001084 R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 00000000000010f1 R_X86_64_PC32 .init.data+0x00000000000000cc Error: ./drivers/video/tdfxfb.o .text refers to 00000000000011b8 R_X86_64_PC32 .init.data+0x00000000000000d4 Error: ./drivers/video/tdfxfb.o .text refers to 00000000000011c1 R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000122b R_X86_64_PC32 .init.data+0x00000000000000d4 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001232 R_X86_64_PC32 .init.data+0x00000000000000cc Error: ./drivers/video/tdfxfb.o .text refers to 000000000000124a R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001320 R_X86_64_PC32 .init.data+0x00000000000000d4 Error: ./drivers/video/tdfxfb.o .text refers to 0000000000001327 R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000134c R_X86_64_32S .init.data+0x00000000000000c0 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000136a R_X86_64_PC32 .init.data+0x00000000000000e6 Error: ./drivers/video/tdfxfb.o .text refers to 000000000000137d R_X86_64_PC32 .init.data+0x00000000000000e8 Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013b1 R_X86_64_PC32 .init.data+0xfffffffffffffffc Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013c5 R_X86_64_PC32 .init.data+0xfffffffffffffffc Error: ./drivers/video/tdfxfb.o .text refers to 00000000000013e4 R_X86_64_32S .init.data+0x0000000000000020 Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Randy Dunlap authored
Fix sis section reference: change 2 __init functions to be __devinit. Error: ./drivers/video/sis/sis_main.o .text refers to 0000000000000b5b R_X86_64_PC32 .init.text+0xfffffffffffffffc Signed-off-by:
-
Randy Dunlap authored
Fix riva sections references: change __initdata to __devinitdata. Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001e64 R_X86_64_32S .init.data+0x0000000000000020 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001e6f R_X86_64_PC32 .init.data+0x0000000000000004 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001e7c R_X86_64_PC32 .init.data+0x0000000000000003 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001e93 R_X86_64_PC32 .init.data Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001ec6 R_X86_64_PC32 .init.data+0x000000000000005c Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001ef2 R_X86_64_PC32 .init.data+0x0000000000000034 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001f38 R_X86_64_PC32 .init.data+0x000000000000005c Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001f41 R_X86_64_PC32 .init.data+0x0000000000000054 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001f4f R_X86_64_PC32 .init.data+0x000000000000002c Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000001f94 R_X86_64_PC32 .init.data+0x000000000000002c Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000201a R_X86_64_PC32 .init.data+0x0000000000000034 Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000002035 R_X86_64_PC32 .init.data+0x0000000000000034 Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000203c R_X86_64_PC32 .init.data+0x000000000000002c Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000206b R_X86_64_PC32 .init.data+0xfffffffffffffffb Error: ./drivers/video/riva/fbdev.o .text refers to 0000000000002074 R_X86_64_PC32 .init.data+0x0000000000000034 Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000207b R_X86_64_PC32 .init.data+0x000000000000002c Error: ./drivers/video/riva/fbdev.o .text refers to 00000000000020e7 R_X86_64_32S .init.data+0x0000000000000020 Error: ./drivers/video/riva/fbdev.o .text refers to 00000000000021cb R_X86_64_32S .init.data+0x0000000000000080 Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000220f R_X86_64_PC32 .init.data+0x000000000000011c Error: ./drivers/video/riva/fbdev.o .text refers to 000000000000228e R_X86_64_32S .init.data+0x0000000000000080 Error: ./drivers/video/riva/fbdev.o .text refers to 00000000000022ea R_X86_64_PC32 .init.data+0x0000000000000007 Signed-off-by:
-
