From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, Carlos.Pardo@siliconimage.com
Subject: Re: [PATCH] libata: fix READ CAPACITY simulation
Date: Tue, 28 Nov 2006 04:10:34 -0500 [thread overview]
Message-ID: <456BFD0A.90209@pobox.com> (raw)
In-Reply-To: <20061120021547.GL2184@htj.dyndns.org>
Tejun Heo wrote:
> * READ CAPACITY (16) implementation fixed. Result was shifted by two
> bytes. Carlos Pardo spotted this problem and submitted preliminary
> patch. Capacity => 2TB is handled correctly now. (verifid w/ fake
> capacity)
>
> * Use dev->n_sectors instead of re-reading directly from ID data.
>
> * Define and use ATA_SCSI_RBUF_SET() which considers rbuf length.
> This should be done for all simulation functions. Userland can
> issue any simulated command with arbitrary buffer length.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Carlos Pardo <Carlos.Pardo@siliconimage.com>
ACK
prev parent reply other threads:[~2006-11-28 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 2:15 [PATCH] libata: fix READ CAPACITY simulation Tejun Heo
2006-11-28 9:10 ` 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=456BFD0A.90209@pobox.com \
--to=jgarzik@pobox.com \
--cc=Carlos.Pardo@siliconimage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).