Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966381AbXEVQQW (ORCPT ); Tue, 22 May 2007 12:16:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757473AbXEVQQG (ORCPT ); Tue, 22 May 2007 12:16:06 -0400 Received: from outbound-mail-37.bluehost.com ([69.89.20.191]:54936 "HELO outbound-mail-37.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757228AbXEVQQF (ORCPT ); Tue, 22 May 2007 12:16:05 -0400 From: Jesse Barnes To: "Jon Smirl" Subject: Re: [RFC] enhancing the kernel's graphics subsystem Date: Tue, 22 May 2007 09:15:50 -0700 User-Agent: KMail/1.9.6 Cc: "Alan Cox" , "Jeff Garzik" , "Jesse Barnes" , linux-kernel@vger.kernel.org, "Antonino A. Daplas" References: <200705171423.46748.jesse.barnes@intel.com> <200705220846.53664.jbarnes@virtuousgeek.org> <9e4733910705220902y151d1922s7e478de041062aa4@mail.gmail.com> In-Reply-To: <9e4733910705220902y151d1922s7e478de041062aa4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705220915.50238.jbarnes@virtuousgeek.org> X-Identified-User: {642:box128.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 76.102.120.196 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1242 Lines: 25 On Tuesday, May 22, 2007, Jon Smirl wrote: > I've talked to an ATI engineer about VBIOS initialization. The chips > may have different steppings. They flash the right VBIOS that matches > the chip into the ROM on the card. Given all the various steppings > this is the only sane way to initialize the hardware. I don't believe > generic initialization code that can handle all of the various > steppings exists for any hardware. I think you must have misunderstood. Last time I worked on ATI, there was a single ROM image that supported several (maybe even all) of their addin cards. There's nothing magical about them... But that's beside the point. They may have hardcoded information about how a particular board is wired up--it's ok to use that (makes the DAC discovery much easier). We just want to avoid relying on the VBIOS for DAC setup and output probing, since we'll need to do that ourselves for suspend resume and to fully support various multihead configurations. Jesse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/