public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Vlad <vladc6@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: arch/i386/boot rewrite, and all the hard-coded video cards
Date: Wed, 02 May 2007 01:22:07 +0200	[thread overview]
Message-ID: <4637CB9F.9010408@gmail.com> (raw)
In-Reply-To: <741290.4122.qm@web54405.mail.yahoo.com>

On 05/02/2007 12:41 AM, Vlad wrote:

> H. Peter Anvin wrote:

>> 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?
> 
> Yes, booting Linux on old i386/i486 hardware is still very useful for
> forensic purposes and recovering important data. I've personally had
> to do this many times, and I'm sure others have as well.
> 
> Booting is such a critical process that a user would be completely
> lost as to why it fails, especially if they can't see any output on
> the screen. I think it would be a shame to prevent Linux from running
> on these machines.

He wasn't asking about doing away with all video output on 386/486s, but 
with special Super VGA adapter specific modes. You'd have normal VGA 
available as always, and VESA if the videocard supports it (which all cards 
that _can_ do more than 80x25 do).

Rene.


  reply	other threads:[~2007-05-01 23:24 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 22:41 arch/i386/boot rewrite, and all the hard-coded video cards Vlad
2007-05-01 23:22 ` Rene Herman [this message]
2007-05-02  1:10   ` Vlad
2007-05-02 18:25 ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-05-01  1:33 H. Peter Anvin
2007-05-01  1:40 ` Jeff Garzik
2007-05-01  1:42   ` H. Peter Anvin
2007-05-02  7:46     ` Martin Mares
2007-05-02  9:22       ` Andi Kleen
2007-05-02 20:49         ` H. Peter Anvin
2007-05-03  2:15         ` H. Peter Anvin
2007-05-02 19:05       ` Lennart Sorensen
2007-05-01  1:51 ` Dave Jones
2007-05-01  2:17   ` H. Peter Anvin
2007-05-01  2:34     ` Eric W. Biederman
2007-05-01  3:46       ` Andi Kleen
2007-05-01  2:54         ` H. Peter Anvin
2007-05-01  4:29           ` Andi Kleen
2007-05-01  3:38             ` H. Peter Anvin
2007-05-01  3:06         ` Eric W. Biederman
2007-05-01  3:21           ` H. Peter Anvin
2007-05-01  3:41             ` Eric W. Biederman
2007-05-01  3:44               ` H. Peter Anvin
2007-05-01  2:43 ` Linus Torvalds
2007-05-01  2:59   ` Dave Jones
2007-05-01 20:32   ` Rene Herman
2007-05-01 21:01     ` Rene Herman
2007-05-01 21:41     ` Linus Torvalds
2007-05-01 21:52       ` H. Peter Anvin
2007-06-14  4:51         ` Oleg Verych
2007-06-14  5:11           ` H. Peter Anvin
2007-06-14  7:18             ` Oleg Verych
2007-05-01 22:59       ` Rene Herman
2007-05-01 23:18       ` Antonino A. Daplas
2007-05-02 18:22       ` Jan Engelhardt
2007-05-02 20:59         ` H. Peter Anvin
2007-05-02 21:07           ` Rene Herman
2007-05-02 21:15             ` H. Peter Anvin
2007-05-02 21:20               ` Rene Herman
2007-05-02 21:25                 ` H. Peter Anvin
2007-05-02 21:39                   ` Rene Herman
2007-05-02 22:11                     ` H. Peter Anvin
2007-05-02 22:49                       ` Rene Herman
2007-05-02 22:59                         ` H. Peter Anvin
2007-05-02 23:18                           ` Rene Herman
2007-05-03  2:09                             ` H. Peter Anvin
2007-05-01  3:56 ` WANG Cong

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=4637CB9F.9010408@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vladc6@yahoo.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