From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michel =?ISO-8859-1?Q?D=E4nzer?= Subject: Re: Some questions Date: 12 Mar 2003 02:29:13 +0100 Sender: linux-fbdev-devel-admin@lists.sourceforge.net Message-ID: <1047432552.1348.94.camel@thor> References: <1047407816 .1013.182.camel@localhost.localdomain> <3E6E4D9A.7060003@winischhofer.net> <1047419056.1100.26.camel@localhost.localdomain> <3E6E61C6.2000503@winischhofer.net> <1047422558.1128.120.camel@localhost.localdomain> <1047427628.6814.79.camel@thor> <1047430840.1186.233.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: Received: from netline-be1.netline.ch ([195.141.226.32]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18sv3W-0003Iw-00 for ; Tue, 11 Mar 2003 17:29:18 -0800 In-Reply-To: <1047430840.1186.233.camel@localhost.localdomain> Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="iso-8859-1" To: Antonino Daplas Cc: Thomas Winischhofer , James Simmons , Geert Uytterhoeven , Linux Fbdev development list On Mit, 2003-03-12 at 02:02, Antonino Daplas wrote: > On Wed, 2003-03-12 at 08:07, Michel D=E4nzer wrote: > > On Die, 2003-03-11 at 23:51, Antonino Daplas wrote: > > > On Wed, 2003-03-12 at 06:23, Thomas Winischhofer wrote: > > > > >=20 > > > > > I actually prefer #3, and I already have working code for this. = We can > > > > > also make this driver switchable (ie, drivers that are not affect= ed by X > > > > > can disable this, and only drivers that are affected such as the = riva, > > > > > aty, radeon, etc can turn this on). > > > >=20 > > > > What exactly is a "trusted" console? > > >=20 > > > By default, the pid of each vt is -1. When X loads, it installs its = own > > > VT (ie vt7), which in that case the pid of that particular vt =3D=3D = X's > > > pid. We can check this pid, and if switching from a vt with pid =3D= =3D -1, > > > we can safely assume that the hardware state is still sane, and if no= t, > > > assume the hardware state is undefined. > >=20 > > Can you also detect when the app has opened the framebuffer device, and > > assume it's playing nice when it has? (for Option "UseFBDev") > >=20 >=20 > X using fbdev will also have the same limitation. I have implemented > something like this before. For each fb_open, the current->pid can be > saved into a "white list" and removed for each fb_close. fbcon can then > compare this to the pid of the vt it's switching from. I see, makes sense. > This is becoming to sound very ugly though. I guess, the best way is to > really support Option "UseFBDev", or at least have the user decide if > he/she wants to have the hardware refreshed. =20 I'm afraid I don't understand what you're saying here. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open!=20 Get cracking and register here for some mind boggling fun and=20 the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en