On Wed, Nov 13, 2013 at 02:53:34PM +0100, Gerd Hoffmann wrote: > On Mi, 2013-11-13 at 11:58 +0000, Wei Liu wrote: > > On Wed, Nov 13, 2013 at 08:03:39AM +0100, Gerd Hoffmann wrote: > > > Hi, > > > > > > > > The first thing that comes in mind is to reuse E820 table for memory > > > > > map > > > > > plus some extra fields for io / mmio resources. But I guess UEFI is > > > > > the > > > > > new world so stuffs like E820 from old world will be less popular. Any > > > > > suggestion on existing table / data structure I can use? > > > > > > What io/mmio ressources do you need to pass on? > > > > > > > MMIO holes, IO range created by hvmloader. > > Why? All (memory) address space not backed by ram effectively is mmio. > There is no need to explicitly declare holes ... >
Yes there is, because hvmloader is in charge of declaring holes. OVMF should just use whatever it gets. > Also why io ranges? Isn't pc io address space pretty much fixed anyway? > This is not actually necessary, but I want to pass this anyway, just to be consistent. Wei. > cheers, > Gerd > > ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
