From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <syrjala@sci.fi>
Subject: Re: FB model basic issues (WAS: radeon, apertures & memory mapping)
Date: Tue, 15 Mar 2005 15:27:46 +0200
Message-ID: <20050315132746.GA14267@sci.fi>
References: <1110696189.5787.100.camel@gaston>
	<1110774523.4003.511.camel@localhost>
	<1110784327.5787.288.camel@gaston>
	<1110817205.4004.527.camel@localhost>
	<1110837171.5863.16.camel@gaston>
	<1110838356.4003.548.camel@localhost>
	<1110839873.5673.41.camel@gaston>
	<1110862777.4044.592.camel@localhost>
	<20050315060138.GA13064@sci.fi> <4236C770.8020101@hispeed.ch>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
In-Reply-To: <4236C770.8020101@hispeed.ch>
List-Id: <fbdev-devel.lists.sourceforge.net>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/listinfo/xorg>,
	<mailto:xorg-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/xorg>
List-Post: <mailto:xorg@lists.freedesktop.org>
List-Help: <mailto:xorg-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/xorg>,
	<mailto:xorg-request@lists.freedesktop.org?subject=subscribe>
Sender: xorg-bounces@lists.freedesktop.org
Errors-To: xorg-bounces@lists.freedesktop.org
Content-Type: text/plain; charset="iso-8859-1"
To: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
Cc: Michel =?iso-8859-1?Q?D=E4nzer?= <michel@daenzer.net>, Jon Smirl <jonsmirl@yahoo.com>, Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>, dri-devel@lists.sourceforge.net, xorg@lists.freedesktop.org

On Tue, Mar 15, 2005 at 12:30:56PM +0100, Roland Scheidegger wrote:
> Ville Syrj=E4l=E4 wrote:
>  > I think that making the assumption that all memory is preserved when=
=20
> the
> >memory layout (virtual resolution and depth) doesn't change is perfect=
ly=20
> >valid too. That would allow X to do it's Ctrl-Alt-+ and - things witho=
ut=20
> >repainting the whole screen.
> I'm not sure I agree here, as it's not always true. For instance, the=20
> radeon has some restrictions whether it can use tiling or not with a=20
> certain mode (interlace/double scan) thus you need to redraw everything=
=20
> anyway

I didn't know about that. My first thought would be to disallow such mode=
s=20
but knowing that X lacks a proper fullscreen API that might not be a=20
realistic option.

> (which is exactly why I implemented a driver workaround to=20
> repaint everything when that happens - in fact the workaround also gets=
=20
> rid of the offscreen contents, which is not necessary, but was much=20
> easier to implement, since I couldn't find an easy way to "invalidate=20
> the framebuffer"). What's the big deal with repainting everything? It's=
=20
> not like you would do 100 mode changes per second so it would be=20
> performance-critical...

I don't really have a big deal with invalidating the visible part of the=20
memory.

--=20
Ville Syrj=E4l=E4
syrjala@sci.fi
http://www.sci.fi/~syrjala/