Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Grub2 and Memtest86+
Date: Thu, 29 Jan 2015 16:50:54 +0100	[thread overview]
Message-ID: <20150129165054.5b72b7fe@free-electrons.com> (raw)
In-Reply-To: <54CA4C59.3010107@ou.edu>

Dear Steve Kenton,

On Thu, 29 Jan 2015 09:06:01 -0600, Steve Kenton wrote:
> I've been tinkering with adding memtest86+ V4.20 to the
> grub2 menu for my x86 target. It's straight forward.
> 
> The questions, is there interest in this and how to
> do this only for x86 targets. I've not dug into how
> the boot loaders are handled, yet, but it's apparently
> different from regular packages. Is there anyone
> who keeps track on the grub2 boot loader in buildroot?

I'm not sure I can say I "keep track of grub2", but I did add the
package last year.

> Modify ~boot/grub2/grub.cfg to add the memtest entry
> and download the memtest86+ source tarball and then
> copy/rename the shipped precomp.bin file file to
> /boot/memtest86+.bin (It's a bootable 486 binary)
> 
> set default="0"
> set timeout="5"
> 
> menuentry "Buildroot" {
> 	linux /boot/bzImage root=/dev/sda1 console=tty1 quiet splash=silent
> }
> 
> menuentry "Memtest86+" {
> 	linux16 /boot/memtest86+.bin
> }

What I would suggest is to add a package for memtest86 in Buildroot,
have it install the appropriate binary in /boot, and in its Config.in
help text, indicate how to add it to the Grub menu.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-01-29 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:06 [Buildroot] Grub2 and Memtest86+ Steve Kenton
2015-01-29 15:50 ` Thomas Petazzoni [this message]
2015-02-03  5:11   ` Steve Kenton
2015-02-03  5:16     ` Steve Kenton

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=20150129165054.5b72b7fe@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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