From: Kevin Hickey <khickey@rmicorp.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: [PATCH v3 0/5] Alchemy: Basic Au1300 and DB1300 support
Date: Wed, 8 Apr 2009 18:36:03 -0500 [thread overview]
Message-ID: <1239233768-11927-1-git-send-email-khickey@rmicorp.com> (raw)
In-Reply-To: <>
This patch series introduces support for the RMI Alchemy Au1300 series of SOCs
and the DBAu1300 (or DB1300) development board. With this set the basic CPU
and board are supported. I have code for several of the peripherals, including
USB, MMC, IDE, and Ethernet and will submit those patches after these have been
accepted.
Though some of the new code added here could be useful for other boards (the
DB1200 in particular), I did my best to limit this patch set to additions only.
It should not disturb any other boards. To verify this I built and tested the
updated directory for an on a DB1200 board. A future patch set may include
some integration of this new code into the DB1200 configuration.
This set incorporates feedback I received on v2 of these patches.
=Kevin
next reply other threads:[~2009-04-08 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 23:36 Kevin Hickey [this message]
2009-04-08 23:36 ` [PATCH v3 1/5] Alchemy: Initial Au1300 and DBAu1300 support Kevin Hickey
2009-04-08 23:36 ` [PATCH v3 2/5] Alchemy: Au1300 new interrupt controller Kevin Hickey
2009-04-08 23:36 ` [PATCH v3 3/5] Alchemy: Au1300/DB1300 UART support Kevin Hickey
2009-04-08 23:36 ` [PATCH v3 4/5] Alchemy: Au1300/DB1300 peripheral resource declarations Kevin Hickey
2009-04-08 23:36 ` [PATCH v3 5/5] Alchemy: Au1300: Add LCD framebuffer support Kevin Hickey
2009-04-09 10:07 ` [PATCH v3 2/5] Alchemy: Au1300 new interrupt controller Manuel Lauss
2009-04-09 10:07 ` Manuel Lauss
2009-04-09 14:27 ` Kevin Hickey
2009-04-09 15:15 ` Manuel Lauss
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=1239233768-11927-1-git-send-email-khickey@rmicorp.com \
--to=khickey@rmicorp.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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