Hi Alex,
We are using tiger4 platform. I didn't find md about space:
0xa0000-0xc0000 in efi memmap, maybe it was assumed EFI_MEMORY_MAPPED_IO in
native OS. But dom_fw_init shouldn't neglect it to set IO space according to
MDs efi provides. Seems your platform has VGA console. So this patch can enable
VGA console on all platforms explicitly, maybe as you said this step is better
to do in dom_fw_init :)
Thanks
-Xiantao
> -----Original Message-----
> From: Alex Williamson [mailto:[EMAIL PROTECTED]
> Sent: 2006年5月31日 23:32
> To: Zhang, Xiantao
> Cc: xen-ia64-devel@lists.xensource.com
> Subject: Re: [Xen-ia64-devel] [PATCH]Fix domain0 no VGA console bug.
>
> On Wed, 2006-05-31 at 20:30 +0800, Zhang, Xiantao wrote:
> > After enabling dom0_vp mode, we lost domain0's VGA console, and we have
> > to connect it through network or serial console.
> > The reason is that VGA frame buffer(0xa0000-0xc0000) was set to
> > conventional
> > memory not IO in dom0's p2m table. Attached patch fixes it.
>
> Hi Xiantao,
>
> What about systems that don't have VGA? What memory type does your
> system report in the EFI MDT for address 0xA0000? I would expect
> EFI_MEMORY_MAPPED_IO, but if it's something else, it probably needs to
> be assigned a passthrough in dom_fw_init(). Thanks,
>
> Alex
>
> --
> Alex Williamson HP Open Source & Linux Org.
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
