linux-kernel - Re: [RFC] enhancing the kernel's graphics subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 May 2007 09:15:50 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	"Jon Smirl" <jonsmirl@...il.com>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Jeff Garzik" <jeff@...zik.org>,
	"Jesse Barnes" <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org,
	"Antonino A. Daplas" <adaplas@...il.com>
Subject: Re: [RFC] enhancing the kernel's graphics subsystem

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/