From: Jes Sorensen <jes@sgi.com>
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>
Subject: Re: qla1280 endiannes and 64/32bit fixes
Date: 18 Jan 2004 16:59:33 -0500 [thread overview]
Message-ID: <1074463172.1591.2.camel@lappy.trained-monkey.org> (raw)
In-Reply-To: <1074437655.1804.12.camel@mulgrave>
On Sun, 2004-01-18 at 09:54, James Bottomley wrote:
> On Sun, 2004-01-18 at 02:33, Jeremy Higdon wrote:
> > James, with your code as it is now, ha->flags.enable_64bit_addressing
> > is always 0. You'd need to add code to read the value out of the
> > nvram. Then we'll need an nvram override for Altix.
>
> Actually, I found it. There was a missed endianness problem in the 64
> bit path (see patch).
>
> 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.
Hi James,
Same problem on Altix, the BIOS can't run as there is no x86 emulation
in the EFI firmware on the box.
Cheers,
Jes
next prev parent reply other threads:[~2004-01-18 22:00 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 [this message]
2004-01-19 17:40 ` Christoph Hellwig
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=1074463172.1591.2.camel@lappy.trained-monkey.org \
--to=jes@sgi.com \
--cc=James.Bottomley@SteelEye.com \
--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.