From: Chris Wedgwood <cw@f00f.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
"Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Problems with MSI-X on ia64
Date: Fri, 17 Feb 2006 11:10:26 -0800 [thread overview]
Message-ID: <20060217191026.GA3136@taniwha.stupidest.org> (raw)
In-Reply-To: <20060217163605.GA26660@colo.lackof.org>
On Fri, Feb 17, 2006 at 09:36:05AM -0700, Grant Grundler wrote:
> If the machine is suppose to support a 32-bit OS, then yeah, it's a
> BIOS bug. It all depends on who defines the support matrix.
Well, maybe. I mean, the CPUs all have PAE (in 32-bit mode) and thus
can use 36-bit physical addressing these days (or more in the case of
amd chips).
> The other way is to reassign "invalid" resources (above 4GB) with
> "valid" ones (below 4GB). I suspect windows is doing this and I'd
> rather see linux take this route as well if possible.
Hrm, it may be doing this. I wonder how that works though with 4GB's
of RAM installed?
I originally thought Windows probably allowed the larger addresses
and use PAE but that might not be the case at all.
next prev parent reply other threads:[~2006-02-17 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:14 Problems with MSI-X on ia64 Miller, Mike (OS Dev)
2006-01-26 17:24 ` Mark Maule
2006-01-26 20:24 ` Grant Grundler
2006-02-17 7:58 ` Grant Grundler
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 16:36 ` Grant Grundler
2006-02-17 19:10 ` Chris Wedgwood [this message]
2006-06-01 6:35 ` Grant Grundler
2006-01-26 20:37 Miller, Mike (OS Dev)
2006-01-27 4:37 ` Greg KH
2006-01-27 15:34 Miller, Mike (OS Dev)
2006-02-17 19:52 Luck, Tony
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:21 ` Roland Dreier
2006-02-21 20:21 Miller, Mike (OS Dev)
2006-02-25 16:23 ` Grant Grundler
2006-02-27 18:36 Miller, Mike (OS Dev)
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=20060217191026.GA3136@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=Mike.Miller@hp.com \
--cc=gregkh@suse.de \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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;
as well as URLs for NNTP newsgroup(s).