From: Iwo Mergler <iwo@call-direct.com.au>
To: Meng Sun <meng.sun@sesca.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More things for writing new CPU ports.
Date: Mon, 22 Sep 2008 14:20:27 +1000 [thread overview]
Message-ID: <48D71D0B.8000405@call-direct.com.au> (raw)
In-Reply-To: <48D0B629.7070401@sesca.com>
Meng Sun wrote:
> Hi all,
>
> 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?
>
> Cheers,
That depends on what you mean by new CPU.
1) Your new CPU is an ASIC variant of an existing one. That is, it has a different
part number, but is based on a supported processor core, e.g. MIPS, ARM, etc.
In this case, you add a new board directory in arch/YourProc/. If the processor
architecture has ASIC variant support, use it to cover the stuff internal to the ASIC.
2) Your new CPU is an extension or modification of an existing processor core.
You have already updated GCC to support the extensions and now want kernel
support for the OS relevant ones.
In this case, you probably need to update the CPU common files files in arch/YourProc,
as well as create a board file for your target board.
3) You have designed a completely new processor core from scratch. You have
implemented support for this core in GNU binutils, GCC, etc. You have ported
a bootloader and now want Linux on your new system.
In this case, you create your own processor directory in arch/ and implement
the primitives, probably using an existing similar architecture as a template.
That directory is all yours, so you may decide using board or ASIC subdirectories.
In other words, the kernel is fairly modular and there is a good chance that you
new CPU is already 90% supported.
Kind regards,
Iwo
prev parent reply other threads:[~2008-09-22 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 7:47 More things for writing new CPU ports Meng Sun
2008-09-22 4:20 ` Iwo Mergler [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=48D71D0B.8000405@call-direct.com.au \
--to=iwo@call-direct.com.au \
--cc=linux-kernel@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