From: Albert Lee <albertcc@tw.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_pdc2027x: Restore various updates done on the driver
Date: Thu, 15 Mar 2007 14:04:54 +0800 [thread overview]
Message-ID: <45F8E206.2000206@tw.ibm.com> (raw)
In-Reply-To: <20070308233920.7371d07d@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> - Use of cable_detect method
> - ata_pci_default_filter needed on PATA100 ops
> - Filter for UDMA 133 errata from vendor (not enabled in this diff but
> added ready)
>
> Signed-off-by: Alan Cox <alan@redhat.com>
>
<snip>
>
> /**
> + * pdc2720x_mode_filter - mode selection filter
> + * @adev: ATA device
> + * @mask: list of modes proposed
> + *
> + * Block UDMA on devices that cause trouble with this controller.
> + */
> +
> +static unsigned long pdc2027x_mode_filter(struct ata_device *adev, unsigned long mask)
> +{
> + unsigned char model_num[ATA_ID_PROD_LEN + 1];
> + struct ata_device *pair = ata_dev_pair(adev);
> +
> + if (adev->class != ATA_DEV_ATA || adev->devno == 0 || pair == NULL)
> + return ata_pci_default_filter(adev, mask);
> +
> + /* Check for slave of a Maxtor at UDMA6 */
> + ata_id_c_string(pair->id, model_num, ATA_ID_PROD,
> + ATA_ID_PROD_LEN + 1);
> + /* If the master is a maxtor in UDMA6 then the slave should not use UDMA 6 */
> + if(strstr(model_num, "Maxtor") == 0 && pair->dma_mode == XFER_UDMA_6)
> + mask &= ~ (1 << (6 + ATA_SHIFT_UDMA));
Some Maxtor drives have "Maxtor" while others have "MAXTOR" in the IDENTIFY data.
Should we check both "Maxtor" and "MAXTOR" here?
--
albert
> +
> + return ata_pci_default_filter(adev, mask);
> +}
> +
> +/**
next prev parent reply other threads:[~2007-03-15 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 23:39 [PATCH] pata_pdc2027x: Restore various updates done on the driver Alan Cox
2007-03-09 13:03 ` Jeff Garzik
2007-03-09 13:11 ` Jeff Garzik
2007-03-15 6:04 ` Albert Lee [this message]
2007-03-15 12:00 ` 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=45F8E206.2000206@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.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).