From: "Kalle Pokki" <kalle.pokki@iki.fi>
To: "Clint Thomas" <cthomas@soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux Kernel without bootloader
Date: Wed, 26 Jul 2006 09:15:48 +0300 [thread overview]
Message-ID: <a425f86c0607252315l43c2d64w8b1d10331dd1b9d@mail.gmail.com> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA240952915DF66@bluefin.Soneticom.local>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
On 7/26/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.
>
Once the hardware is initialised, it is pretty straightforward to boot the
linux kernel. All you have to have is the kernel at address zero, struct
bd_info filled in some place in memory, kernel command line stored in
memory, and registers r3 ... r7 containing pointers to these.
For reference, look
1) include/asm-ppc/ppcboot.h for example struct bd_info
2) arch/ppc/syslib/m8260_setup.c for the registers
If you have some custom hardware, you need to create (basically empty)
platform code, since the existing ones would try to touch some board control
registers you don't have.
But remember, you need to initialise the memory controller and all sorts of
things yourself somehow - with a JTAG debugger or a custom boot loader.
[-- Attachment #2: Type: text/html, Size: 1682 bytes --]
next prev parent reply other threads:[~2006-07-26 6:15 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 [this message]
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
-- 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=a425f86c0607252315l43c2d64w8b1d10331dd1b9d@mail.gmail.com \
--to=kalle.pokki@iki.fi \
--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).