From: Jack Steiner <steiner@sgi.com>
To: Len Brown <lenb@kernel.org>
Cc: hpa@zytor.com, hmh@hmh.eng.br, tony.luck@gmail.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
gbeshers@sgi.com
Subject: Re: [PATCH] - Mapping ACPI tables as CACHED
Date: Tue, 14 Dec 2010 20:41:36 -0600 [thread overview]
Message-ID: <20101215024136.GB19601@sgi.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1012141903210.25387@x980>
On Tue, Dec 14, 2010 at 07:04:13PM -0500, Len Brown wrote:
> hmm, my arrandale laptop fails to get into graphics mode w/ this patch
> applied -- last thing i see is the kernel freeing memory, then black
> screen.
>
> thanks,
> Len Brown, Intel Open Source Technology Center
Do you know where the ACPI tables actually reside? In RAM
or in another type of memory.
The original version of this patch made the cacheable mapping
a platform attribute that was set via a function called thru
the x86_platform_ops. This was intended to minimize the potential
for breaking systems with BIOSes that used non-RAM ACPI tables.
There are a lot of different BIOSes and I'm not even close to
understanding them all.
Wonder if I should resurrect that version of the patch....
next prev parent reply other threads:[~2010-12-15 2:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 22:09 [PATCH] - Mapping ACPI tables as CACHED Jack Steiner
2010-12-14 22:58 ` H. Peter Anvin
2010-12-14 23:22 ` Len Brown
2010-12-15 0:26 ` H. Peter Anvin
2010-12-15 2:27 ` Jack Steiner
2010-12-15 4:17 ` H. Peter Anvin
2010-12-15 0:04 ` Len Brown
2010-12-15 1:18 ` H. Peter Anvin
2010-12-15 2:40 ` Len Brown
2010-12-15 2:41 ` Jack Steiner [this message]
2010-12-15 4:03 ` Len Brown
2010-12-15 4:35 ` Len Brown
2010-12-15 6:17 ` H. Peter Anvin
2010-12-15 6:17 ` Milton Miller
2010-12-15 6:29 ` H. Peter Anvin
2010-12-15 16:46 ` Jack Steiner
2010-12-15 21:16 ` Len Brown
2010-12-15 22:18 ` H. Peter Anvin
2010-12-17 2:54 ` Len Brown
2010-12-17 8:08 ` [PATCH] ACPI: use ioremap_cache() Len Brown
2010-12-27 19:42 ` Tony Luck
2010-12-27 20:12 ` H. Peter Anvin
2010-12-28 3:21 ` Shaohua Li
2010-12-28 3:35 ` H. Peter Anvin
2010-12-28 5:02 ` Shaohua Li
2010-12-28 20:12 ` H. Peter Anvin
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=20101215024136.GB19601@sgi.com \
--to=steiner@sgi.com \
--cc=gbeshers@sgi.com \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@gmail.com \
/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