public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86 setup rewrite tree ready for flamage^W review
Date: Sat, 12 May 2007 21:35:15 -0300	[thread overview]
Message-ID: <46465D43.3060200@gmail.com> (raw)
In-Reply-To: <46450910.8080503@zytor.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

H. Peter Anvin wrote:
> Kevin Winchester wrote:
>> Not sure if you were looking for testing, but I fuzzed it to apply to
>> 2.6.21-git and gave it a spin.  Worked just like a normal boot (which I
>> assume was the point).
> 
> That would be the point, yes :)  Looking for breakage in video mode
> detection, memory detection, and APM are probably the trickiest areas.
> 
> 	-hpa
> 

Video mode detection (including "scan") seemed to work just the same as before.
 As for memory detection, my 512M x86-64 UP system is probably not what you had
in mind, and I don't really know what goes on for APM or how to test it.

As well, I've been looking through the actual code, and even with my very
limited experience with x86 assembler and operating systems, I now at least have
an idea of what is going on.  So switching to C for as much of the code as
possible seems like the right idea if you want to make it easier for new people
to get involved in that area of the kernel.

Kevin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGRl1CKPGFQbiQ3tQRAuEcAJ93zlfNzB7YipLHgvkQP3Jrtjh0EwCfSRQ5
9emaZMVvJsuXMs1ifO4KWkY=
=G4zx
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-05-13  0:36 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
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 [this message]
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=46465D43.3060200@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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