From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Vitaliyi <imgrey@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata extension
Date: Sun, 11 Mar 2007 15:09:38 +0100 [thread overview]
Message-ID: <200703111509.38642.bzolnier@gmail.com> (raw)
In-Reply-To: <3aac340703102322p362998b9labedc13503702d2b@mail.gmail.com>
Hi,
On Sunday 11 March 2007, Vitaliyi wrote:
> Good Day
>
> Say i want to implement extended set of ATA commands available to
> userspace for building diagnostic tools.
> I need 0x40 -- read verify and 0x32 -- write long with error handling,
Mark Lord is working on READ/WRITE_LONG support for libata,
he has posted draft patch recently on linux-ide mailing list.
[ Please consider reading/joining linux-ide@vger.kernel.org ML,
it is where Linux ATA discussion happens... ]
> for example. I was trying ide driver through ioctl's, but seems it
> lack of functionality and full of gotchas. Furthermore it oopses
> sometimes.
READ/WRITE_LONG is unsupported and as you've already noticed
TASKFILE ioctls are full of gotchas...
> Is it possible to use libata for such purpose or i need to write
> separate IDE driver ?
It should be possible using ATA pass-through, some libata changes
may be required but it is the right way to go IMO.
Bart
next prev parent reply other threads:[~2007-03-11 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 7:22 libata extension Vitaliyi
2007-03-11 14:09 ` Bartlomiej Zolnierkiewicz [this message]
2007-03-12 14:47 ` Mark Lord
[not found] ` <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>
2007-03-12 17:12 ` Fwd: " Vitaliyi
[not found] ` <3aac340703121007q35c7acf7t648e0ed7608be04d@mail.gmail.com>
[not found] ` <200703122106.39669.bzolnier@gmail.com>
2007-03-13 2:36 ` Vitaliyi
2007-03-13 11:23 ` Jeff Garzik
[not found] <fa.tUT8ZqaAp2RZveBFqwzUhq3UYGI@ifi.uio.no>
2007-03-11 8:04 ` Robert Hancock
2007-03-11 13:31 ` Alan Cox
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=200703111509.38642.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=imgrey@gmail.com \
--cc=linux-kernel@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).