From: Matthew Wilcox <matthew@wil.cx>
To: Meng Sun <meng.sun@sesca.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: How to write ports to new CPU and architecture?
Date: Wed, 17 Sep 2008 07:41:35 -0600 [thread overview]
Message-ID: <20080917134134.GB5802@parisc-linux.org> (raw)
In-Reply-To: <48D0F9A2.60806@sesca.com>
On Wed, Sep 17, 2008 at 03:35:46PM +0300, Meng Sun wrote:
> What should I do for implement Linux kernel on a new CPU and target
> board? I just read FAQ but it's just general information. Could you
> please tell me which documents(except CPU datasheets and target board
> documents) I should read?
Is it an existing processor such as PowerPC or MIPS? If so, you should
approach that port directly and ask for advice (since it will differ
greatly from one architecture to another).
Is it a new processor that we don't currently have support for in the
kernel tree? That's a much larger undertaking, normally a multi-year
project First, you're going to need a toolchain that targets your CPU --
GCC, binutils and so on. Then you can start porting Linux. It's
probably best to start by copying an existing architecture and modify it
piecemeal.
I can't really be more specific since your question is so vague.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2008-09-17 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 12:35 How to write ports to new CPU and architecture? Meng Sun
2008-09-17 13:41 ` Matthew Wilcox [this message]
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=20080917134134.GB5802@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-arch@vger.kernel.org \
--cc=meng.sun@sesca.com \
/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