From: Adrian Bunk <bunk@fs.tum.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch] update help for hpt366.c
Date: Sat, 11 Jan 2003 23:08:49 +0100 [thread overview]
Message-ID: <20030111220849.GK21826@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10301111335480.11839-100000@master.linux-ide.org>
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.
next prev parent reply other threads:[~2003-01-11 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 20:04 [2.4 patch] update help for hpt366.c Adrian Bunk
2003-01-11 21:42 ` Andre Hedrick
2003-01-11 22:08 ` Adrian Bunk [this message]
2003-01-11 22:19 ` Andre Hedrick
2003-01-11 22:47 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030111220849.GK21826@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.