From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Theodore Tso <tytso@mit.edu>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com
Subject: Re: ATA support for 4k sector size
Date: Thu, 26 Feb 2009 00:16:00 -0500 [thread overview]
Message-ID: <yq1eixlg4mn.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20090226030735.GA16891@parisc-linux.org> (Matthew Wilcox's message of "Wed\, 25 Feb 2009 20\:07\:35 -0700")
>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:
Matthew> Lowest aligned logical block address=0
Matthew> This disagrees with Martin's assertion.
Quick answer from one of my contacts. Desktop drives will indeed ship
with an alignment of 1(*). The alignment is hardwired at time of
manufacture and can't be changed.
(*) I had to go back and reread the ATA spec to grok this. READ
CAPACITY(16) indicates the lowest naturally aligned LBA. With LBA 63
offset in play that would be LBA 7.
ATA, on the other hand, indicates how much LBA 0 is offset from the
beginning of the first physical sector. If LBA 63 is naturally aligned
that means that LBA 0 is offset 512 bytes (physical sector 0 starts at
LBA -1 if you will). Hence IDENTIFY DEVICE word 209 will contain 0x4001.
So you need to tweak your RC16 response a bit...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2009-02-26 5:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 22:24 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 1/2] ata: Define new commands from ATA8 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 2/2] ata: Add support for Long Logical Sectors and Long Physical Sectors Matthew Wilcox
2009-02-25 22:53 ` ATA support for 4k sector size H. Peter Anvin
2009-02-25 23:27 ` Martin K. Petersen
2009-02-25 23:33 ` H. Peter Anvin
2009-02-25 23:51 ` Martin K. Petersen
2009-02-26 12:43 ` Karel Zak
2009-02-26 15:17 ` H. Peter Anvin
2009-02-25 23:42 ` H. Peter Anvin
2009-02-25 23:55 ` Martin K. Petersen
2009-02-25 23:57 ` H. Peter Anvin
2009-02-26 0:07 ` Martin K. Petersen
2009-02-26 0:10 ` H. Peter Anvin
2009-02-26 0:17 ` Martin K. Petersen
2009-02-25 23:49 ` david
2009-02-26 0:04 ` Martin K. Petersen
2009-02-26 0:13 ` david
2009-02-26 0:20 ` Martin K. Petersen
2009-02-26 2:50 ` Theodore Tso
2009-02-26 3:05 ` Martin K. Petersen
2009-02-26 3:07 ` Matthew Wilcox
2009-02-26 3:23 ` Martin K. Petersen
2009-12-11 7:05 ` James Andrewartha
2009-12-11 7:26 ` H. Peter Anvin
2009-12-11 7:32 ` Martin K. Petersen
2009-02-26 5:16 ` Martin K. Petersen [this message]
2009-02-26 12:36 ` Matthew Wilcox
2009-02-26 15:32 ` H. Peter Anvin
2009-02-26 20:35 ` Martin K. Petersen
2009-02-26 21:02 ` H. Peter Anvin
2009-03-16 14:51 ` Greg Freemyer
2009-03-16 16:27 ` H. Peter Anvin
2009-03-16 17:37 ` Greg Freemyer
2009-03-16 18:11 ` H. Peter Anvin
2009-03-22 1:20 ` Bill Davidsen
2009-03-18 14:33 ` James Bottomley
2009-02-26 18:22 ` hdparm-9.12 released Mark Lord
2009-03-21 13:47 ATA support for 4k sector size Andries E. Brouwer
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=yq1eixlg4mn.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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
Powered by JetHome