public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Garet Cammer <arcolin@arcoide.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need IDE Taskfile Access
Date: Tue, 18 Jun 2002 16:38:31 +0200	[thread overview]
Message-ID: <3D0F45E7.3050605@evision-ventures.com> (raw)
In-Reply-To: 004701c216cf$efd1ca60$8201a8c0@arcoi0s17j2t0x

Użytkownik Garet Cammer napisał:
> For some time now we have been writing user applications that send ATAPI 
> commands to the IDE bus to initialize and configure our hardware RAID 1 
> controllers. This has been working well, thanks to Andre's patch that 
> gave us taskfile access through the ioctl API. We were counting on it to 
> be a permanent part of the 2.5/2.6 kernel, since there is a lot of 
> hardware in the field using these apps.
> Imagine our surprise when we discovered that taskfile access was being 
> abandoned completely!
> Although we understand that the kernel may need to filter some commands, 
> why can't applications access at least the Smart commands? Help!
> Regards,
> Garet Cammer
> Software Development
> Arco Computer Products
> (954) 925-2688

ATAPI is no problem. You can use the whole SCSI layer on top of
ide-scsi.






       reply	other threads:[~2002-06-18 14:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <004701c216cf$efd1ca60$8201a8c0@arcoi0s17j2t0x>
2002-06-18 14:38 ` Martin Dalecki [this message]
2002-06-18 16:22 ` Need IDE Taskfile Access Andre Hedrick
2002-06-18 19:32   ` Bartlomiej Zolnierkiewicz
2002-06-19  7:54     ` Martin Dalecki
2002-06-19 22:43       ` Scott Tillman
2002-06-19 22:52         ` Dave Jones
2002-06-20 16:36           ` Scott Tillman
2002-06-20  6:24         ` H. Peter Anvin
2002-06-21 22:40         ` Alan Cox
2002-06-21 23:09           ` Andries Brouwer
2002-06-21 23:45   ` 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=3D0F45E7.3050605@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=arcolin@arcoide.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