From: Jeff Garzik <jgarzik@pobox.com>
To: "Huang, Shane" <Shane.Huang@amd.com>
Cc: Aaron Lu <aaron.lu@intel.com>,
Robert Hancock <hancockrwd@gmail.com>,
Borislav Petkov <bp@amd64.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ata4.00: failed to get Identify Device Data, Emask 0x1
Date: Fri, 16 Nov 2012 12:44:28 -0500 [thread overview]
Message-ID: <50A67B7C.4090608@pobox.com> (raw)
In-Reply-To: <43EB3AB3EEFE8D43B525F4D2EAF507E107EF3D53@SCYBEXDAG04.amd.com>
On 11/16/2012 11:02 AM, Huang, Shane wrote:
>> I tried word 78 bit 5(Hardware Feature Control) which does not work,
>> it is 0 on my HDD sample with log 30h page 08h and DevSlp supported.
>>
>> Seems that word 78 bit 5 is only the sufficient condition, not the
>> essential condition. Do you guys have suggestion?
>
> Eventually I received the confirmation from the DevSlp HDD vendor,
> bit 5 should be and will be set in production drives with log 30h
> page 08h supported. So I will submit a patch to use it instead.
>
>
> Hi Jeff,
>
> I don't know when I will receive some production drives to verify
> my patch, are you okay if I submit my patch first without testing
> so as to meet kernel 3.7 bug fix window?
Yes, please do.
Jeff
prev parent reply other threads:[~2012-11-16 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:49 ata4.00: failed to get Identify Device Data, Emask 0x1 Borislav Petkov
2012-10-16 14:58 ` Alan Cox
2012-10-16 15:18 ` Borislav Petkov
2012-10-17 1:38 ` Aaron Lu
2012-10-17 4:50 ` Robert Hancock
2012-10-17 6:55 ` Aaron Lu
2012-10-18 9:11 ` Huang, Shane
2012-11-16 16:02 ` Huang, Shane
2012-11-16 17:44 ` Jeff Garzik [this message]
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=50A67B7C.4090608@pobox.com \
--to=jgarzik@pobox.com \
--cc=Shane.Huang@amd.com \
--cc=aaron.lu@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@amd64.org \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.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 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.