All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Denil <joachim.denil@gmail.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: porting linux to new board type
Date: Tue, 15 Nov 2005 13:03:51 +0100	[thread overview]
Message-ID: <4379ce76.65b4ffc2.2c64.274a@mx.gmail.com> (raw)

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

Hi,
 
For an internship I have to port linux to custom made board. I assume I'll
have to set the memory-map right and make the hardware initialize, set IRQ,
.. Browsing trough the kernel source I found that all that happens within
/arch/ppc/platforms and there are separate files for each board. But how do
I start to write my own code. Can someone give me some pointers or is there
any documentation on this subject? This is what my board is made of:
 
*	64 Mb SDRAM (a PLD copy's the kernel to this location (0x00000000))
*	1 MB boot ram (a PLD copy's the boot loader from flash to this
location at the end of the memory map)
*	MMC card reader
*	Flash 8MB (don't have to use it though-> the PLD's use them to copy
boot loader and kernel there)
*	Leds that I can use through a PLD-register
 
The processor is a 405Gr processor, 1 UART is connected to a V24 iface.
The boot loader is a striped version of ppcboot, and is now used to load a
self written RTOS. So I guess I can use that version.
 
Is there besides this something else I 'll have to adjust? 
 
Thanks,
 
Joachim Denil
Student @ Karel De Grote hogeschool Antwerpen (Belgium)

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

             reply	other threads:[~2005-11-15 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 12:03 Joachim Denil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-01 11:30 porting linux to new board type Nathael PAJANI

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=4379ce76.65b4ffc2.2c64.274a@mx.gmail.com \
    --to=joachim.denil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.