From: Milton Miller <miltonm@bga•com>
To: "Grant Likely" <grant.likely@secretlab•ca>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Booting Linux Kernel without bootloader
Date: Thu, 3 Aug 2006 11:27:51 -0500 [thread overview]
Message-ID: <b4c0f7394350325fbdbfe66afb1b4ec8@bga.com> (raw)
In-Reply-To: <528646bc0608030734j163acdd0gf37f19ece6f18c09@mail.gmail.com>
On Aug 3, 2006, at 9:34 AM, Grant Likely wrote:
> On 8/3/06, Milton Miller <miltonm@bga•com> wrote:
>> On Tue Aug 1 2006 11:17:41 PM CDT, Grant Likely wrote:
>> > On 7/25/06, Clint Thomas <cthomas@soneticom•com> wrote:
>> > >
>> > > 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.
>>
>> > 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.
>> >
>>
>> The boot wrapper is a reference implementation, not a required piece
>> of the
>> boot sequence.
...
>
> I agree. However, the original post sounded to me like he was looking
> for a canned solution. I know zImage isn't exactly what he asked for
> because it is a compressed image, but it does achieve the *effect* he
> asked for.
Actually the existing zImage will not do that, it requires a client
interface to allocate memory, etc. There are alternates available
but they are not yet merged.
> I am curious as to the source of his requirements. ie. what is
> loading the kernel into ram? Where is it coming from?
That would be useful to help suggest alternatives.
> I've got a similar situation on my Virtex-4 platform. The FPGA takes
> care of all device initialization. However, the kernel is loaded of a
> CF card via a *slow* JTAG interface. Loading an uncompressed image is
> more time consuming than loading a compressed image and uncompressing
> it in software.
This is often the case. However, if its loaded via some kind of DMA
access
from a higher powered cpu then loading the uncompressed kernel could be
the fastest way. Since we don't know we can only mention things to
consider as we state what can be done.
milton
next prev parent reply other threads:[~2006-08-03 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:48 Booting Linux Kernel without bootloader Milton Miller
2006-08-03 14:34 ` Grant Likely
2006-08-03 16:27 ` Milton Miller [this message]
2006-08-03 16:34 ` Grant Likely
2006-08-03 16:49 ` David H. Lynch Jr.
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 18:02 Milton Miller
2006-07-26 14:06 Milton Miller
2006-08-02 3:49 ` Parav Pandit
2006-07-25 22:30 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
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=b4c0f7394350325fbdbfe66afb1b4ec8@bga.com \
--to=miltonm@bga$(echo .)com \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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