Hi Marcelo, hi Alan,
the trivial patch below updates the information about the chipsets
supported by hpt366.c.
Please apply
Adrian
--- linux-2.4.20/drivers/ide/Config.in.old 2003-01-11 20:58:01.000000000 +0100
+++ linux-2.4.20/drivers/ide/Config.in 2003-01-11 20:59:20.000000000 +0100
@@ -56,7 +56,7 @@
dep_tristate ' Cyrix CS5530 MediaGX chipset support' CONFIG_BLK_DEV_CS5530 $CONFIG_BLK_DEV_IDEDMA_PCI
dep_tristate ' HPT34X chipset support' CONFIG_BLK_DEV_HPT34X $CONFIG_BLK_DEV_IDEDMA_PCI
dep_mbool ' HPT34X AUTODMA support (WIP)' CONFIG_HPT34X_AUTODMA $CONFIG_BLK_DEV_HPT34X $CONFIG_IDEDMA_PCI_WIP
- dep_tristate ' HPT366/368/370 chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
+ dep_tristate ' HPT36X/37X chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
dep_tristate ' Intel PIIXn chipsets support' CONFIG_BLK_DEV_PIIX $CONFIG_BLK_DEV_IDEDMA_PCI
if [ "$CONFIG_MIPS_ITE8172" = "y" -o "$CONFIG_MIPS_IVR" = "y" ]; then
dep_mbool ' IT8172 IDE support' CONFIG_BLK_DEV_IT8172 $CONFIG_BLK_DEV_IDEDMA_PCI
--- linux-2.4.20/Documentation/Configure.help.old 2003-01-11 20:59:56.000000000 +0100
+++ linux-2.4.20/Documentation/Configure.help 2003-01-11 21:00:54.000000000 +0100
@@ -1161,11 +1161,13 @@
If unsure, say N.
-HPT366/368/370 chipset support
+HPT36X/37X chipset support
CONFIG_BLK_DEV_HPT366
HPT366 is an Ultra DMA chipset for ATA-66.
HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
HPT370 is an Ultra DMA chipset for ATA-100.
+ HPT372 is an Ultra DMA chipset for ATA-133.
+ HPT374 is an Ultra DMA chipset for ATA-133.
This driver adds up to 4 more EIDE devices sharing a single
interrupt.
Caution!
I and Andrew Morton have hpt374's which do not behave will under U133.
It could be a device - controller combination erratium but not sure
Cheers,
On Sat, 11 Jan 2003, Adrian Bunk wrote:
> Hi Marcelo, hi Alan,
>
> the trivial patch below updates the information about the chipsets
> supported by hpt366.c.
>
> Please apply
> Adrian
>
> --- linux-2.4.20/drivers/ide/Config.in.old 2003-01-11 20:58:01.000000000 +0100
> +++ linux-2.4.20/drivers/ide/Config.in 2003-01-11 20:59:20.000000000 +0100
> @@ -56,7 +56,7 @@
> dep_tristate ' Cyrix CS5530 MediaGX chipset support' CONFIG_BLK_DEV_CS5530 $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_tristate ' HPT34X chipset support' CONFIG_BLK_DEV_HPT34X $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_mbool ' HPT34X AUTODMA support (WIP)' CONFIG_HPT34X_AUTODMA $CONFIG_BLK_DEV_HPT34X $CONFIG_IDEDMA_PCI_WIP
> - dep_tristate ' HPT366/368/370 chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
> + dep_tristate ' HPT36X/37X chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_tristate ' Intel PIIXn chipsets support' CONFIG_BLK_DEV_PIIX $CONFIG_BLK_DEV_IDEDMA_PCI
> if [ "$CONFIG_MIPS_ITE8172" = "y" -o "$CONFIG_MIPS_IVR" = "y" ]; then
> dep_mbool ' IT8172 IDE support' CONFIG_BLK_DEV_IT8172 $CONFIG_BLK_DEV_IDEDMA_PCI
> --- linux-2.4.20/Documentation/Configure.help.old 2003-01-11 20:59:56.000000000 +0100
> +++ linux-2.4.20/Documentation/Configure.help 2003-01-11 21:00:54.000000000 +0100
> @@ -1161,11 +1161,13 @@
>
> If unsure, say N.
>
> -HPT366/368/370 chipset support
> +HPT36X/37X chipset support
> CONFIG_BLK_DEV_HPT366
> HPT366 is an Ultra DMA chipset for ATA-66.
> HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
> HPT370 is an Ultra DMA chipset for ATA-100.
> + HPT372 is an Ultra DMA chipset for ATA-133.
> + HPT374 is an Ultra DMA chipset for ATA-133.
>
> This driver adds up to 4 more EIDE devices sharing a single
> interrupt.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Andre Hedrick
LAD Storage Consulting Group
On Sat, Jan 11, 2003 at 01:42:46PM -0800, Andre Hedrick wrote:
> Caution!
>
> I and Andrew Morton have hpt374's which do not behave will under U133.
> It could be a device - controller combination erratium but not sure
This is an area where you have more knowledge than I do.
I do only know people who don't have DMA support because you don't
select "HPT366/368/370 chipset support" when you have a HPT374.
What about the patch below?
> Cheers,
cu
Adrian
--- linux-2.4.20/drivers/ide/Config.in.old 2003-01-11 20:58:01.000000000 +0100
+++ linux-2.4.20/drivers/ide/Config.in 2003-01-11 20:59:20.000000000 +0100
@@ -56,7 +56,7 @@
dep_tristate ' Cyrix CS5530 MediaGX chipset support' CONFIG_BLK_DEV_CS5530 $CONFIG_BLK_DEV_IDEDMA_PCI
dep_tristate ' HPT34X chipset support' CONFIG_BLK_DEV_HPT34X $CONFIG_BLK_DEV_IDEDMA_PCI
dep_mbool ' HPT34X AUTODMA support (WIP)' CONFIG_HPT34X_AUTODMA $CONFIG_BLK_DEV_HPT34X $CONFIG_IDEDMA_PCI_WIP
- dep_tristate ' HPT366/368/370 chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
+ dep_tristate ' HPT36X/37X chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
dep_tristate ' Intel PIIXn chipsets support' CONFIG_BLK_DEV_PIIX $CONFIG_BLK_DEV_IDEDMA_PCI
if [ "$CONFIG_MIPS_ITE8172" = "y" -o "$CONFIG_MIPS_IVR" = "y" ]; then
dep_mbool ' IT8172 IDE support' CONFIG_BLK_DEV_IT8172 $CONFIG_BLK_DEV_IDEDMA_PCI
--- linux-2.4.20/Documentation/Configure.help.old 2003-01-11 23:05:04.000000000 +0100
+++ linux-2.4.20/Documentation/Configure.help 2003-01-11 23:06:42.000000000 +0100
@@ -1161,11 +1161,14 @@
If unsure, say N.
-HPT366/368/370 chipset support
+HPT36X/37X chipset support
CONFIG_BLK_DEV_HPT366
- HPT366 is an Ultra DMA chipset for ATA-66.
- HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
- HPT370 is an Ultra DMA chipset for ATA-100.
+ This driver includes support for the following chipsets:
+ - HPT366
+ - HPT368
+ - HPT370
+ - HPT372
+ - HPT374
This driver adds up to 4 more EIDE devices sharing a single
interrupt.
Adrian,
It is fine.
I just do not want to over represent the drivers capabilities.
Cheers,
On Sat, 11 Jan 2003, Adrian Bunk wrote:
> On Sat, Jan 11, 2003 at 01:42:46PM -0800, Andre Hedrick wrote:
>
> > Caution!
> >
> > I and Andrew Morton have hpt374's which do not behave will under U133.
> > It could be a device - controller combination erratium but not sure
>
> This is an area where you have more knowledge than I do.
>
> I do only know people who don't have DMA support because you don't
> select "HPT366/368/370 chipset support" when you have a HPT374.
>
> What about the patch below?
>
> > Cheers,
>
> cu
> Adrian
>
> --- linux-2.4.20/drivers/ide/Config.in.old 2003-01-11 20:58:01.000000000 +0100
> +++ linux-2.4.20/drivers/ide/Config.in 2003-01-11 20:59:20.000000000 +0100
> @@ -56,7 +56,7 @@
> dep_tristate ' Cyrix CS5530 MediaGX chipset support' CONFIG_BLK_DEV_CS5530 $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_tristate ' HPT34X chipset support' CONFIG_BLK_DEV_HPT34X $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_mbool ' HPT34X AUTODMA support (WIP)' CONFIG_HPT34X_AUTODMA $CONFIG_BLK_DEV_HPT34X $CONFIG_IDEDMA_PCI_WIP
> - dep_tristate ' HPT366/368/370 chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
> + dep_tristate ' HPT36X/37X chipset support' CONFIG_BLK_DEV_HPT366 $CONFIG_BLK_DEV_IDEDMA_PCI
> dep_tristate ' Intel PIIXn chipsets support' CONFIG_BLK_DEV_PIIX $CONFIG_BLK_DEV_IDEDMA_PCI
> if [ "$CONFIG_MIPS_ITE8172" = "y" -o "$CONFIG_MIPS_IVR" = "y" ]; then
> dep_mbool ' IT8172 IDE support' CONFIG_BLK_DEV_IT8172 $CONFIG_BLK_DEV_IDEDMA_PCI
> --- linux-2.4.20/Documentation/Configure.help.old 2003-01-11 23:05:04.000000000 +0100
> +++ linux-2.4.20/Documentation/Configure.help 2003-01-11 23:06:42.000000000 +0100
> @@ -1161,11 +1161,14 @@
>
> If unsure, say N.
>
> -HPT366/368/370 chipset support
> +HPT36X/37X chipset support
> CONFIG_BLK_DEV_HPT366
> - HPT366 is an Ultra DMA chipset for ATA-66.
> - HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
> - HPT370 is an Ultra DMA chipset for ATA-100.
> + This driver includes support for the following chipsets:
> + - HPT366
> + - HPT368
> + - HPT370
> + - HPT372
> + - HPT374
>
> This driver adds up to 4 more EIDE devices sharing a single
> interrupt.
>
Andre Hedrick
LAD Storage Consulting Group
On Sat January 11 2003 13:42, Andre Hedrick wrote:
>
> Caution!
>
> I and Andrew Morton have hpt374's which do not behave will under U133.
> It could be a device - controller combination erratium but not sure
>
Well that _used_ to be the case. But I just retested - the hpt374 under
2.5.56 is writing at a smooth 35 megs/sec to a single disk using UDMA6.
So it looks like something got fixed - it used to write extremely slowly
unless I forced it back to UDMA5.