All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graham Wood <linux@dragonhold.org>
To: Jes Sorensen <jes@wildopensource.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] qla1280.c patch against 2.6.9 to allow settings of Initiator ID
Date: Tue, 30 Nov 2004 10:36:04 +0000	[thread overview]
Message-ID: <20041130103604.GA3539@dragonhold.org> (raw)
In-Reply-To: <yq0is7n63lw.fsf@jaguar.mkp.net>

On Tue, Nov 30, 2004 at 05:19:39AM -0500, Jes Sorensen wrote:
> What would be the reasoning for this patch? 
I've got a pair of dual 10160 controller cards that I've salvaged and don't have a PC BIOS on them - which means I've got no way to set the SCSI ID other than through the driver.  They both default to ID7, which causes a problem when I attempt to dual-attach storage.

I couldn't find any way to do that, so I patched the driver.  Since I wasn't sure if this would help other people, I thought I'd offer it as a patch.  It also seemed a simple enough change to be a good place to start, since I want to get a better understanding of the stuff I'm running as well.

> higher level rather than by the individual drivers IMHO.
Definitely - it would be better if there was a standard way to specify the SCSI ID, but since this gets set during the module initialisation, I'm not sure what sort of higher level API would make sense.

AFAIK, without unloading & reloading the driver, I don't think there's a sane way to change the ID on these cards, or indeed probably any card - since it involves a complete reset of the card (again, AFAIK).

There are similar options on a couple of the drivers, which is why I thought just adding it here would be the simplest way to do it.


Graham

      reply	other threads:[~2004-11-30 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05  1:18 [PATCH] qla1280.c patch against 2.6.9 to allow settings of Initiator ID linux
2004-11-30 10:19 ` Jes Sorensen
2004-11-30 10:36   ` Graham Wood [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=20041130103604.GA3539@dragonhold.org \
    --to=linux@dragonhold.org \
    --cc=jes@wildopensource.com \
    --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 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.