From: "Gerb Stralko" <gerb.stralko@gmail.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: 2.6.23: does it supposed to work on an i486?
Date: Fri, 30 Nov 2007 14:20:24 -0500 [thread overview]
Message-ID: <75b57c110711301120r7deff435oc010229b2b84b6a8@mail.gmail.com> (raw)
In-Reply-To: <475059D6.2080900@msgid.tls.msk.ru>
> Well, I applied the patch (in 2.6.23 it's
> arch/i386/boot/pmjump.S,
> not
> arch/x86/boot/pmjump.S,
> but that's minor) - still the same behavior, it still reboots
> instantly right when bootloader gave control to the kernel.
> So it must be something else.. ;)
It should be x86, they merged the i386 and x86_64 code into one arch
called x86. Try it again and see if it works
Thanks,
- Jerry
prev parent reply other threads:[~2007-11-30 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 17:32 2.6.23: does it supposed to work on an i486? Michael Tokarev
2007-11-30 18:08 ` H. Peter Anvin
2007-11-30 18:43 ` Michael Tokarev
2007-11-30 19:08 ` H. Peter Anvin
2007-11-30 19:20 ` Gerb Stralko [this message]
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=75b57c110711301120r7deff435oc010229b2b84b6a8@mail.gmail.com \
--to=gerb.stralko@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).