From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, alan@redhat.com
Cc: jeff@garzik.org, htejun@gmail.com,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: [patch for 2.6.24? 1/1] libata: correct handling of TSS DVD
Date: Tue, 15 Jan 2008 15:52:09 -0500 [thread overview]
Message-ID: <478D1CF9.1040707@garzik.org> (raw)
In-Reply-To: <200801140906.m0E96Ks2020536@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>
> Devices that misreport the validity bit for word 93 look like SATA. If
> they are on the blacklist then we must not test for SATA but assume 40 wire
> in the 40 wire case (The TSSCorp reports 80 wire on SATA it seems!)
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> Cc: Tejun Heo <htejun@gmail.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> include/linux/ata.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff -puN include/linux/ata.h~libata-correct-handling-of-tss-dvd include/linux/ata.h
> --- a/include/linux/ata.h~libata-correct-handling-of-tss-dvd
> +++ a/include/linux/ata.h
> @@ -554,8 +554,6 @@ static inline int ata_drive_40wire(const
>
> static inline int ata_drive_40wire_relaxed(const u16 *dev_id)
> {
> - if (ata_id_is_sata(dev_id))
> - return 0; /* SATA */
> if ((dev_id[93] & 0x2000) == 0x2000)
> return 0; /* 80 wire */
> return 1;
Alan, is this .24 material?
There were a lot of different threads and BZs about this one device, and
I want to triple-check that multiple fixes are not being applied
independently for the same problem.
Jeff
next parent reply other threads:[~2008-01-15 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801140906.m0E96Ks2020536@imap1.linux-foundation.org>
2008-01-15 20:52 ` Jeff Garzik [this message]
2008-01-15 21:01 ` [patch for 2.6.24? 1/1] libata: correct handling of TSS DVD 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=478D1CF9.1040707@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=htejun@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 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.