mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 embedded - Problem getting past 'move compressed kernel  before decompression'
Date: Mon, 22 Feb 2010 09:51:09 +1100	[thread overview]
Message-ID: <d66caabb1002211451s5a68565fue6096e17b99402f7@mail.gmail.com> (raw)
In-Reply-To: <4B80CA55.3040402@zytor.com>

On Sun, Feb 21, 2010 at 4:53 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 02/20/2010 09:45 PM, H. Peter Anvin wrote:
>
> Make that:
>
>        asm volatile(
>                "movl   %2, %%ds\n" \
>                "movl   %2, %%es\n" \
>                "movl   %2, %%fs\n" \
>                "movl   %2, %%gs\n" \
>                "movl   %2, %%ss\n" \
>                "xorl   %ebp, %ebp\n" \
>                "xorl   %ebx, %ebx\n" \
>                "ljmpl  $0x10,$0x100000"
>         : : "S" (&boot_params), "D" (0), "r" (0x18));
>

Thanks Peter - I gave that a try but no luck. I am in the process of
writing some routines which will dump the contents of the registers
upon entering startup_32 and the relocation jump address prior to
the jump.

My assembler is a bit rusty, so it is taking a bit of time

What other information should I dump?

Regards,

Graeme

  parent reply	other threads:[~2010-02-21 22:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21  2:03 Graeme Russ
2010-02-21  5:45 ` H. Peter Anvin
2010-02-21  5:53   ` H. Peter Anvin
2010-02-21  9:11     ` Yuhong Bao
2010-02-21 22:51     ` Graeme Russ [this message]
2010-02-27  5:06       ` Graeme Russ
2010-03-01 11:56         ` Graeme Russ
2010-03-01 16:46           ` H. Peter Anvin
2010-03-01 19:41             ` Graeme Russ
2010-03-01 19:43               ` H. Peter Anvin
2010-03-01 19:59                 ` Graeme Russ
2010-03-05 13:02                   ` Graeme Russ

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=d66caabb1002211451s5a68565fue6096e17b99402f7@mail.gmail.com \
    --to=graeme.russ@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

all inboxes | Powered by JetHome®