From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Clint Thomas" <cthomas@soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux Kernel without bootloader
Date: Tue, 1 Aug 2006 22:17:41 -0600 [thread overview]
Message-ID: <528646bc0608012117i6a5afb37l7e9ee327309aca9b@mail.gmail.com> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA240952915DF66@bluefin.Soneticom.local>
On 7/25/06, Clint Thomas <cthomas@soneticom.com> wrote:
>
>
> Hey guys,
>
> I have gone through the Linuxppc embedded and dev lists for information
> related to what I am trying to do, but was unable to find exactly what i'm
> looking for.
>
> Basically, the system I want linux running on does not require the
> initialization of hardware that U-boot provides, or at least it does not
> need it to boot the linux kernel. I want to load an uncompressed linux
> kernel into memory and start the execution of the kernel, without using any
> kind of bootloader. Is this possible? Or does linux need some kind of
> firmware or other software to tell it to start executing? Thanks for any
> info you might have.
Loading a kernel into memory and starting execution *is* a boot loader. :)
You could use the bootwrapper that is in the kernel source tree
(zImage). If a zImage's entry point is at the execution entry point,
then it will start the Linux kernel correctly. However, it is still a
compressed image.
If you *really* need an uncompressed image, I would start with the
bootwrapper and hack it to work with an non-gzipped kernel image.
However, why do you want to do it this way? You probably won't gain
much in boot time and it will be more difficult to maintain.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2006-08-02 4:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 22:30 Booting Linux Kernel without bootloader Clint Thomas
2006-07-25 23:38 ` bennett78
2006-07-26 6:15 ` Kalle Pokki
2006-07-26 10:45 ` Andrei Konovalov
2006-07-28 8:03 ` David H. Lynch Jr.
2006-07-28 14:02 ` bennett78
2006-08-02 4:17 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 14:06 Milton Miller
2006-08-02 3:49 ` Parav Pandit
2006-08-03 7:48 Milton Miller
2006-08-03 14:34 ` Grant Likely
2006-08-03 16:27 ` Milton Miller
2006-08-03 16:34 ` Grant Likely
2006-08-03 16:49 ` David H. Lynch Jr.
2006-08-03 18:02 Milton Miller
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=528646bc0608012117i6a5afb37l7e9ee327309aca9b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=cthomas@soneticom.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).