WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

[Xen-ia64-devel] [GFW PATCH] HVM DSDT fixes

To: Tristan Gingold <tgingold@xxxxxxx>
Subject: [Xen-ia64-devel] [GFW PATCH] HVM DSDT fixes
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Wed, 10 Oct 2007 12:11:02 -0600
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 10 Oct 2007 11:12:21 -0700
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>
Organization: HP OSLO R&D
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Tristan,

  The attached patch fixes a couple things in HVM ACPI namespace.  Most
importantly, the MMIO resource range for the PCI bridge is corrected.  I
also removed the legacy handling of the 0xCF8/0xCFC range, we shouldn't
need this on ia64.  I also reformatted the _OSI code to match the rest
of the file (space vs tab and comment style).  There's still a lot of
legacy devices in the DSDT that I'd like to remove (both of the
motherboard resource devices, the PIC, DMA0, TMR, RTC, SPKR, and FDC0).
Do any of these need to be in the system?  Thanks,

        Alex

BTW, the README for updating dsdt.c looks rather irrelevant to the GFW
build.  I've been using the following steps to build it:
        iasl -p foo -tc dsdt.asl
        tail --lines=1 dsdt.c >> foo.hex
        cp foo.hex dsdt.c
The tail just pulls over DsdtLen.  Is this correct?  Is there an easier
way?

-- 
Alex Williamson                             HP Open Source & Linux Org.

Attachment: hvm_dsdt.patch
Description: Text Data

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
<Prev in Thread] Current Thread [Next in Thread>