From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:45297) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRjRl-0004CE-En for qemu-devel@nongnu.org; Wed, 01 Jun 2011 07:18:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRjRk-00076b-0h for qemu-devel@nongnu.org; Wed, 01 Jun 2011 07:18:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56179) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRjRj-00076O-GE for qemu-devel@nongnu.org; Wed, 01 Jun 2011 07:18:43 -0400 Message-ID: <4DE62005.3070707@redhat.com> Date: Wed, 01 Jun 2011 14:18:29 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20110525023406.GG8517@valinux.co.jp> <20110525043353.GH8517@valinux.co.jp> <4DDCC7A5.60706@redhat.com> <4DDCF9ED.5050208@redhat.com> <4DDDDA8D.6080807@web.de> <4DDDF62C.2010603@redhat.com> <4DDF3768.5010002@web.de> <4DDF867A.9040700@siemens.com> <4DDFFE1E.1060900@web.de> <4DE3486F.10502@redhat.com> <20110531022922.GB10673@valinux.co.jp> <4DE5EA84.7040400@redhat.com> <08A969ED-DDE7-48A0-AFED-283239FFF5CE@suse.de> <4DE61EC4.50402@redhat.com> <5BE6529C-2D6C-4031-A2CD-28E5636A63D6@suse.de> In-Reply-To: <5BE6529C-2D6C-4031-A2CD-28E5636A63D6@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [SeaBIOS] Graphics card pass-through working with two pass pci-initialization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: KVM list , Jan Kiszka , seabios@seabios.org, "qemu-devel@nongnu.org Developers" , Isaku Yamahata , Alex Williamson , Gerd Hoffmann , =?ISO-8859-1?Q?Andr=E9_Weidemann?= On 06/01/2011 02:16 PM, Alexander Graf wrote: > >> > > > > Generating the DSDT dynamically is hard, but the DSDT itself is dynamic. You can make any function talk to the firmware configuration interface and return results that depend on the information there. > > Does that hold true for nodes as well? I thought you can only use 'functions' for specific elements? I believe that if you declare _CRS as a method, it should work (there are both "Name" and "Method" _CRSs in the DSDT currently). -- error compiling committee.c: too many arguments to function