From: Julien Plissonneau Duquene <lkml.20030224@julien.plissonneau.duquene.net>
To: linux-kernel@vger.kernel.org
Subject: ide ioctls draft manpage - feedback wanted
Date: Mon, 24 Feb 2003 00:08:11 +0000 [thread overview]
Message-ID: <20030224000811.GA14003@junk.org> (raw)
Hi,
I needed a doc to HDIO_... ioctls, couldn't find any, and decided to
write my own. I use those to write data (or drives) recovery programs
that bypass almost completely the block I/O. The programs are not
written yet, I would like to understand the IDE layer first.
It can be found here :
http://junk.org/~jpd/kernelstuff/ide_ioctls
for the "formatted" edition, just add .4 for the source code.
This is about kernel 2.4.19, I lack bandwidth/time/drive
space/financial incentives to upgrade. Mostly bandwidth. And thus I will
follow the discussions on the list archives, so don't expect replies in
the minute.
If you know better than me on the subject (e.g. you write IDE drivers,
IDE utilities that need to send raw commands, or are among the IDE
maintainers) I would like to hear from you. There are blanks on the
page, stuff I guessed, and stuff I don't really understand.
Thanks in advance for help.
--
Julien Plissonneau Duquène.
reply other threads:[~2003-02-23 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030224000811.GA14003@junk.org \
--to=lkml.20030224@julien.plissonneau.duquene.net \
--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