linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: Re: HEADS UP for QLA2100 users
Date: Sat, 4 Feb 2006 23:58:01 +0100	[thread overview]
Message-ID: <20060204225801.GD4528@stusta.de> (raw)
In-Reply-To: <1130542543.23729.160.camel@localhost.localdomain>

On Fri, Oct 28, 2005 at 04:35:43PM -0700, Badari Pulavarty wrote:
> On Fri, 2005-10-28 at 16:03 -0700, Andrew Vasquez wrote:
> > On Fri, 28 Oct 2005, Christoph Hellwig wrote:
> > 
> > > On Thu, Oct 27, 2005 at 02:53:13PM -0700, Andrew Vasquez wrote:
> > > 
> > > > I'm still in the process of ironing out the .bin distribution details
> > > > locally, but perhaps once we migrate to firmware-loading exclusively
> > > > via request_firmware(), the (small?) contigent of 2100 could use the
> > > > EF variant I referenced above.
> > > 
> > > You know, I'm in favour of getting firmware images in the kernel image,
> > > but what's the problem of simply downgrading the 2100 firmware until
> > > we get rid of the builtin firmware for all qla2xxx variants?
> > 
> > I have no problems with submitting 1.17.38 EF for inclusion upstream.
> > My only hope is that for the (other) 2100 user out there that use the
> > latest 2100 firmware and are not experiencing problems, the downgrade
> > does not break anything.
> > 
> > That's another reason I posed the following question:
> > 
> > > > Could I get another informal count of 2100 users who are still having
> > > > problems with qla2xxx?
> > 
> > Perhaps I should also ask:
> > 
> > 	Who's running 2100 cards with the latest qla2xxx driver and
> > 	are experiencing no problems?
> 
> Hmm.. I thought qla2xxx driver doesn't like qla2100. I had troubles
> getting my qla2100 cards to work with qal2xxx (9 months ago) and
> gave up and using only qla2200 and qla2300 card.
> 
> Is there a point in me going back and trying qla2100 ? (Ofcourse,
> I need to locate those cards).

Now that in 2.6.16-rc the recommended method for firmware loading in
qla2xxx is to load it from userspace, the firmware version problems 
should have become non-issues.

If ypu have hardware that works in 2.6.16-rc2 with the qlogicfc driver 
but not with the qal2xxx driver, a bug report would be appreciated.

> Thanks,
> Badari

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-02-04 22:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051024014838.0dd491bb.akpm@osdl.org>
     [not found] ` <1130186927.6831.23.camel@localhost.localdomain>
2005-10-24 21:16   ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 15:12     ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-25 17:57       ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 16:13     ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 15:26     ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 15:44       ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-27 16:48         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 19:02       ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 21:53         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-28 22:51           ` HEADS UP for QLA2100 users Christoph Hellwig
2005-10-28 23:03             ` Andrew Vasquez
2005-10-28 23:35               ` Badari Pulavarty
2006-02-04 22:58                 ` Adrian Bunk [this message]
2006-02-14  0:14                   ` [2.6 patch] schedule the SCSI qlogicfc driver for removal Adrian Bunk
2006-02-14 17:43                     ` Christoph Hellwig
2006-03-25 18:04                       ` Adrian Bunk
2005-10-29 19:59 ` 2.6.14-rc5-mm1: SAS: compile error with gcc 2.95 Adrian Bunk
2005-10-29 20:15   ` Luben Tuikov

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=20060204225801.GD4528@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbadari@gmail.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).