From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 6CC36DE1F2 for ; Mon, 29 Jan 2007 08:39:35 +1100 (EST) Subject: Re: [PATCH 1/9] ps3: AV Settings Driver From: Benjamin Herrenschmidt To: Geert Uytterhoeven In-Reply-To: References: <200701260513.24010.arnd@arndb.de> Content-Type: text/plain Date: Mon, 29 Jan 2007 08:37:00 +1100 Message-Id: <1170020220.26655.35.camel@localhost.localdomain> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, Paul Mackerras , James Simmons , Linux Frame Buffer Device Development , Arnd Bergmann List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > Analog YUV (Component and composite/S-video) video timings are dictated by > broadcast standards. > > The last 3 resolutions are supported through the HDMI output only. Hence if > your TV has HDMI or DVI-D (_with_ HDCP, else you get a black screen) inputs, > you can use 1280x768. > > If your TV doesn't have HDMI or DVI-D with HDCP, but it has component inputs, > you can use analog 720p. Please, still try to get the HV folks to add more VESA modes for use by linux :-) 1600x1200 would be nice for example, as would 1440x900 (lots of cheap flat panels do that nowadays.... they can demote to 720p which is good enough for games, but for linux, we want native resolution). > Reducing these values may cause video noise to be seen when changing video > modes. So the whole thing should be turned into a state machine on a timer or a kthread no ? So at least, whatever issues the mode change can start drawing while the kernel waits to actually enable the outputs... Ben.