linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH RFC] sata_promise: make pdc_atapi_pkt() use values from qc->tf
Date: Mon, 26 Nov 2007 21:18:38 +0900	[thread overview]
Message-ID: <474AB99E.3030109@gmail.com> (raw)
In-Reply-To: <200711261200.lAQC0vFd029485@harpo.it.uu.se>

Hello,

Mikael Pettersson wrote:
>>  	buf[20] = (1 << 5) | ATA_REG_FEATURE;
>>  	buf[21] = feature;
>>  	buf[22] = (1 << 5) | ATA_REG_BYTEL;
>> -	buf[23] = nbytes & 0xFF;
>> +	buf[23] = qc->tf.lbam;
>>  	buf[24] = (1 << 5) | ATA_REG_BYTEH;
>> -	buf[25] = (nbytes >> 8) & 0xFF;
>> +	buf[25] = qc->tf.lbah;
> 
> The original code matches what Promise' own driver does, including
> the "set byte counter register to real transfer byte count" comment.
> It's certainly possible that if lbah/lbam don't match ->nbytes,
> the HW will go nuts. Their data sheets are very quiet about ATAPI.

Yeah, now core code sets the value properly and I just posted a patch to
massage transfer chunk size a bit so I was curious whether now
sata_promise can use the result of core layer instead.

> I can test your proposed change next weekend when I'm back to where
> my sata_promise test equipment is.

Thank you.

-- 
tejun

  reply	other threads:[~2007-11-26 12:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 12:00 [PATCH RFC] sata_promise: make pdc_atapi_pkt() use values from qc->tf Mikael Pettersson
2007-11-26 12:18 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-03  8:41 Mikael Pettersson
2007-12-02 17:06 Mikael Pettersson
2007-12-03  4:49 ` Tejun Heo
2007-11-26 11:34 Tejun Heo
2007-12-01 23:23 ` Jeff Garzik

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=474AB99E.3030109@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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).