mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: Booting Linux bzImage on x86_64
Date: Fri, 30 Oct 2015 08:47:53 +0100	[thread overview]
Message-ID: <20151030074753.GA32176@pengutronix.de> (raw)
In-Reply-To: <trinity-0d310d91-ea1a-4a70-b46d-11b3b53ff135-1446065406666@3capp-gmx-bs58>

Hi,

On Wed, Oct 28, 2015 at 09:50:06PM +0100, Viktor Stark wrote:
> I recently discovered barebox and I am trying to boot a Linux bzImage on an
> x86_64 embedded platform.
> 
> Some background: My project involves an x86_64 embedded device for which I am
> building a bzImage and a root filesystem with buildroot. The idea is to have
> multiple combinations of these in order to serve different use cases, but
> also for fallback situations.
> 
> I went down both possible ways on x86, but cannot really find a way to boot a bzImage.
> 
> Both configurations are tested under QEMU with barebox 2015.10.0.
> 
> 1. EFI - I have a working barebox.efi living inside an EF00 partition. The
> issue I am having is that I cannot really find any pointers as to how to boot
> a bzImage from these. I have found some earlier posts on the list indicating
> that it is not possible to boot a bzImage from EFI, but also a G+ post saying
> that it is possible.

I'm running my Laptop with Barebox on EFI, so it's certainly possible.
Without any error messages I can only guess what the problem might be.
Have you enabled CONFIG_EFI_STUB in your kernel config? This is necessary
for barebox to boot your kernel.

> 2. Non-EFI - I have compiled barebox with the attached config file, but it
> seems to triple fault according to qemu. AFAICT (zero asm knowledge here), it
> seems to be in pmjump.S.
> Triple fault

This is _really_ old code. Nobody has tested this in a long time. It's most
likely broken in many ways. Don't use it unless you're interested in
barebox development and want to fix it :-).

Regards,
Michael


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-10-30  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 20:50 Viktor Stark
2015-10-30  7:47 ` Michael Olbrich [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=20151030074753.GA32176@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=barebox@lists.infradead.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