From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
James Bottomley <james.bottomley@steeleye.com>
Subject: Re: [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one
Date: Tue, 9 Oct 2007 09:41:47 -0700 [thread overview]
Message-ID: <20071009164147.GB19854@plap3.qlogic.org> (raw)
In-Reply-To: <470B9E50.2090205@emulex.com>
On Tue, 09 Oct 2007, James Smart wrote:
> Why do you prefer request_firmware() vs something over sysfs ?
>
> Does environments like the kdump kernel also have access to data needed
> by request_firmware() ?
There's already much in the way of automation and infrastructure
present in supporting the request_firwmare() interfaces (perhaps not
the best of names) which can provide for a level of flexibility beyond
a basic 'soft_port_name' interface.
Though I don't see why both can't coexist cleanly -- I take it the use
case you are considering is: software recognizes no valid WWPN
available, query via request_firmware() fails, software halts
initialization (rather than fail), and awaits the admin to poke
'0x123456.. > /sys/.../fc_host/soft_port_name', causing a ping to the
driver and continuation of initialization with requested portname?
next prev parent reply other threads:[~2007-10-09 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 21:25 [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one Darrick J. Wong
2007-10-08 22:48 ` Andrew Vasquez
2007-10-08 23:50 ` Darrick J. Wong
2007-10-09 0:12 ` Andrew Vasquez
2007-10-09 15:29 ` James Smart
2007-10-09 16:41 ` Andrew Vasquez [this message]
2007-10-09 17:06 ` Darrick J. Wong
2007-10-10 14:54 ` James Smart
2007-10-10 15:40 ` Jeff Garzik
2007-10-10 19:38 ` 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=20071009164147.GB19854@plap3.qlogic.org \
--to=andrew.vasquez@qlogic.com \
--cc=James.Smart@Emulex.Com \
--cc=alexisb@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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