From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] davinci: Initial support for MityDSP-L138/MityARM-1808
Date: Thu, 02 Sep 2010 11:10:16 -0700 [thread overview]
Message-ID: <871v9c6mpj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1283450287-9881-1-git-send-email-michael.williamson@criticallink.com> (Michael Williamson's message of "Thu, 2 Sep 2010 13:58:07 -0400")
Michael Williamson <michael.williamson@criticallink.com> writes:
> This patch adds initial support for the MityDSP-L138 and MityDSP-1808 system
> on Module (SOM) under the machine name "mityomapl138". These SOMs are based
> on the da850 davinci CPU architecture. Information on these SOMs may be
> found at http://www.mitydsp.com.
>
> Basic support for the console UART, NAND, and EMAC (MII interface) is
> included in this patch.
>
> Signed-off-by: Michael Williamson <michael.williamson@criticallink.com>
Thanks, applying and queueing for 2.6.37 (with one minor change
below...)
> ---
> Changes since v2:
> 1) Remove defaulting this board from Kconfig.
> 2) Add MITYOMAPL138 board to da8xx_omapl_defconfig.
> 3) Fix tabs alignment per comment.
>
> The new defconfig file was generated by:
> make da8xx_omapl_defconfig
> make menuconfig
> select MITYOMAPL138 option
> make savedefconfig
> cp defconfig arch/arm/configs/da8xx_omapl_defconfig
>
> I think the other 3 lines were a result of updated KConfig options
> in the current baseline.
Yes, but to minimize unrelated defconfig diffs upstream, I'm going to
remove the 3 unrelated ones when applying this patch.
Soon we will hopefully be getting rid of defconfigs all together, but
until that is sorted out, we need to minimize diffs against defconfigs,
especially ones that are not related to the patch.
Kevin
prev parent reply other threads:[~2010-09-02 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:58 [PATCH v3] davinci: Initial support for MityDSP-L138/MityARM-1808 Michael Williamson
2010-09-02 18:05 ` Sergei Shtylyov
2010-09-02 18:17 ` Kevin Hilman
2010-09-02 18:10 ` Kevin Hilman [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=871v9c6mpj.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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