From: Wakko Warner <wakko@animx.eu.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>, linux-kernel@vger.kernel.org
Subject: Re: Version 6.1.11 of the aic7xxx driver availalbe
Date: Wed, 11 Apr 2001 20:06:43 -0400 [thread overview]
Message-ID: <20010411200643.A3708@animx.eu.org> (raw)
In-Reply-To: <200104100234.f3A2YFs23361@aslan.scsiguy.com> <E14mvvQ-0003zl-00@the-village.bc.nu>
In-Reply-To: <E14mvvQ-0003zl-00@the-village.bc.nu>; from Alan Cox on Tue, Apr 10, 2001 at 12:03:05PM +0100
> > >So, what about on an alpha system. I've asked a few times what I could do,
> > >but you didn't help nor explain what you meant.
> >
> > From talking to the maintainer of the QLogic driver, it appears
> > that there is a generic issue with data mapping on the Alpha.
> > The only way to correct this issue will be for someone to debug
> > it.
>
> This seems to be the case for some Alpha boxes. On these aic7xxx dies with
> 2.4 but then so does IDE DMA for example. The real test would be to run
> Justin's 2.2.19 patch driver and see if that works on Alpha.
Ok, i tried 2.2.19 with only justin's driver. everything works. The tagged
queue is the default, 253, when doing:
for x in b c d;do cp zero sd$x&;done
it works. 2.2.17 stock would give me errors before the end of the write and
just hang. 2.4.x with and without justin's driver would also do the same.
I used 2.2.19 with justin's latest (as of like 3 days ago) driver. I just
now had time to try it.
I'll give 2.4.1 another try with justin's latest driver (time permitting)
--
Lab tests show that use of micro$oft causes cancer in lab animals
prev parent reply other threads:[~2001-04-11 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 21:11 Version 6.1.11 of the aic7xxx driver availalbe Justin T. Gibbs
2001-04-10 2:05 ` Wakko Warner
2001-04-10 2:34 ` Justin T. Gibbs
2001-04-10 11:03 ` Alan Cox
2001-04-10 11:13 ` Wakko Warner
2001-04-10 11:34 ` Alan Cox
2001-04-12 0:06 ` Wakko Warner [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=20010411200643.A3708@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gibbs@scsiguy.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