From: "H. Peter Anvin" <hpa@zytor.com>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 setup code rewrite in C
Date: Tue, 10 Jul 2007 13:48:11 -0700 [thread overview]
Message-ID: <4693F08B.5060904@zytor.com> (raw)
In-Reply-To: <200707102032.29124.a1426z@gawab.com>
Al Boldi wrote:
> H. Peter Anvin wrote:
>> This patch set replaces the x86 setup code, which is currently all in
>> assembly, with a version written in C, using the ".code16gcc" feature
>> of binutils (which has been present since at least 2001.)
>>
>> The new code is vastly easier to read, and, I hope, debug. It should
>> be noted that I found a fair number of minor bugs while going through
>> this code, and have attempted to correct them.
>
> I have an i810 which supends-to-ram just fine, but when booted over pxe it
> just hangs. Will these patches fix this, and if so, is there an easy
> tar-ball against 2.6.22?
There is absolutely no way to know, other than testing it. There isn't
any real reason to suspect the setup code in your case, but it's worth a
shot, I guess.
There is a git tree on git.kernel.org you can pull, which is current
against 2.6.22.
-hpa
next prev parent reply other threads:[~2007-07-10 20:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 17:32 Al Boldi
2007-07-10 20:48 ` H. Peter Anvin [this message]
2007-07-10 21:07 ` Al Boldi
2007-07-10 21:13 ` H. Peter Anvin
2007-07-10 21:33 ` Randy Dunlap
2007-07-10 21:38 ` H. Peter Anvin
2007-07-11 11:35 ` Chris Smith
2007-07-13 22:33 ` H. Peter Anvin
2007-07-10 21:36 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2007-07-10 2:51 H. Peter Anvin
2007-07-10 4:24 ` Yinghai Lu
2007-07-10 4:39 ` H. Peter Anvin
2007-07-10 5:25 ` Jeff Garzik
2007-07-10 16:24 ` Jeremy Fitzhardinge
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=4693F08B.5060904@zytor.com \
--to=hpa@zytor.com \
--cc=a1426z@gawab.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
Powered by JetHome