From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Frame buffer mmap not working in pvops dom0 Date: Wed, 28 Jul 2010 11:33:52 -0400 Message-ID: <20100728153352.GA6848@phenom.dumpdata.com> References: <4C46FA8D.6040809@tycho.nsa.gov> <20100721141613.GG17817@reaktio.net> <20100721144209.GA5031@phenom.dumpdata.com> <4C4711BB.5090905@tycho.nsa.gov> <20100721190056.GA9756@phenom.dumpdata.com> <4C474909.8080005@tycho.nsa.gov> <20100721195006.GA5839@phenom.dumpdata.com> <4C47584F.1000200@tycho.nsa.gov> <20100728142912.GA6817@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20100728142912.GA6817@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Daniel De Graaf Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org > ==) Using config directory: "/etc/xorg.conf.d" > (XEN) mm.c:1747:d0 Bad L1 flags 400000 > (XEN) mm.c:1747:d0 Bad L1 flags 400000 > (XEN) mm.c:1747:d0 Bad L1 flags 400000 With your patch, those messages above are gone. > ... > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument > (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument I get this even on baremetal, so I doubt this Xen problem. But I am curious how the fbdev works then under Xen fbdev device. Or maybe it is a xorg-video-vesa it uses ...