From: Tejun Heo <htejun@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <tj@home-tj.org>
Subject: Re: [rfc][patch] ide: fix unneeded LBA48 taskfile registers access
Date: Thu, 10 Feb 2005 09:01:58 +0900 [thread overview]
Message-ID: <420AA476.1040406@gmail.com> (raw)
In-Reply-To: <200502070959.54973.bzolnier@elka.pw.edu.pl>
Hello, Bartlomiej. Happy new lunar year.
Bartlomiej Zolnierkiewicz wrote:
>
> I would prefer to not teach do_rw_taskfile() about ->tf_{in,out}_flags
> (and convert all users to use helpers) - it is much simpler this way,
>
> ->flags field in ide_task_t is needed anyway (32-bit I/O flag).
>
New lunar year day is one of the biggest holidays here, so I haven't
got time to work for a few days. As it's over now, I began to work on
ide drivers again. I applied your task->flags patch and am moving my
patches over it.
One problem is that, with ATA_TFLAG_LBA48, whether to use HOB
registers or not cannot be determined separately for writing and
reading. So, when initializing flush tasks, if WIN_FLUSH_CACHE_EXT is
used, we need to turn on ATA_TFLAG_LBA48 to read error location
properly, and we end up unnecessarily writing HOB registers.
I think we can...
1. Just leave it as it is. It's not that big a deal.
2. Use another flag(s) to control LBA48 reading/writing separately.
3. do my proposal. :-)
I'm currently sticking to #1. Please let me know what you think.
Thanks.
--
tejun
next prev parent reply other threads:[~2005-02-10 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 22:54 [rfc][patch] ide: fix unneeded LBA48 taskfile registers access Bartlomiej Zolnierkiewicz
2005-02-07 4:47 ` Tejun Heo
2005-02-07 8:58 ` Jeff Garzik
2005-02-07 8:59 ` Bartlomiej Zolnierkiewicz
2005-02-10 0:01 ` Tejun Heo [this message]
2005-02-10 0:24 ` Bartlomiej Zolnierkiewicz
2005-02-10 0:52 ` Tejun Heo
2005-02-10 1:31 ` Bartlomiej Zolnierkiewicz
2005-02-10 2:04 ` 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=420AA476.1040406@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@home-tj.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).