From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Samuel Flory <sflory@rackable.com>,
"Robert L. Harris" <Robert.L.Harris@rdlg.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1-ac3 still broken on Adaptec I2O
Date: 24 Jul 2003 12:24:00 +0100 [thread overview]
Message-ID: <1059045840.7993.7.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030724090154.A25026@infradead.org>
On Iau, 2003-07-24 at 09:01, Christoph Hellwig wrote:
> On Wed, Jul 23, 2003 at 11:17:32PM +0100, Alan Cox wrote:
> > Either way someone else can fix it if they want, or use the core
> > i2o drivers which should drive this hardware nowdays
>
> So why is dpt_i2o still around then? It's a horrible mess and much
> much worse than i2o_scsi.
Primarily because the i²o drivers didnt use to handle the dpt devices. They
speak a slightly odd dialect of i²o and that tripped us up. I need to check
2.6 has all the 2.4 core i²o stuff in place. With that done then I think
doing some testing and losing dpt_i2o is doable.
Alan
prev parent reply other threads:[~2003-07-24 11:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 20:18 2.6.0-test1-ac3 still broken on Adaptec I2O Robert L. Harris
2003-07-23 20:22 ` Christoph Hellwig
2003-07-23 22:00 ` Robert L. Harris
2003-07-23 22:53 ` Tomas Szepe
2003-07-23 23:32 ` Posting format bill davidsen
2003-07-24 0:52 ` Tomas Szepe
2003-07-24 15:14 ` Steven Cole
2003-07-24 15:47 ` Robert L. Harris
2003-07-24 16:03 ` Tomas Szepe
2003-07-24 16:52 ` Steven Cole
2003-07-24 17:15 ` Robert L. Harris
2003-07-24 17:42 ` Steven Cole
2003-07-24 16:03 ` Bas Mevissen
2003-07-24 16:05 ` Steven Cole
2003-07-24 23:15 ` Bill Davidsen
2003-07-24 23:24 ` CaT
2003-07-25 2:59 ` jw schultz
2003-07-25 3:33 ` Miles Bader
2003-07-24 15:24 ` [OT] " Sean Neakums
2003-07-23 20:24 ` 2.6.0-test1-ac3 still broken on Adaptec I2O Alan Cox
2003-07-23 21:20 ` Samuel Flory
2003-07-23 22:17 ` Alan Cox
2003-07-24 8:01 ` Christoph Hellwig
2003-07-24 11:24 ` Alan Cox [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=1059045840.7993.7.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Robert.L.Harris@rdlg.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sflory@rackable.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).