Re: Frame buffer mmap not working in pvops dom0

[Daniel De Graaf <dgdegra@tycho.nsa.gov>]

On 07/28/2010 10:29 AM, Konrad Rzeszutek Wilk wrote:
>>> If that fixes your problem, are you OK with me sticking a Signed-off-by:
>>> from you on this patch?
>>>
>>
>> Yep, your version also fixes the problem, and I agree it's more
>> sensible. I'm OK with signing off on that patch.
> 
> Oh, and here is the S-O-B that I missed sticking on the git tree.
> 
> Anyhow, I found out that his patch also fixes the Nvidia fb problem,
> which is quite nice.
> 
> By any chance did you try to use Xserver on top of this patch? In the
> past I had gotten this (from Xorg.0.log file):
> 
> ==) 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
> ...
> (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
> 
> .. and a continuing stream of FBIOPUTCMAP's.
> 

I had been testing using framebuffer only; I just tested Xorg, and it
appears to be working - I don't see any errors in my Xorg.0.log or on
the Xen console. Haven't tried running anything more interesting than
xterm, though.

I'm not certain if I've ended up testing the Xen fbdev device, or just
using the guest's i915 driver within the guest. This is with an empty
xorg.conf{,.d/}.

The only issue I've been having is that I haven't been able to get the
system to work more than once per powerup, even with a soft reboot of
the host (going back to the real BIOS). There's obviously some state not
being reset by the startup that is tripping it on later boots, but I
haven't yet been able to find out what it is.

-- 

Daniel De Graaf
National Security Agency