From: "fabien boucher" <fabien.fb@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Informations about mem and proc environment between bootloader and kernel
Date: Thu, 13 Sep 2007 16:05:11 +0200 [thread overview]
Message-ID: <f8f856500709130705t2109e559v19f0ffac318a4756@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
And I need some help for my project (I'm in internship) to port linux on a
custom board.
This board has been developped by the company where i'm doing the intership
and it's
based on a MPC875 with RAM and Flash chips and several other devices.
Currently the board run with a BSP developped
by the company's developpers, the BSP launch Psos.
This BSP is able to decompress an image and load it in RAM.
I plan to use U-boot to be more able to boot a kernel but as it's not a
common
board so it's not initialy supported by U-boot. So I have two choices first
use the BSP with some changes to adapt it for loading the Linux kernel or
using U-boot.
I'm looking for informations about the memory and processor environment
needed by linux to
boot properly for evaluate whether the use of a customize BSP is the easiest
way against
the port of a new board under U-boot. So if someone know where i can found
those informations
concerning the step between where the boot program have control of the cpu
and where Linux
take control.
Thank you,
Fabien
[-- Attachment #2: Type: text/html, Size: 1130 bytes --]
next reply other threads:[~2007-09-13 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 14:05 fabien boucher [this message]
2007-09-13 14:23 ` Informations about mem and proc environment between bootloader and kernel raul.moreno
2007-09-14 19:57 ` Wolfgang Denk
2007-10-23 7:42 ` DMA problem - mpc8xx raul.moreno
2007-10-23 18:49 ` Scott Wood
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=f8f856500709130705t2109e559v19f0ffac318a4756@mail.gmail.com \
--to=fabien.fb@gmail.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).