From: cmchao <cmchao@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 00/12] refactor OMAP implementation
Date: Sat, 29 May 2010 09:54:14 +0800 [thread overview]
Message-ID: <1275098066-9022-1-git-send-email-cmchao@gmail.com> (raw)
The following changes since commit 29f91781bd300b228d9c38b9f6c1e0b6a38f25fb:
Jes Sorensen (1):
vhost_net.c: v2 Fix build failure introduced by 0bfcd599e3f5c5679cc7d0165a0a1822e2f60de2
The patches almostly base on http://meego.gitorious.org/qemu-maemo/qemu work and
act as preparatory work to merge their OMAP3 and beagleboard support. All the
work are to separate modules, which will be shared or extended in OMAP3 implementation
and make certain local function static
[PATCH 01/12] hw/omap1.c : separate gpio module
[PATCH 02/12] hw/omap2.c : separate gpio module
[PATCH 03/12] hw/omap2.c : separate gptimer module
[PATCH 04/12] hw/omap2.c : separate synctimer module
[PATCH 05/12] hw/omap2.c : separate gpmc(general purpose memory controller)
[PATCH 06/12] hw/omap2.c : separate sdrc (sdram controller)
[PATCH 07/12] hw/omap1.c : separate interrupt controller module
[PATCH 08/12] hw/omap2.c : separate spi module
[PATCH 09/12] hw/omap2.c : separate tap module(Test-Chip-level)
[PATCH 10/12] hw/omwp2.c : separate l4 interconnect module
[PATCH 11/12] hw/omap1.c : separate uart module
[PATCH 12/12] hw/omap : make local function static and remove declaration from header
next reply other threads:[~2010-05-29 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 1:54 cmchao [this message]
2010-05-29 1:54 ` [Qemu-devel] [PATCH 01/12] hw/omap1.c : separate gpio module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 02/12] hw/omap2.c " cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 03/12] hw/omap2.c : separate gptimer module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 04/12] hw/omap2.c : separate synctimer module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 05/12] hw/omap2.c : separate gpmc(general purpose memory controller) cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 06/12] hw/omap2.c : separate sdrc (sdram controller) cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 07/12] hw/omap1.c : separate interrupt controller module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 08/12] hw/omap2.c : separate spi module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 09/12] hw/omap2.c : separate tap module(Test-Chip-level) cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 10/12] hw/omwp2.c : separate l4 interconnect module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 11/12] hw/omap1.c : separate uart module cmchao
2010-05-29 1:54 ` [Qemu-devel] [PATCH 12/12] hw/omap : make local function static and remove declaration from header cmchao
-- strict thread matches above, loose matches on Subject: below --
2010-05-28 17:43 [Qemu-devel] [PATCH 00/12] refactor OMAP implementation cmchao
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=1275098066-9022-1-git-send-email-cmchao@gmail.com \
--to=cmchao@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).