From: Mike Anderson <andmike@us.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
James Bottomley <James.Bottomley@steeleye.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Broken SCSI code in the BK tree (was: 2.5.59-mm8)
Date: Fri, 7 Feb 2003 00:50:43 -0800 [thread overview]
Message-ID: <20030207085043.GA2001@beaverton.ibm.com> (raw)
In-Reply-To: <20030207041936.GA26189@krispykreme>
I removed the other Mike Anderson (mikeand@us.ibm.com) from the cc
list, we seem to have many Mike Anderson's around hear :-).
Anton Blanchard [anton@samba.org] wrote:
>
> Hi,
>
> > If I understand correctly, Matthew Jacob's latest isp driver set drives
> > *all* qlogic hardware (or at least all the older stuff like the qlogicisp
> > driver drives). I would much prefer that people simply test out Matthew's
> > driver and use it instead. In fact, if it's ready for 2.5 kernel use, I
> > would strongly recommend that it be considered as a possible replacement
> > in the linux kernel for the default driver on all qlogic cards not handled
> > by the new qla2x00 driver version 6 (DaveM may have objections to that
> > related to sparc if Matthew's driver isn't sparc friendly, but I don't
> > know of any other reason not to switch over).
>
> I had a bunch of problems with the in kernel and vendor qlogic drivers
> on my ppc64 box. Matt Jacob's driver worked out of the box. Davem
> sounded positive last time I asked him about it.
>
> I did a quick forward port to 2.5 a month or two ago, sounds like we
> should work to get it in the kernel. There are some rough edges but
> Mike kindly offered to lend a hand here.
I have been buried lately so I have only taken the patch you sent me
and updated it so it will compile with the most recent SCSI
changes. I also made a few tweaks to the make files.
Currently it is running on my 2202 card system.
When I ran it my other system that has a Qlogic ISP1020 and two Qlogic
2300's it would hang post initing the driver. The driver seemed to be
responsive to external events like port downs, but appeared to not
complete its init. When I use the driver disable defines to turn off
detection of the ISP1020 the driver loaded ok (I only ran it up to 60MB
on a few spindles so not a very good test).
I will look at this more and see if I can understand the cause.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-02-07 8:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:31 2.5.59-mm8 Andrew Morton
2003-02-04 8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:05 ` 2.5.59-mm8 Andrew Morton
2003-02-04 8:08 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04 8:17 ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15 ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06 5:13 ` Martin J. Bligh
2003-02-06 20:50 ` Martin J. Bligh
2003-02-06 22:30 ` Martin J. Bligh
2003-02-06 23:25 ` James Bottomley
2003-02-07 1:24 ` Patrick Mansfield
2003-02-07 2:01 ` Martin J. Bligh
2003-02-07 2:25 ` Patrick Mansfield
2003-02-07 4:05 ` Doug Ledford
2003-02-07 4:19 ` Anton Blanchard
2003-02-07 8:50 ` Mike Anderson [this message]
2003-02-07 4:19 ` Andrew Morton
2003-02-07 4:24 ` Doug Ledford
2003-02-07 4:35 ` William Lee Irwin III
2003-02-07 4:53 ` Matthew Jacob
2003-02-07 4:50 ` Matthew Jacob
2003-02-07 4:28 ` Martin J. Bligh
2003-02-04 9:07 ` 2.5.59-mm8 Dave Hansen
2003-02-04 9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04 9:21 ` Andrew Morton
2003-02-04 9:29 ` David S. Miller
2003-02-04 9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05 8:08 ` 2.5.59-mm8 Mike Galbraith
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=20030207085043.GA2001@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=patmans@us.ibm.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