From: Rossier Daniel <Daniel.Rossier@heig-vd.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot & x86 & coreboot
Date: Wed, 17 Jul 2013 13:35:04 +0000 [thread overview]
Message-ID: <5f6ee1c8018b478cbc3be0fc6310df65@EINTMBXC.einet.ad.eivd.ch> (raw)
In-Reply-To: <2c8e1bd91a4c4e27b71ca641e7c367ac@EINTMBXC.einet.ad.eivd.ch>
Basically, should the coreboot-x86_config replace the use of coreboot ? Or, is coreboot still necessary?
> -----Original Message-----
> From: u-boot-bounces at lists.denx.de [mailto:u-boot-
> bounces at lists.denx.de] On Behalf Of Rossier Daniel
> Sent: mercredi 17 juillet 2013 10:29
> To: u-boot at lists.denx.de
> Subject: [U-Boot] U-boot & x86 & coreboot
>
> Hi,
>
> I would like to run U-boot on x86 emulated QEMU-based environment. I
> found some info regarding coreboot + U-boot integration, using U-boot as
> payload, etc. but I was unable to start U-boot.
> I'm using the 32-bits i686-pc-linux-gnu toolchain and I successfully cross-
> compiled coreboot and started it on qemu-system-i386.
> I also configured coreboot to use u-boot (ELF) as payload, but coreboot
> performs a reset when U-boot should show up after loading.
> Where could I have some information regarding that?
> Furthermore, I'm unable to debug anything remotely with gdb; gdb cannot
> disassemble once connected via "target remote localhost:1234".
>
> Any hints welcome.
> Thanks so much.
>
> Cheers
> Daniel
next prev parent reply other threads:[~2013-07-17 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 8:29 [U-Boot] U-boot & x86 & coreboot Rossier Daniel
2013-07-17 13:35 ` Rossier Daniel [this message]
2013-07-17 15:43 ` Simon Glass
2013-07-17 15:42 ` Simon Glass
2013-07-17 21:20 ` [U-Boot] FW: " Rossier Daniel
2013-07-17 21:20 ` Rossier Daniel
2013-07-17 21:57 ` Simon Glass
[not found] ` <4517dc2e643743ebac2f9c8b61aafdfa@EINTMBXC.einet.ad.eivd.ch>
[not found] ` <CAPnjgZ3bUn-nsdfvo9=WZhfi592L7jhu1epuwh5AM3g4EaOBDA@mail.gmail.com>
2013-07-19 7:49 ` [U-Boot] " Rossier Daniel
2013-07-19 16:14 ` Simon Glass
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=5f6ee1c8018b478cbc3be0fc6310df65@EINTMBXC.einet.ad.eivd.ch \
--to=daniel.rossier@heig-vd.ch \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.