From: Zygo Blaxell <zblaxell@feedme.hungrycats.org>
To: andre@linux-ide.org, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Patch for Promise FastTrack 100 Tx2 (aka PDC20268R)
Date: Wed, 29 Aug 2001 07:54:33 -0400 [thread overview]
Message-ID: <20010829075433.A9238@feedme.hungrycats.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
The code in 2.4.9-ac3 for detecting a PDC20268 or PDC20268R doesn't
enable BM-DMA for the PDC20268R. The fix below seems to work for me.
There is a note in the comments to the effect that the Promise FastTrack
100 RAID card has a different PCI device ID just to prevent Linux from
detecting it. Having seen both the UltraATA-100 and FastTrack-100 cards,
I don't believe this is the case.
Unlike certain previous Promise ATA and ATA-RAID controllers, there
are physical differences between the RAID and non-RAID ATA-100 cards.
The UltraATA-100 card is a normal 33MHz PCI card, while the FastTrack
100 is a 66MHz PCI card.
Then again, last time I checked, 66MHz cards _look_ just like 33MHz cards.
Hmmm...
diff -ur linux/drivers/ide/ide-pci.c 586-smp/kernel-source-2.4.9-ac3-zb-586-smp-zb2001082823/drivers/ide/ide-pci.c
--- linux/drivers/ide/ide-pci.c Mon Aug 13 17:56:19 2001
+++ 586-smp/kernel-source-2.4.9-ac3-zb-586-smp-zb2001082823/drivers/ide/ide-pci.c Tue Aug 28 23:31:08 2001
@@ -767,6 +767,7 @@
IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20265) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20267) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20268) ||
+ IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20268R) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_AEC6210) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_AEC6260) ||
IDE_PCI_DEVID_EQ(d->devid, DEVID_AEC6260R) ||
diff -ur linux/drivers/ide/pdc202xx.c 586-smp/kernel-source-2.4.9-ac3-zb-586-smp-zb2001082823/drivers/ide/pdc202xx.c
--- linux/drivers/ide/pdc202xx.c Mon Aug 13 17:56:19 2001
+++ 586-smp/kernel-source-2.4.9-ac3-zb-586-smp-zb2001082823/drivers/ide/pdc202xx.c Tue Aug 28 23:31:21 2001
@@ -133,6 +133,7 @@
switch(dev->device) {
case PCI_DEVICE_ID_PROMISE_20268:
+ case PCI_DEVICE_ID_PROMISE_20268R:
p += sprintf(p, "\n PDC20268 TX2 Chipset.\n");
invalid_data_set = 1;
break;
--
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2001-08-29 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010829075433.A9238@feedme.hungrycats.org \
--to=zblaxell@feedme.hungrycats.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®