From: Daniel Phillips <phillips@arcor.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jens Axboe <axboe@suse.de>, Samium Gromoff <_deepfire@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [2.5] DAC960
Date: Sun, 15 Sep 2002 18:20:09 +0200 [thread overview]
Message-ID: <E17qc81-0000D1-00@starship> (raw)
In-Reply-To: <1032102890.25716.7.camel@irongate.swansea.linux.org.uk>
On Sunday 15 September 2002 17:14, Alan Cox wrote:
> On Sun, 2002-09-15 at 05:21, Daniel Phillips wrote:
> > A somewhat curt reply, it could be seen as a brush-off. I believe the
> > whole story goes something like this: the scsi system is a festering
> > sore on the whole and eventually needs to be rationalized. But until
> > that happens, we should basically just keep nursing along the various
> > drivers that should be using a generic interface, until there really
> > is a generic interface around worth putting in the effort to port to.
>
> DAC960 doesn't present a scsi interface to the higher levels. Its
> abstraction truely is block based, like i2o_block, like aacraid, like
> many other cards.
Yup, brainlock, I knew that. Just bracketing the target...
--
Daniel
next prev parent reply other threads:[~2002-09-15 16:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 5:30 Samium Gromoff
2002-09-10 6:20 ` Jens Axboe
2002-09-10 16:16 ` Dave Olien
2002-09-15 4:21 ` Daniel Phillips
2002-09-15 13:19 ` Jens Axboe
2002-09-15 15:23 ` Daniel Phillips
2002-09-15 16:18 ` Daniel Phillips
2002-09-16 20:13 ` Dave Olien
2002-09-16 20:26 ` Daniel Phillips
2002-09-16 22:08 ` Dave Olien
2002-09-16 22:25 ` Dave Olien
2002-09-19 18:49 ` Dave Olien
2002-09-19 19:16 ` Daniel Phillips
2002-09-19 22:09 ` Dave Olien
2002-09-19 22:21 ` Daniel Phillips
2002-09-20 6:21 ` Jens Axboe
2002-09-20 21:32 ` Daniel Phillips
2002-09-19 21:25 ` Dave Olien
2002-09-20 6:20 ` Jens Axboe
2002-09-15 15:14 ` Alan Cox
2002-09-15 16:20 ` Daniel Phillips [this message]
2002-09-18 16:17 James Bottomley
2002-09-18 16:40 ` Daniel Phillips
2002-09-23 19:23 Dave Olien
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=E17qc81-0000D1-00@starship \
--to=phillips@arcor.de \
--cc=_deepfire@mail.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--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®