From: Jeff Garzik <jgarzik@pobox.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
IDE Linux <linux-ide@vger.kernel.org>
Subject: Re: [PATCH/RFC] Port of pdc202xx_new driver to libata
Date: Mon, 18 Oct 2004 13:00:28 -0400 [thread overview]
Message-ID: <4173F6AC.7090409@pobox.com> (raw)
In-Reply-To: <001901c4b4fd$88204bc0$294bbf09@tw.ibm.com>
I'm applying to libata-dev, but won't push this upstream for a while.
My comments:
1) why is ROM enabled? Normally you don't want to do this.
+ /* Enable the ROM */
+ /*
+ if (pdev->resource[PCI_ROM_RESOURCE].start) {
+ pci_write_config_dword(pdev, PCI_ROM_ADDRESS,
+ pdev->resource[PCI_ROM_RESOURCE].start |
PCI_ROM_ADDRESS
_ENABLE);
2) why does this quirk exist? if pata_pdc2027x (libata) will work with
this hardware, then remove this code (and quirk) completely. It is up
to the user to choose the correct driver, if multiple drivers will
function properly on the hardware.
+#ifdef PDC_20276_QUIRK
+ /*
+ * Skip Promise PDC20276 attached to I2O RAID controller
+ */
+ if ((pdev->device == PCI_DEVICE_ID_PROMISE_20276) &&
+ (pdev->bus->self) &&
+ (pdev->bus->self->vendor == PCI_VENDOR_ID_INTEL) &&
+ ((pdev->bus->self->device == PCI_DEVICE_ID_INTEL_I960) ||
+ (pdev->bus->self->device == PCI_DEVICE_ID_INTEL_I960RM))) {
+ printk(KERN_INFO DRV_NAME ": Skipping Promise PDC20276 "
+ "attached to I2O RAID controller.\n");
+ return -ENODEV;
+ }
+#endif
3) the quirk PDC_20270_QUIRK needs work to conform to current PCI API
standards.
next prev parent reply other threads:[~2004-10-18 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 10:06 [PATCH/RFC] Port of pdc202xx_new driver to libata Albert Lee
2004-10-13 19:32 ` Bartlomiej Zolnierkiewicz
2004-10-13 19:58 ` Jeff Garzik
2004-10-13 20:16 ` Bartlomiej Zolnierkiewicz
2004-10-18 10:30 ` Albert Lee
2004-10-18 17:00 ` Jeff Garzik [this message]
2004-10-18 17:26 ` Jeff Garzik
2004-10-21 8:36 ` Albert Lee
2004-10-21 23:10 ` Jeff Garzik
2004-10-22 2:32 ` Albert Lee
2004-10-27 14:46 ` Jeff Garzik
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=4173F6AC.7090409@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertcc@tw.ibm.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).