From: ebiederm@xmission.com (Eric W. Biederman)
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux as Bootloader
Date: Tue, 06 Sep 2011 11:18:05 -0700 [thread overview]
Message-ID: <m11uvto7qa.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAH9NwWfGA7jLWDZcN=DfGN5H2g=dt6U8SBxAX_wJAk6MKKfZAA@mail.gmail.com> (Christian Gmeiner's message of "Mon, 5 Sep 2011 10:24:13 +0200")
Christian Gmeiner <christian.gmeiner@gmail.com> writes:
> Hi all,
>
> I am using the linux kernel in combination with busybox and a separate
> bootloader app to
> startup a x86 based embedded device. As the used BIOS does only do
> basic hw init, we
> used Linux as a bootloader. Our custom BIOS starts the bootloader
> kernel located in BIOS
> flash. If the kernel and userland is ready our boot application
> searches for the productive kernel
> and executes it via kexec.
>
> Now I run in some troubles as I need to be able to boot a MSDOS
> application stored on
> an usb stick. I have tried grub4linux but I am not able to boot from
> the usb stick - even I
> see the grub command line.
>
> Are there some creative/working solutions for my problem?
There has been some success using a modified bochs bios on real hardware
in the context of coreboot. That should be loadable from linux and
usable on your setup. Avoiding the DOS requirement is probably a more
certain path, getting DOS going is probably more fun.
Eric
next prev parent reply other threads:[~2011-09-06 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 8:24 Linux as Bootloader Christian Gmeiner
2011-09-05 12:33 ` el es
2011-09-06 18:18 ` Eric W. Biederman [this message]
2011-09-11 21:18 ` Geoff Levand
2011-09-16 11:02 ` Christian Gmeiner
2011-09-19 2:22 ` Geoff Levand
2011-10-21 23:07 ` Geoff Levand
2011-09-12 6:20 ` James Courtier-Dutton
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=m11uvto7qa.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=christian.gmeiner@gmail.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