All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Martin Dalecki <dalecki@evision-ventures.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.6-pre2 IDE cleanup 16
Date: Tue, 05 Mar 2002 16:42:33 -0500	[thread overview]
Message-ID: <3C853BC9.EC553363@mandrakesoft.com> (raw)
In-Reply-To: <E16i9mc-00043p-00@wagner.rustcorp.com.au> <3C84A34E.6060708@evision-ventures.com> <3C84AE16.A7F1ECCA@redhat.com> <20020305221933.A405@ucw.cz>

Vojtech Pavlik wrote:
> 
> On Tue, Mar 05, 2002 at 11:37:58AM +0000, Arjan van de Ven wrote:
> > Martin Dalecki wrote:
> >
> > > - Disable configuration of the task file stuff. It is going to go away
> > >    and will be replaced by a truly abstract interface based on
> > >    functionality and *not* direct mess-up of hardware.
> >
> > Can we also expect a patch to remove the scb's from the scsi midlayer
> > from you ?
> > I mean, if a standard specifies a nice *common* command packet format
> > I'd expect the midlayer
> > to create such packets. Taskfile is exactly that... why removing it ?
> 
> Note that taskfiles are not being removed from IDE. Just direct (and
> parsed and filtered) interface to userspace. Does the scsi midlayer
> export the SCBs directly to userspace?

It should.

I think it's a mistake to remove the taskfile interface.

It provides a way for people to directly validate the lowest level IDE
interface, without interference from upper layers.  It also provides
access to userspace for important features that -should not- be in the
kernel, like SMART monitoring and security features.

	Jeff



-- 
Jeff Garzik      |
Building 1024    |
MandrakeSoft     | Choose life.

  reply	other threads:[~2002-03-05 21:42 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  7:54 [PATCH] per-cpu areas Rusty Russell
2002-03-05 10:51 ` [PATCH] 2.5.6-pre2 IDE cleanup 16 Martin Dalecki
2002-03-05 11:07   ` Zwane Mwaikambo
2002-03-05 11:28     ` Jens Axboe
2002-03-05 11:54       ` Martin Dalecki
2002-03-05 12:04         ` Jens Axboe
2002-03-05 12:09           ` Martin Dalecki
2002-03-06  0:33         ` Alan Cox
2002-03-06  9:51           ` Martin Dalecki
2002-03-05 11:48     ` Martin Dalecki
2002-03-06  0:34       ` Alan Cox
2002-03-05 12:36     ` Anton Altaparmakov
2002-03-05 12:36       ` Martin Dalecki
2002-03-05 12:35         ` Zwane Mwaikambo
2002-03-06  0:28         ` Alan Cox
2002-03-05 12:47       ` Anton Altaparmakov
2002-03-05 12:52         ` Martin Dalecki
2002-03-06  1:40           ` Alan Cox
2002-03-06  8:56             ` Zwane Mwaikambo
2002-03-06  9:43             ` Martin Dalecki
2002-03-06  0:27       ` Alan Cox
2002-03-06 10:15         ` Martin Dalecki
2002-03-05 11:37   ` Arjan van de Ven
2002-03-05 11:51     ` Martin Dalecki
2002-03-05 21:19     ` Vojtech Pavlik
2002-03-05 21:42       ` Jeff Garzik [this message]
2002-03-05 21:46         ` Vojtech Pavlik
2002-03-06  9:19           ` Martin Dalecki
2002-03-06  1:08       ` Alan Cox
2002-03-06  9:45         ` Martin Dalecki
2002-03-06  0:41   ` Alan Cox
2002-03-06  9:15     ` benh
2002-03-06 11:07       ` Martin Dalecki
2002-03-06 11:12         ` Zwane Mwaikambo
2002-03-06 11:59           ` Martin Dalecki
2002-03-06 12:02         ` Meelis Roos
2002-03-06 12:11           ` Martin Dalecki
2002-03-06 16:01         ` Bill Davidsen
2002-03-06 20:36           ` Linus Torvalds
2002-03-06 17:00         ` benh
2002-03-06  9:49     ` Martin Dalecki
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06 13:46 Ronnie Sahlberg
2002-03-13 15:55 Rick A. Hohensee

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=3C853BC9.EC553363@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=arjanv@redhat.com \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.