This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-ia64-devel] [PATCH][GFW] [RFC] enable /proc/acpi/dsdt

To: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] [PATCH][GFW] [RFC] enable /proc/acpi/dsdt
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Mon, 21 Jan 2008 23:57:56 +0900
Delivery-date: Mon, 21 Jan 2008 06:59:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx

We cannot see /proc/acpi/dsdt with open GFW.
I'm debuging it now.
I think the ACPI_PHYSICAL_ADDRESS is not collect
because the range of the memory are all zero.

I made the patch to move ACPI_PHYSICAL_ADDRESS
from 0xea000 to 0x7ff50000 (it's address of Tiger4)
With the patch, I could get data of /proc/acpi/dsdt.
I'm not sure why the 0x7ff50000 is collect...
What do you think about it?

Signed-off-by: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>

Best Regards,

Akio Takebe

Attachment: enbale_dsdt.patch
Description: Binary data

Xen-ia64-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] [PATCH][GFW] [RFC] enable /proc/acpi/dsdt, Akio Takebe <=