From: Mark Mitchell <mmitchell@eurologic.com>
To: linux-kernel@vger.kernel.org
Subject: Re: raw access and qlogic isp device driver?
Date: Fri, 23 Mar 2001 19:25:36 +0000 [thread overview]
Message-ID: <3ABBA330.2ADCEBAA@eurologic.com> (raw)
In-Reply-To: <E14gUgZ-00050U-00@the-village.bc.nu>
Alan Cox wrote:
>
> ...
>
> > Has anyone used the raw device with qlogicisp driver? Does
> > anyone have any interest in looking at this?
>
> It shouldnt matter which driver is involved, but 2.4 raw stuff
> is reported broken still
Any chance of anyone elaborating on any RAWIO flaws?
*Seems* to work fine with:
- 2.4.2 (inc Dave Miller's zero copy patch)
- qlogic fc driver & qla2200
- PIII
- Seagate ST39103fc drives in a JBOD
I really need to know any *specific* issues with RAWIO.
Cheers,
Mark.
next prev parent reply other threads:[~2001-03-23 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 16:33 raw access and qlogic isp device driver? Joel Gallun
2001-03-23 16:45 ` Alan Cox
2001-03-23 19:25 ` Mark Mitchell [this message]
2001-03-23 22:13 ` Alan Cox
2001-03-28 4:49 ` [PATCH-2.4.2ac26] fix raw IO Stephen Tweedie
2001-03-23 20:09 ` raw access and qlogic isp device driver? Joel Gallun
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=3ABBA330.2ADCEBAA@eurologic.com \
--to=mmitchell@eurologic.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