linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Brauer <brauer@texmemsys.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: New port
Date: Fri, 26 Nov 1999 18:59:52 -0600 (CST)	[thread overview]
Message-ID: <199911270059.SAA07621@sun92.texmemsys.com> (raw)


I am looking on information on porting linux to a new ppc platform.  The short 
version of my efforts are to port linux to a custom 603 sbc.  I have experiance 
with device driver writing, but at this time limited knowledge of the boot 
architecture of ppc.  Currently we are using ix86 to ppc cross compiler to 
generate the kernels.  The SBC consits of a 603 4MB flash, 128 MBs memory, and 
an FPGA which acts as the serial port/DMA engine, network controller, and 
controls memory accesses.  I guess what I am looking for is where to start.  We 
are currently using an EST Vision Probe to download code into RAM on the SBC and 
starting execution.  There is currently no initialization done before we enter 
arch/ppc/head.S but the EST box complained about the locations of memory being 
beyond the physical limits of the RAM at 0xc0000000, so in the Makefile we 
mapped this to 0, but I am not sure if there is a better way around this.  The 
code and documentation on this are light, so any information on this process, 
and the correct way to go about initializing the board before execution of 
head.S would be greatly appreciated.

Essentialy from this my questions would be
1.  Is there a correct mode to start running head.S in (ie. translation on/off?)
2.  Where should the stack be started at?
3.  Where should the code be downloaded to?
4.  Is an uncompressed kernel better than a compressed one?
5.  If we load the kernel at address 0, should we change KERNELBASE?
6.  It appears that after kludging up to identify machine we tend to die.
7.  Enabling the caching seems to throw us for a loop as well.
8.  What values does the kernel assume are passed in by a boot loader and how?

Thanks in advance to anyone who might be able to help in me understanding this 
code better and how to go about getting a good start on this port.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-11-27  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-27  0:59 Jonathan Brauer [this message]
1999-11-29  9:35 ` New port Adrian Cox

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=199911270059.SAA07621@sun92.texmemsys.com \
    --to=brauer@texmemsys.com \
    --cc=linuxppc-dev@lists.linuxppc.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).