From: nickpelling@nanodome.com (Nick Pelling)
To: linux-arm-kernel@lists.infradead.org
Subject: "Porting the Linux Kernel to a New ARM Platform", updated...?
Date: Thu, 27 Jan 2011 12:58:02 +0000 [thread overview]
Message-ID: <87a7d0$e7q8m3@out1.ip07ir2.opaltelecom.net> (raw)
In-Reply-To: <20110127121928.GA1948@richard-laptop>
Hi everyone,
I've been looking for a good source of information on getting Linux
working on a new ARM target, including a checklist of things to cover
such as putc(), arch_decomp_setup(), etc. So far, pretty much the
best source of information I've found is Wookey & Tak-Shing's
"Porting the Linux Kernel to a New ARM Platform"...
http://www.glomationinc.com/PortingLinuxKernel.pdf
...but I can't help but notice that this is from 2002.
Is there an updated version of this document (or perhaps a book
chapter covering this) you would recommend?
Cheers, ....Nick Pelling....
next prev parent reply other threads:[~2011-01-27 12:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:08 [PATCH 1/3] ARM: mach-mx5: Fix build for mx53_loco and mx53_smd Fabio Estevam
2011-01-25 15:08 ` [PATCH 2/3] ARM: mach-mx5/board-mx53_loco: Make UART1 functional Fabio Estevam
2011-01-25 15:08 ` [PATCH 3/3] ARM: mach-mx5/board-mx53_loco: Remove unused UARTs Fabio Estevam
2011-01-28 12:48 ` Richard Zhao
2011-01-28 12:48 ` [PATCH 2/3] ARM: mach-mx5/board-mx53_loco: Make UART1 functional Richard Zhao
2011-01-27 7:30 ` [PATCH 1/3] ARM: mach-mx5: Fix build for mx53_loco and mx53_smd Sascha Hauer
2011-01-27 9:30 ` Richard Zhao
2011-01-27 11:48 ` Fabio Estevam
2011-01-27 12:19 ` Richard Zhao
2011-01-27 12:58 ` Nick Pelling [this message]
2011-02-03 14:31 ` "Porting the Linux Kernel to a New ARM Platform", updated...? Steve Chen
2011-02-03 14:36 ` Russell King - ARM Linux
[not found] ` <AANLkTikWsU2V+1ohAaiFfRneLjsGRWx7ee5X655mAa18@mail.gmail.c om>
2011-02-05 9:59 ` Nick Pelling
2011-01-28 12:26 ` [PATCH 1/3] ARM: mach-mx5: Fix build for mx53_loco and mx53_smd Fabio Estevam
2011-01-28 12:46 ` Richard Zhao
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='87a7d0$e7q8m3@out1.ip07ir2.opaltelecom.net' \
--to=nickpelling@nanodome.com \
--cc=linux-arm-kernel@lists.infradead.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.