mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <ahmad@a3f.at>
To: jbe@pengutronix.de, barebox@lists.infradead.org
Cc: uol@pengutronix.de, Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH 0/1] x86: retire legacy (non-efi) boot ?
Date: Tue,  9 Mar 2021 23:52:22 +0100	[thread overview]
Message-ID: <20210309225223.1687415-1-ahmad@a3f.at> (raw)

barebox for legacy BIOS boot was reported broken on IRC nearly a year
ago. With the link error fixed, I can get some early debug output, but
barebox hangs early after when running under qemu-kvm:

  $ ./scripts/setupmbr/setupmbr -s 32 -m build/barebox-flash-image -d img && \
	kvm -drive format=raw,file=img -serial stdio -m 4G -cpu host -smp 2
  
  SeaBIOS (version 1.14.0-2)
  
  iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+07F8F4C0+07ECF4C0 CA00
  
  Booting from Hard Disk...
  BAREBOX JMP

With OSELAS.Toolchain-2013.12.3, but without the patch included here,
I can get a shell if I shrink down barebox, but no luck getting this
to work with a recent toolchain. There also seems to be some transient
issue that's triggered by the barebox size.

I'd assume that because no one stepped up to fix this so far, no one
cares and we could drop legacy BIOS boot support altogether.
New platforms should be using EFI anyway. Thoughts?

Cheers,
Ahmad Fatoum (1):
  x86: lib: fix link error for legacy (non-EFI) boot

 arch/x86/lib/barebox.lds.S | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.30.0


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


             reply	other threads:[~2021-03-09 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 22:52 Ahmad Fatoum [this message]
2021-03-09 22:52 ` [PATCH 1/1] x86: lib: fix link error for legacy (non-EFI) boot Ahmad Fatoum

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=20210309225223.1687415-1-ahmad@a3f.at \
    --to=ahmad@a3f.at \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.de \
    --cc=uol@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox