All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael.williamson@criticallink.com (Michael Williamson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] davinci: Initial support for MityDSP-L138/MityARM-1808
Date: Tue, 31 Aug 2010 10:59:09 -0400	[thread overview]
Message-ID: <4C7D18BD.9050708@criticallink.com> (raw)
In-Reply-To: <87zkw2u956.fsf@deeprootsystems.com>

 On 8/31/2010 10:52 AM, Kevin Hilman wrote:
> 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>
>> ---
>> Patch is against 0a50e05b20f3c6af67656303bdb3661a2541ce03 of Kevin's tree 
>> (2.6.36-rc2).
>>
>> Changes since v0:
>>   1) Added CONFIG_REGULATOR_DUMMY to da8xx_omapl_defconfig to support
>>      DA8XX machines not providing voltage regulation.
>>   2) Added machine checks on da830/da850 EVM as well as MityDSP-L138 
>>      console init routines.
> These two should be a separate patch as it's a fix not directly related
> to your board support.
>

OK.  I'll separate them and resubmit.  Thanks for your help.

-Mike

  reply	other threads:[~2010-08-31 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31  0:55 [PATCH v1] davinci: Initial support for MityDSP-L138/MityARM-1808 Michael Williamson
2010-08-31 14:52 ` Kevin Hilman
2010-08-31 14:59   ` Michael Williamson [this message]
2010-08-31 15:39 ` Nori, Sekhar
2010-08-31 16:14   ` Nori, Sekhar

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=4C7D18BD.9050708@criticallink.com \
    --to=michael.williamson@criticallink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.