From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Erik Mouw <erik@harddisk-recovery.com>,
linux-ide@vger.kernel.org
Subject: Re: TASKFILE ioctl for libata?
Date: Fri, 17 Feb 2006 09:50:51 -0500 [thread overview]
Message-ID: <43F5E2CB.6040804@rtr.ca> (raw)
In-Reply-To: <43F5951B.3020605@gmail.com>
Tejun Heo wrote:
>
> Also, as you pointed out, it's hardware-wise impossible to do
> register-level granuality with SATA and I'll be surprised if any more
> need for register-level granuality arises than there currently is.
I hope we can keep in mind that libata is about much more than
plain old SATA these days -- it appears about to displace my long
lost IDE subsystem and all of the PATA, Cardbus, and PC-Card devices
that it has long been the sole interface for.
Far be it from me to favour trying to implement the crazy TASKFILE
ioctl() here, though. We just need to nudge the Passthru mechanism
in the right directions so that it can cover everyone's needs,
including those for low-level vendor commands (for drive test etc..).
Cheers
next prev parent reply other threads:[~2006-02-17 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 14:34 TASKFILE ioctl for libata? Erik Mouw
2006-02-15 19:00 ` Mark Lord
[not found] ` <a3d8b0a0602151257x52f6011bs1b37d9ac43b26619@mail.gmail.com>
2006-02-15 21:10 ` Matt Gillette
2006-02-16 0:06 ` Tejun Heo
2006-02-16 0:56 ` Erik Mouw
2006-02-16 2:20 ` Jeff Garzik
2006-02-16 9:30 ` Tejun Heo
2006-02-17 8:38 ` Jeff Garzik
2006-02-17 9:19 ` Tejun Heo
2006-02-17 14:50 ` Mark Lord [this message]
2006-02-17 17:17 ` Erik Mouw
2006-02-17 18:27 ` Timothy Thelin
2006-02-17 17:05 ` Erik Mouw
2006-02-17 17:15 ` Bartlomiej Zolnierkiewicz
2006-02-17 17:28 ` Erik Mouw
2006-02-17 18:13 ` Bartlomiej Zolnierkiewicz
2006-02-17 17:07 ` Erik Mouw
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=43F5E2CB.6040804@rtr.ca \
--to=liml@rtr.ca \
--cc=erik@harddisk-recovery.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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).