Re: UNS: Re: [Xen-devel] BAR 0: cirrusfb load errors prevent hvm domu from getting resolutions above 800x600

[jim burns <jim_burn@xxxxxxxxxxxxx>]

On Thu November 17 2011, 8:10:08 AM, Jan Beulich wrote:
> >>> On 17.11.11 at 00:28, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> Sounds more like a kernel problem.
> 
> > <4>[    0.629101] vesafb: cannot reserve video memory at 0xf0000000
> 
> This doesn't tell what component did the reservation before this point,
> but that's what he/you will need to find out. And then compare with
> the cirrusfb case.

I thought that's what this meant:

[    0.667812] vesafb: framebuffer at 0xf0000000, mapped to 
0xffffc90000580000, using 1875k, total 4096k

Looks like vesafb reserved it.

> One significant difference of course is the DRM base fb driver in the
> radeon case - to compare apples with apples, DRM should really be
> removed from the picture.

True. I was just pointing out that there is a mechanism for vesafb handing off 
control to another video driver:

<3>[  259.974310] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - 
removing generic driver

Any ideas where to go from here? Thanx.

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