From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: petkovbb@gmail.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: IDE S.M.A.R.T. ioctl errors
Date: Sat, 2 Aug 2008 18:38:55 +0200 [thread overview]
Message-ID: <200808021838.55477.bzolnier@gmail.com> (raw)
In-Reply-To: <488E405E.4010300@rtr.ca>
On Monday 28 July 2008, Mark Lord wrote:
> If we're going to continue to keep drivers/ide on life-support,
> then perhaps one should just add SG_IO::ATA_16 support into it
> and leave the "legacy" ioctls alone.
I was actually hoping that somebody will came with this idea (+ patch)
after we unified all separate taskfile execution code-paths and added
struct ide_taskfile (the code is now much more similiar to libata then
it is to old IDE one).
> I've done this for linux-2.2.xx (really!), and the patch was rather
> tiny indeed -- and that custom kernel now supports all of the fancy
> ioctl() needs of hdparm-8.9 and smartctl.
>
> Perhaps a similar patch for drivers/ide ?
>
> Here's my 2.2.xx hack for perusal:
> http://empeg-hijack.sourceforge.net/patches/relative/v489-v490.patch.gz
>
> It won't work on current kernels, of course, but perhaps something similar would.
Thanks, your 2.2.x patch proves the idea well but we need something
more similar to the current libata code for 2.6.x (the resulting patch
should be both smaller and the easier to make than old IDE backport).
Bart
prev parent reply other threads:[~2008-08-02 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 6:01 IDE S.M.A.R.T. ioctl errors Borislav Petkov
2008-07-28 14:44 ` Bartlomiej Zolnierkiewicz
2008-07-28 16:16 ` Boris Petkov
2008-07-28 16:22 ` Bartlomiej Zolnierkiewicz
2008-07-28 21:55 ` Mark Lord
2008-08-02 16:38 ` Bartlomiej Zolnierkiewicz [this message]
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=200808021838.55477.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
/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).