From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, stable@kernel.org, kelk1@comcast.net,
lcapitulino@mandriva.com.br
Subject: Re: [PATCH] libata: implement BROKEN_HPA horkage and apply it to HDS724040KLSA80
Date: Wed, 08 Aug 2007 11:21:08 +0900 [thread overview]
Message-ID: <46B92894.8060502@gmail.com> (raw)
In-Reply-To: <20070807175844.6818ffc9@the-village.bc.nu>
Alan Cox wrote:
>>> I'd rather know what is going on here. A drive can legitimately
>>> support LBA48 and HPA and refuse READ_NATIVE_MAX_EXT.
>> READ_NATIVE_MAX_EXT is mandatory if HPA && LBA48, no
>
> Ok the report in that thread is different. The offending Maxtor simply
> aborts the read_native_max_ext
I'll resend sans ata_id_has_hpa() change. Does that sound okay? I
don't really think we can do anything other than blacklisting it.
--
tejun
next prev parent reply other threads:[~2007-08-08 2:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 5:42 [PATCH] libata: implement BROKEN_HPA horkage and apply it to HDS724040KLSA80 Tejun Heo
2007-08-07 14:51 ` Luiz Fernando N. Capitulino
2007-08-07 15:00 ` Tejun Heo
2007-08-07 15:04 ` Luiz Fernando N. Capitulino
2007-08-07 15:25 ` Alan Cox
2007-08-07 15:36 ` Tejun Heo
2007-08-07 15:47 ` Jeff Garzik
2007-08-07 16:57 ` Alan Cox
2007-08-07 16:52 ` Jeff Garzik
2007-08-07 16:53 ` Alan Cox
2007-08-07 16:53 ` Tejun Heo
2007-08-07 16:58 ` Alan Cox
2007-08-08 2:21 ` Tejun Heo [this message]
2007-08-08 9:35 ` Alan Cox
2007-08-08 13:23 ` Luiz Fernando N. Capitulino
2007-08-08 13:40 ` Tejun Heo
2007-08-07 18:46 ` Chuck Ebbert
2007-08-07 19:41 ` Alan Cox
2007-08-07 22:12 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:50 Quel Qun
2007-08-08 16:54 ` Luiz Fernando N. Capitulino
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=46B92894.8060502@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=kelk1@comcast.net \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-ide@vger.kernel.org \
--cc=stable@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.