All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Bottomley <jbottomley@parallels.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"giridhar.malavali@qlogic.com" <giridhar.malavali@qlogic.com>,
	"konrad@kernel.org" <konrad@kernel.org>,
	"vikas.chaudhary@qlogic.com" <vikas.chaudhary@qlogic.com>,
	"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
	"pjones@redhat.com" <pjones@redhat.com>,
	"iscsi-driver@qlogic.com" <iscsi-driver@qlogic.com>
Subject: Re: [PATCH] iscsi_ibft: search for broadcom specific ibft sign
Date: Wed, 7 May 2014 15:21:58 -0400	[thread overview]
Message-ID: <20140507192158.GA17806@phenom.dumpdata.com> (raw)
In-Reply-To: <1399489950.2227.63.camel@dabdike.int.hansenpartnership.com>

On Wed, May 07, 2014 at 07:12:31PM +0000, James Bottomley wrote:
> On Wed, 2014-05-07 at 09:47 -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, May 07, 2014 at 05:00:20AM -0400, vikas.chaudhary@qlogic.com wrote:
> > > From: Vikas Chaudhary <vikas.chaudhary@qlogic.com>
> > > 
> > > Broadcom iscsi offload firmware uses a non standard ibft sign of "BIFT".
> > 
> > Why? If it uses the standard iBFT format why does it use
> > a non-standard signature?
> 
> This is useful as an academic exercise (and perhaps even a reminder to
> broadcom not to do it again) but I don't think we can make it a show
> stopper.  The boards have shipped with the non-standard signature, so we
> have to work with them.

I agree as the train has left, but this got me thinking about these
questions that I hope Qlogic folks could answer:

 - Mention what else is different - perhaps there are other entries that
   are a bit different? Or maybe the are some non-standard ones added on?

 - How has this been tested? As in had all the fields been tested (so CHAP
   on/off, extra ports, etc).

 - Do future hardware of these cards use the standard one? If so what are they?
   "Anything produced in 2012 and later.." ?
 - Is the subset of hardware that use the non-standard small enough? Would it
   be good to mention it in the commit.

Thanks!
> 
> James
> 

  reply	other threads:[~2014-05-07 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  9:00 [PATCH] iscsi_ibft: search for broadcom specific ibft sign vikas.chaudhary
2014-05-07 13:47 ` Konrad Rzeszutek Wilk
2014-05-07 19:12   ` James Bottomley
2014-05-07 19:21     ` Konrad Rzeszutek Wilk [this message]
2014-05-07 19:49       ` Mike Christie
2014-05-07 20:15         ` Peter Jones
2014-05-07 20:30           ` Mike Christie
2014-05-07 20:57             ` Mike Christie
2014-05-09 11:50               ` Vikas Chaudhary
2014-05-09 13:20                 ` Konrad Rzeszutek Wilk
2014-05-13 12:17                   ` Vikas Chaudhary
2014-05-07 20:19       ` Giridhar Malavali
2014-05-07 19:01 ` Mike Christie
2014-05-13 18:54   ` Konrad Rzeszutek Wilk

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=20140507192158.GA17806@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=giridhar.malavali@qlogic.com \
    --cc=iscsi-driver@qlogic.com \
    --cc=jbottomley@parallels.com \
    --cc=konrad@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=pjones@redhat.com \
    --cc=vikas.chaudhary@qlogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.