Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-23 Thread Andy Lutomirski
Andy Lutomirski wrote: Jerome Glisse wrote: smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the fb buffer into vram by doing so we are loosing vram but fbdev need to be reworked to allow change in framebuffer address. I tested this

Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-23 Thread Jerome Glisse
On Tue, 2009-06-23 at 09:12 -0400, Andy Lutomirski wrote: Andy Lutomirski wrote: Jerome Glisse wrote: smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the fb buffer into vram by doing so we are loosing vram but fbdev need to be

Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-23 Thread Andrew Lutomirski
On Tue, Jun 23, 2009 at 9:35 AM, Jerome Glissegli...@freedesktop.org wrote: On Tue, 2009-06-23 at 09:12 -0400, Andy Lutomirski wrote: Andy Lutomirski wrote: Jerome Glisse wrote: smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the

[PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-22 Thread Jerome Glisse
smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the fb buffer into vram by doing so we are loosing vram but fbdev need to be reworked to allow change in framebuffer address. Signed-off-by: Jerome Glisse jgli...@redhat.com ---

Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-22 Thread Andy Lutomirski
Jerome Glisse wrote: smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the fb buffer into vram by doing so we are loosing vram but fbdev need to be reworked to allow change in framebuffer address. I tested this (and the corresponding