From: Andi Kleen <andi@firstfloor.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Date: Fri, 1 Jun 2007 22:24:16 +0200 [thread overview]
Message-ID: <20070601202416.GL7217@one.firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706011618270.7446@p34.internal.lan>
> 1. The MCH/ICH8 hub 'requires' a minimum of 512MB to run, the board manual
> states it needs at least 512MB of memort.
> 2. The DVT/IGP graphics uses either 128MB or 256MB, I have it set to
> 128MB.
>
> How can the Linux kernel find this out/poll this information so users do
> not have to know mem=XXXXM?
I don't think it should. The Linux kernel is not trying to be
a BIOS replacement and should not know everything about the platforms
it runs on. We sometimes try to work around very common
bugs, but this one (involving lots of memory and special configuration)
seems to be more in the exotic range where command line options
or waiting for a BIOS update seem better options.
-Andi
next prev parent reply other threads:[~2007-06-01 20:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 18:14 Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Justin Piszcz
2007-06-01 19:10 ` Jesse Barnes
2007-06-01 19:17 ` Justin Piszcz
2007-06-01 19:19 ` Justin Piszcz
2007-06-01 19:21 ` Jesse Barnes
2007-06-01 21:14 ` Andi Kleen
2007-06-01 20:19 ` Justin Piszcz
2007-06-01 20:24 ` Andi Kleen [this message]
2007-06-01 20:26 ` Justin Piszcz
2007-06-01 21:07 ` Jesse Barnes
2007-06-01 21:19 ` Andi Kleen
2007-06-01 21:35 ` Jesse Barnes
2007-06-01 21:41 ` Jesse Barnes
2007-06-02 1:05 ` Venki Pallipadi
2007-06-02 1:15 ` Jesse Barnes
2007-06-02 8:43 ` Justin Piszcz
2007-06-02 9:22 ` Andi Kleen
2007-06-02 20:11 ` Justin Piszcz
2007-06-03 9:15 ` Matt Keenan
2007-06-04 15:40 ` Jesse Barnes
2007-06-04 15:48 ` Ray Lee
2007-06-04 15:49 ` Justin Piszcz
2007-06-04 16:01 ` Ray Lee
2007-06-04 15:54 ` Jesse Barnes
2007-06-04 18:24 ` Andi Kleen
2007-06-04 18:13 ` Eric W. Biederman
2007-06-04 18:22 ` Justin Piszcz
2007-06-04 19:08 ` Justin Piszcz
2007-06-04 19:17 ` Jesse Barnes
2007-06-04 19:18 ` Alan Cox
2007-06-04 21:01 ` Eric W. Biederman
2007-06-05 0:59 ` Yinghai Lu
2007-06-05 1:38 ` Eric W. Biederman
2007-06-05 9:46 ` Andi Kleen
2007-06-05 13:18 ` Justin Piszcz
2007-06-05 17:20 ` Jesse Barnes
2007-06-07 8:47 ` Andi Kleen
2007-06-04 19:23 ` Andi Kleen
2007-06-04 19:24 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? II Andi Kleen
2007-06-05 0:54 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Yinghai Lu
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=20070601202416.GL7217@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@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