linux-kernel - arch/i386/boot rewrite, and all the hard-coded video cards

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-next>] [day] [month] [year] [list]

Message-ID: <463698D5.20102@zytor.com>
Date:	Mon, 30 Apr 2007 18:33:09 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andi Kleen <ak@...e.de>, Jeff Garzik <jeff@...zik.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: arch/i386/boot rewrite, and all the hard-coded video cards

Hi all,

I'm rewriting the i386 setup code in C, instead of assembly, and before
I spend a very large amount of time translating all the various
card-specific probes, I want to ask the following question...

Does *anyone* care about these anymore?

All of these are specific to cards from a very long time ago.  I am
currently planning to retain the VESA-related code, and the standard
video modes, but I'd like to avoid the card-specific stuff, especially
since I have absolutely zero ability to test any of testing them (with
the possible sole exception of the cirrus5 code, which is emulated by qemu.)

Please holler if you care...

	-hpa

-
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/