From: "O.Sezer" <sezero@superonline.com>
To: linux-kernel@vger.kernel.org
Subject: Re: HPT372N not supported?
Date: Wed, 19 Mar 2003 17:07:02 +0200 [thread overview]
Message-ID: <3E788796.4060703@superonline.com> (raw)
pci_ids.h also has to be patched; something like this one:
--- linux/include/linux/pci_ids.h.orig 2003-03-11 18:50:01
+++ linux/include/linux/pci_ids.h 2003-03-19 16:16:09
@@ -975,6 +975,7 @@
#define PCI_DEVICE_ID_TTI_HPT372 0x0005
#define PCI_DEVICE_ID_TTI_HPT302 0x0006
#define PCI_DEVICE_ID_TTI_HPT371 0x0007
+#define PCI_DEVICE_ID_TTI_HPT372N 0x0009
#define PCI_DEVICE_ID_TTI_HPT374 0x0008
#define PCI_VENDOR_ID_VIA 0x1106
--
O.Sezer
"Alan Cox" wrote:
On Mon, 2003-03-17 at 17:28, Henning Schroeder wrote:
> I don=C5=BDt like that solution very much, though, because the highpoint
> driver uses the scsi subsystem. Looking through highpoints hpt.c file
> I could not find very much differences in the way the HPT372N is
> accessed from the HPT372-way. Maybe somebody (Andre Hedrick?) could
> look through the code and integrate the HPT372N into
> linux/drivers/ide/pci/hpt366.c? This feat is regrettably way beyound
> my own programming capability.
Try the patch attached below. The 372N doesn't seem to be that different
except that we have to use different pci timing thresholds. The patch
below isn't tested as I don't have a 372N.
> I would love to hear about the current status of that chip. I do not
> need the RAID capability, just the extra IDE ports.
hptraid should already support the raid bits
next reply other threads:[~2003-03-19 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 15:07 O.Sezer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 17:28 HPT372N not supported? Henning Schroeder
2003-03-18 16:06 ` Alan Cox
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=3E788796.4060703@superonline.com \
--to=sezero@superonline.com \
--cc=linux-kernel@vger.kernel.org \
/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.