linux/drivers/ata/Kconfig

728 lines
18 KiB

[PATCH] ATA must depend on BLOCK Fix the following compile error with CONFIG_ATA=y, CONFIG_BLOCK=n: ... CC drivers/ata/libata-scsi.o /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c: In function ‘ata_scsi_dev_config’: /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:791: warning: implicit declaration of function ‘blk_queue_max_sectors’ /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:799: error: ‘request_queue_t’ undeclared (first use in this function) /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:799: error: (Each undeclared identifier is reported only once /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:799: error: for each function it appears in.) /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:799: error: ‘q’ undeclared (first use in this function) /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:800: warning: implicit declaration of function ‘blk_queue_max_hw_segments’ /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c: In function ‘ata_scsi_slave_config’: /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/ata/libata-scsi.c:831: warning: implicit declaration of function ‘blk_queue_max_phys_segments’ make[3]: *** [drivers/ata/libata-scsi.o] Error 1 Bug report by Jesper Juhl. Signed-off-by: Adrian Bunk <bunk@stusta.de> Cc: Jeff Garzik <jeff@garzik.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Jeff Garzik <jeff@garzik.org>
2006-10-20 14:39:35 -07:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
2006-08-10 07:31:37 -04:00
2006-08-24 02:41:25 -04:00
2006-08-10 07:31:37 -04:00
ahci, pata_marvell: play nicely together I've been chasing Jeff about this for months. Jeff added the Marvell device identifiers to the ahci driver without making the AHCI driver handle the PATA port. This means a lot of users can't use current kernels and in most distro cases can't even install. This has been going on since March 2008 for the 6121 Marvell, and late 2007 for the 6145!!! This was all pointed out at the time and repeatedly ignored. Bugs assigned to Jeff about this are ignored also. To quote Jeff in email > "Just switch the order of 'ahci' and 'pata_marvell' in > /etc/modprobe.conf, then use Fedora's tools regenerate the initrd. > See? It's not rocket science, and the current configuration can be > easily made to work for Fedora users." (Which isn't trivial, isn't end user, shouldn't be needed, and as it usually breaks at install time is in fact impossible) To quote Jeff in August 2007 > " mv-ahci-pata > Marvell 6121/6141 PATA support. Needs fixing in the 'PATA controller > command' area before it is usable, and can go upstream." Only he add the ids anyway later and caused regressions, adding a further id in March causing more regresions. The actual fix for the moment is very simple. If the user has included the pata_marvell driver let it drive the ports. If they've only selected for SATA support give them the AHCI driver which will run the port a fraction faster. Allow the user to control this decision via ahci.marvell_enable as a module parameter so that distributions can ship 'it works' defaults and smarter users (or config tools) can then flip it over it desired. Signed-off-by: Alan Cox <alan@redhat.com> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
2008-09-03 14:48:34 +01:00