From: "Guan Xuetao" <gxt@mprc.pku.edu.cn>
To: <linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>, "'Greg KH'" <greg@kroah.com>
Subject: [PATCHv2 00/11] unicore32 core architecture
Date: Sun, 13 Feb 2011 14:23:51 +0800 [thread overview]
Message-ID: <02e101cbcb46$96333a40$c299aec0$@mprc.pku.edu.cn> (raw)
From: Guan Xuetao <gxt@mprc.pku.edu.cn>
The whole subsystem code could be fetched from:
git://git.kernel.org/pub/scm/linux/kernel/git/epip/linux-2.6-unicore32.git
with branch name: unicore32.
And it is divided into three patch sets: core architecture files,
additional architecture files, and machine related files.
This patch set adds the core architecture support for UniCore32 ISA.
Patch 1 implements build infrastructure.
Patch 2 includes some generic stuff including elf and ksyms.
Because all one-line asm-generic headers are auto-generated by ASM_GENERIC_HEADERS
in arch/unicore32/Makefile, so the rest seems very little.
ELF handling functions and module handling functions are also here.
Patch 3 includes processor and system headers. System call interface is here.
We used the syscall interface the same as asm-generic version.
Patch 4 implements low level entry and setup codes.
Patch 5 implements process/thread related codes. Backtrace and stacktrace are here.
Patch 6 includes generic codes of memory management.
Patch 7 implements fault handling of memory management.
Patch 8 implements consistent device DMA handling of memory management.
DMA device operations are also here.
Patch 9 implements timer and time. RTC and PWM device drivers are also here.
Patch 10 implements interrupts and gpio. UniCore32 has 9 gpio interrupt sources.
And gpio device operations are also here.
Patch 11 implements signals.
Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
reply other threads:[~2011-02-13 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='02e101cbcb46$96333a40$c299aec0$@mprc.pku.edu.cn' \
--to=gxt@mprc.pku.edu.cn \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome