mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaliyi <imgrey@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: libata extension
Date: Mon, 12 Mar 2007 19:12:22 +0200	[thread overview]
Message-ID: <3aac340703121012k7d2bb9cby62651079405ad8e7@mail.gmail.com> (raw)
In-Reply-To: <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>

---------- Forwarded message ----------
From: Vitaliyi <imgrey@gmail.com>
Date: Mar 12, 2007 7:03 PM
Subject: Re: libata extension
To: Mark Lord <lkml@rtr.ca>


> Use the SCSI SG_IO ioctl() with opcode=ATA_16,
> which gives you access to the ATA Passthrough mechanism.
> This will work for most ATA commands.

How about soft-reset, is it possible to reach Device Control Register ?
Seems not. I was thinking about patch to libata which allow to use
Control Register.
In the perfect case i would like to be able to execute vendor command
set (reverse engineered).

Is it possible to control timeouts in user space precisely enough and
get rid of unnecessary kernel error messages without touching
syslogd/klogd?

By the way, how to make libata to not probe some ide channel or drive ?

> I already use it in hdparm and in some other utilities
> for scanning/repairing drives.
>
> A notable exeception are the READ/WRITE LONG opcodes,
> which require an extra kernel patch from me,
> awaiting merge into libata some year.

Could you please send me this patch once it's ready ?


Thank you

  parent reply	other threads:[~2007-03-12 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-11  7:22 Vitaliyi
2007-03-11 14:09 ` Bartlomiej Zolnierkiewicz
2007-03-12 14:47 ` Mark Lord
     [not found]   ` <3aac340703121003l43685599t8dbffe6247879a91@mail.gmail.com>
2007-03-12 17:12     ` Vitaliyi [this message]
     [not found]     ` <3aac340703121007q35c7acf7t648e0ed7608be04d@mail.gmail.com>
     [not found]       ` <200703122106.39669.bzolnier@gmail.com>
2007-03-13  2:36         ` Fwd: " Vitaliyi
2007-03-13 11:23           ` 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=3aac340703121012k7d2bb9cby62651079405ad8e7@mail.gmail.com \
    --to=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

all inboxes | Powered by JetHome®