From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Gerards Subject: Re: [PATCH] Framebuffer support on the Intel Mac Date: Tue, 22 Aug 2006 02:11:13 +0200 Message-ID: <87u045bpem.fsf@xs4all.nl> References: <878xlhd4hx.fsf@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <878xlhd4hx.fsf@xs4all.nl> (Marco Gerards's message of "Tue, 22 Aug 2006 01:59:54 +0200") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Marco Gerards writes: Hi, > When booting the Intel Mac in non-legacy mode (EFI), it doesn't > support textmode. In order to get a console in Xen, I have written a > framebuffer for the Intel Mac. At the moment it was only tested on > the MacBook. Because a framebuffer is capable of showing more than > just text, I have added the Xen logo at startup. I made a photo last > week, although this was while I was hacking it and this was under > xen-testing. But it should give you an impression of what it looks > like. See the end of the email for the URLs. Something I forgot to mention is that I was unable to use ioremap to map in the video memory. But the memory was already mapped to the virtual memory address that matches the physical address. To be honest, I do not know (yet) why ioremap doesn't work in this case and why directly accessing the memory does work. I am wondering if this will cause problems at a later stage, Xen does not boot all the way yet because there other other things I have to change before Xen will work properly with EFI. -- Marco