From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Mares <mj@ucw.cz>
Cc: Alexander van Heukelum <heukelum@fastmail.fm>,
"Antonino A. Daplas" <adaplas@gmail.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>, Matt Domsch <Matt_Domsch@dell.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@in.ibm.com>,
James Bottomley <James.Bottomley@HansenPar.ms.mff.cuni.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander van Heukelum <heukelum@mailshack.com>
Subject: Re: x86 setup rewrite tree ready for flamage^W review
Date: Thu, 10 May 2007 17:55:58 -0700 [thread overview]
Message-ID: <4643BF1E.50200@zytor.com> (raw)
In-Reply-To: <mj+md-20070510.183659.21639.nikam@ucw.cz>
Martin Mares wrote:
> Hello!
>
>> As far as I could tell, "scan" simply caused the nonstandard video
>> driver scan modules (unsafe probes) to be invoked. Since those modules
>> are no longer present, there appeared to be no need for them. The VGA
>> and VESA probes are safe.
>
> "scan" is still useful, because it is able to find BIOS video modes with
> non-standard numbers (they are still sometimes found on recent cards).
Well, I don't have a card which does anything like that, but I did just
implement the "scan" functionality and pushed it out. If anyone cares
about that functionality it would be good if they could test it out and
report if it works.
-hpa
next prev parent reply other threads:[~2007-05-11 0:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:15 x86 setup rewrite tree ready for flamage^W review H. Peter Anvin
2007-05-09 6:51 ` Sam Ravnborg
2007-05-09 7:02 ` H. Peter Anvin
2007-05-09 8:11 ` Sam Ravnborg
2007-05-10 14:10 ` Alexander van Heukelum
2007-05-10 18:08 ` H. Peter Anvin
2007-05-10 18:38 ` Martin Mares
2007-05-11 0:55 ` H. Peter Anvin [this message]
2007-05-10 22:04 ` Alexander van Heukelum
2007-05-10 22:48 ` H. Peter Anvin
2007-05-12 12:21 ` Alexander van Heukelum
2007-05-12 14:20 ` Eric W. Biederman
2007-05-12 18:09 ` H. Peter Anvin
2007-05-12 18:35 ` Eric W. Biederman
2007-05-12 18:59 ` H. Peter Anvin
2007-05-12 22:04 ` Eric W. Biederman
2007-05-12 22:08 ` H. Peter Anvin
2007-05-11 4:37 ` Vivek Goyal
2007-05-11 23:58 ` Kevin Winchester
2007-05-12 0:23 ` H. Peter Anvin
2007-05-13 0:35 ` Kevin Winchester
2007-05-15 20:45 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4643BF1E.50200@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPar.ms.mff.cuni.cz \
--cc=Matt_Domsch@dell.com \
--cc=adaplas@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=heukelum@fastmail.fm \
--cc=heukelum@mailshack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=vgoyal@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox