Re: deprecating fix->mmio_start and smem_start

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

On Tue, 2008-04-22 at 21:41 +0300, Ville Syrjälä wrote:
> DirectFB uses both.
> 
> smem_start is used to get the physical address of the frambuffer for v4l
> capture purposes at least. It's also used by several of the hw specific
> gfxdrivers for various reasons. For example the matrox driver uses it to
> figure out the offset from the beginning of the video memory to the
> portion allocated for CRTC2 by matroxfb. This only applies when matroxfb
> is left in control of CRTC2. I doubt may people use DirectFB this way
> since DirectFB can drive CRTC2+TVout itself and manage the full memory
> for both heads. But the support is still there in the code FWIW. I'm
> not actually sure what the other gfxdrivers use it for but I see several
> references when I grep for it.
> 
> mmio_start is used to figure out where the registers actually lie within
> the mmapped MMIO area. atyfb is the only fb driver that I know to need
> this. The problem is that with new chips the aux register aperture is
> used and the registers are at the beginning of that aperture but when the
> aux register aperture is not used the registers occupy the last 2K
> of the framebuffer. That means an offset of 2K on typical systems.

So DirectFB can be fixed to use the "new" structure with 64 bits offsets
if we define such a thing right ? (with new ioctl's to access it).

Cheers,
Ben.




-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel