From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Jeremy Higdon <jeremy@sgi.com>,
Andrew Vasquez <praka@users.sourceforge.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
jes@sgi.com
Subject: Re: qla1280 endiannes and 64/32bit fixes
Date: Mon, 19 Jan 2004 17:40:27 +0000 [thread overview]
Message-ID: <20040119174027.B3176@infradead.org> (raw)
In-Reply-To: <1074437655.1804.12.camel@mulgrave>; from James.Bottomley@steeleye.com on Sun, Jan 18, 2004 at 09:54:13AM -0500
On Sun, Jan 18, 2004 at 09:54:13AM -0500, James Bottomley 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.
Guys, given that problems with that nvram reading stuff show up again and
again, shouldn't we rip out the code looking at the nvram completely?
Or at least disable it by default and enable it only by a module option
(for both qla1280 and qla2xxx).
next prev parent reply other threads:[~2004-01-19 17:40 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 [this message]
2004-01-19 21:13 ` Jes Sorensen
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=20040119174027.B3176@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=jeremy@sgi.com \
--cc=jes@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.