From: Jes Sorensen <jes@wildopensource.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Jeremy Higdon <jeremy@sgi.com>,
Andrew Vasquez <praka@users.sourceforge.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: qla1280 endiannes and 64/32bit fixes
Date: 19 Jan 2004 16:13:40 -0500 [thread overview]
Message-ID: <yq065f7od4r.fsf@wildopensource.com> (raw)
In-Reply-To: <20040119174027.B3176@infradead.org>
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
Christoph> On Sun, Jan 18, 2004 at 09:54:13AM -0500, James Bottomley
Christoph> wrote:
>> However, I have another question for you: Does the card BIOS
>> actually get to run on bootup? It doesn't (because it can't) on
>> PA, so I get strange values for certain NVRAM quantities (like the
>> 32 bit mode, but more importantly, the offset of all my devices
>> gets set to 1). I was thinking about doing an override to set them
>> more sensibly and wondered if you were having the same problem.
Christoph> Guys, given that problems with that nvram reading stuff
Christoph> show up again and again, shouldn't we rip out the code
Christoph> looking at the nvram completely? Or at least disable it by
Christoph> default and enable it only by a module option (for both
Christoph> qla1280 and qla2xxx).
Christoph, I have thought about this before and while I agree in
principle that relying on BIOS settings is inherently broken, I am
also wary of changing a behavior a number of users are currently
relying upon.
Second, for qla2xxx you need a persistent place where you can store
the Fibre Channel ID (the name slips my mind right now).
Cheers,
Jes
next prev parent reply other threads:[~2004-01-19 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 23:40 qla1280 endiannes and 64/32bit fixes James Bottomley
2004-01-18 2:43 ` Jeremy Higdon
2004-01-18 3:16 ` James Bottomley
2004-01-18 6:21 ` Andrew Vasquez
2004-01-18 7:33 ` Jeremy Higdon
2004-01-18 14:54 ` James Bottomley
2004-01-18 21:59 ` Jes Sorensen
2004-01-19 17:40 ` Christoph Hellwig
2004-01-19 21:13 ` Jes Sorensen [this message]
2004-01-18 14:35 ` James Bottomley
2004-01-19 8:54 ` Jes Sorensen
2004-01-18 7:08 ` Jeremy Higdon
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=yq065f7od4r.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=praka@users.sourceforge.net \
/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.