linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bennett78 <bennett78@digis.net>
To: Clint Thomas <cthomas@Soneticom.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Booting Linux Kernel without bootloader
Date: Tue, 25 Jul 2006 17:38:40 -0600	[thread overview]
Message-ID: <44C6AB80.9040000@digis.net> (raw)
In-Reply-To: <3C02138692C13C4BB675FE7EA240952915DF66@bluefin.Soneticom.local>

[-- Attachment #1: Type: text/plain, Size: 2831 bytes --]

Clint Thomas 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.

You seem to be looking for a striped down U-boot functionality:
    o copy flash to ram and run code
but to do this:
    o processor registers need to be initilized
    o caches need to be flushed
    o interrupts need to be disabled
    o C environment (stack) needs to be setup
U-boot is fairly small compared to a x86 BIOS which has to find
multiple boot device choices, yet supports multiple architectures.

I'm using a BDI2000 to load/debug u-boot running in SDRAM
for a new PPC hardware design.  U-boot is probably easier to
debug than the kernel!
U-boot has other features that help with initial H/W turnon:
    o it's a debug/monitor
          o ram test
          o ram/register read/modify
    o u-boot environment
          o IP address, mac address
          o Linux boot options - NFS verses flash
          o Ethernet/NFS option using a server enables:
             o debugging kernel changes
             o debugging kernel driver modules
             o quick change of application processes
             o cross compile target code on server to local target
             o telnet to embedded H/W
    o knows how to flash partitions
          o u-boot (/dev/mtd0) (well I use the BDI to flash here)
          o can flash kernel (/dev/mtd1)
          o can flash root fs (/dev/mtd2)
          o can flash config data (/dev/mtd3)
          o this partitioning will help with future F/W updates
          o kind of required if your flash is soldered to the board
          o to read/write flash requires u-boot to relocate itself to ram

>  
> Clinton Thomas
> cthomas@soneticom.com
>  _______________________________________________
>
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
Frank Bennett

*/Technical Contractor/*

/Triad Systems Engineering
200 West Mountain Avenue, Suite 103C
Ft. Collins, CO 80521
/http://www.traidsyseng.com <http://www.triadsyseng.com>
frank.bennett@triadsyseng.com <mailto:frank.bennett@triadsyseng.com>/
/
"I think there's a world market for about five computers."
        -- attr. Thomas J. Watson (Chairman of the Board, IBM), 1943




[-- Attachment #2: Type: text/html, Size: 5234 bytes --]

  reply	other threads:[~2006-07-25 23:57 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 [this message]
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
  -- 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=44C6AB80.9040000@digis.net \
    --to=bennett78@digis.net \
    --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).