From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Andre Hedrick (anhedric)" <anhedric@cisco.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, lkml@vger.kernel.org
Subject: Re: CFA 4.0 patch
Date: Tue, 15 May 2012 14:15:04 +0400 [thread overview]
Message-ID: <4FB22CA8.8080207@mvista.com> (raw)
In-Reply-To: <4E75C4FECC27A44E9F7E0737D71946900F686C5B@xmb-sjc-21e.amer.cisco.com>
Hello.
On 15-05-2012 8:57, Andre Hedrick (anhedric) wrote:
> This is a missing part of the CFA 4.0 and above support.
> 6.2.1.6.1 Word 0: General Configuration
> This field indicates the general characteristics of the device.
> When Word 0 of the Identify drive information is 848Ah then the device
> is a CompactFlash Storage Card and complies with the CFA specification
> and CFA command set. It is recommended that PC Card modes of operation
> report only the 848Ah value as they are always intended as removable
> devices.
> Bits 15-0: CF Standard Configuration Value
> Word 0 is 848Ah. This is the recommended value of Word 0.
> Some operating systems require Bit 6 of Word 0 to be set to 1
> (Non-removable device) to use the card as the root storage device. The
> Card must be the root storage device when a host completely replaces
> conventional disk storage with a CompactFlash Card in True IDE mode. To
> support this requirement and provide capability for any future removable
> media Cards, alternate handling of Word 0 is permitted.
> Bits 15-0: CF Preferred Alternate Configuration Values
> 044Ah: This is the alternate value of Word 0 turns on ATA device and
> turns off Removable Media and Removable Device while preserving all
> Retired bits in the word.
> 0040h: This is the alternate value of Word 0 turns on ATA device and
> turns off Removable Media and Removable Device while zeroing all
> Retired bits in the word
> Cheers,
> Andre
> --------------------
> The Linux X-ATA/SATA guy
>
>
> --- linux-2.6.32.orig/include/linux/ata.h Mon May 14 15:48:24 2012
> +++ linux-2.6.32/include/linux/ata.h Mon May 14 15:51:42 2012
> @@ -819,6 +819,10 @@
> {
> if (id[ATA_ID_CONFIG] == 0x848A) /* Traditional CF */
> return 1;
> + if (id[ATA_ID_CONFIG] == 0x044A) /* Alternative CF w/
> removable turned off, preserving retired bits */
> + return 1;
> + if (id[ATA_ID_CONFIG] == 0x0040) /* Alternative CF w/
> removable turned off, zeroing retired bits*/
> + return 1;
Have you read the code below this point? We rely on the CFA feature set
bit in the word 83 if the word 0 is non-traditional. Or does this below check
not detect your CF?
Your patch won't apply to the recent kernels anyway.
> /*
> * CF specs don't require specific value in the word 0 anymore
> and yet
> * they forbid to report the ATA version in the word 80 and
> require the
Patch is also line wrapped.
WBR, Sergei
next prev parent reply other threads:[~2012-05-15 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 4:57 CFA 4.0 patch Andre Hedrick (anhedric)
2012-05-15 10:15 ` Sergei Shtylyov [this message]
2012-05-15 11:07 ` Andre Hedrick (anhedric)
2012-05-15 11:37 ` Sergei Shtylyov
2012-05-15 19:20 ` Andre Hedrick (anhedric)
2012-05-16 12:26 ` Sergei Shtylyov
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=4FB22CA8.8080207@mvista.com \
--to=sshtylyov@mvista.com \
--cc=anhedric@cisco.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=lkml@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