From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ch-zrh-72-201.trenka.ch ([93.188.72.201]:42958 "EHLO mail.o2s.ch" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1753139Ab0IPRHm (ORCPT ); Thu, 16 Sep 2010 13:07:42 -0400 Subject: Re: HTC Dream From: David =?iso-8859-1?q?Lanzend=F6rfer?= Date: Thu, 16 Sep 2010 19:07:42 +0200 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1460171.AXWImhvBm8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201009161907.46942.david.lanzendoerfer@o2s.ch> Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: linux-arm-msm@vger.kernel.org --nextPart1460171.AXWImhvBm8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit >What's this "refresh thread" ? Where did it come from? Commit message[1] says: msmfb: added refresh thread to support X's fbdev (disabled by default) rebased patch from Martijn Stolk from the original commit message: "As the touchscreen is now interrupt based instead of polling, the screen does not get updated in a regular fashion. The refresh thread has been added to compensate for this. As it's not a very nice solution,it is disabled by default and can be enabled at compile-time by setting CONFIG_MSM_FB_REFRESH. Note that this refresh thread is not neccesary for Android. [1] http://gitorious.org/htc-msm-2-6-32/leviathan-incoming/commit/e25e2109b02f84a361ae037f8576af942aeb39a6 --nextPart1460171.AXWImhvBm8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkySTuIACgkQAeZw77btGjpbQwCbBop/FfLD8yx6lf4pPDr7qhyF yfsAn1rbNdlGa1TsvJIQEU279N4mI1MI =89Vu -----END PGP SIGNATURE----- --nextPart1460171.AXWImhvBm8--