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-devel

Re: [Xen-devel] [PATCH] Framebuffer support on the Intel Mac

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] Framebuffer support on the Intel Mac
From: Marco Gerards <mgerards@xxxxxxxxx>
Date: Tue, 22 Aug 2006 02:11:13 +0200
Delivery-date: Mon, 21 Aug 2006 17:05:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <878xlhd4hx.fsf@xxxxxxxxx> (Marco Gerards's message of "Tue, 22 Aug 2006 01:59:54 +0200")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-copies-to: mgerards@xxxxxxxxx
References: <878xlhd4hx.fsf@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
Marco Gerards <mgerards@xxxxxxxxx> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>