linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: atul.sabharwal@exgate.tek.com
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: kernel startup
Date: Fri, 10 Feb 2006 17:46:10 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0602101745150.31619-100000@gate.crashing.org> (raw)
In-Reply-To: <4A062D477D842B4C8FC48EA5AF2D41F201BA207A@us-bv-m23.global.tektronix.net>

> > Normally is it the uboot that uncompresses the kernel or the kernel
> uncompress itself? 
> 
> >>How would something compressed uncompress itself?  If u-boot is being
> used 
> >>it will uncompress a compressed kernel and put the image at physical
> 0.
> 
> Small correction. Just like a self extracting binary, a kernel can have
> a decompression code prepended to the start of kernel which can
> decompress the 
> Kernel.  This is how redboot for xscale is structured or syslinux /lilo
> for x86. 

This also happens with the boot wrapper that is in arch/{ppc,powerpc}/boot

> 
> Although u-boot has simplified this step by doing the CRC checksum of
> the
> uiMage header as well as data and also decompress the kernel. Based on
> load
> address, entry point, the kernel can start executing.  
> 
> Now, whether cache is enable or not, MMU is enabled/disabled depends on
> the
> Developer. In current u-boot, the MMU is not used. I-Cache is On and
> D-cache
> is off.

I'm not sure what sub-arch we are talking about, but some do have the MMU 
on.

- kumar

  reply	other threads:[~2006-02-10 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 23:53 kernel startup atul.sabharwal
2006-02-10 23:46 ` Kumar Gala [this message]
2006-02-11  0:08 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-02-11  2:10 atul.sabharwal
2006-02-11  2:03 atul.sabharwal
2006-02-11  1:47 atul.sabharwal
2006-02-11 12:59 ` Wolfgang Denk
2006-02-11  1:40 atul.sabharwal
2006-02-11  0:28 atul.sabharwal
2006-02-11  0:23 ` Kumar Gala
2006-02-11  1:20 ` Wolfgang Denk
2006-02-11  0:19 atul.sabharwal
2006-02-11  0:10 atul.sabharwal
2006-02-11  0:03 ` Kumar Gala
2006-02-11  1:13   ` Wolfgang Denk
2006-02-11  1:12 ` Wolfgang Denk
2006-02-11  0:02 atul.sabharwal
2006-02-11  0:12 ` Wolfgang Denk
2006-02-10 23:33 dibacco
2006-02-10 23:32 ` Kumar Gala
2006-02-11  0:06   ` Wolfgang Denk

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=Pine.LNX.4.44.0602101745150.31619-100000@gate.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=atul.sabharwal@exgate.tek.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).