public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gcembed@gmail.com (Gaëtan Carlier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: imx: Add DTSC02 platform (i.MX27)
Date: Thu, 27 Mar 2014 16:55:37 +0100	[thread overview]
Message-ID: <533449F9.4090101@gmail.com> (raw)
In-Reply-To: <53344680.6080800@gmail.com>

Fabio,
On 03/27/2014 04:40 PM, Ga?tan Carlier wrote:
> Hi Fabio,
> On 03/27/2014 04:35 PM, Fabio Estevam wrote:
>> Hi Ga?tan,
>>
>> On Thu, Mar 27, 2014 at 12:29 PM, Ga?tan Carlier <gcembed@gmail.com>
>> wrote:
>>>
>>> Signed-off-by: Ga?tan Carlier <gcembed@gmail.com>
>>> ---
>>>   arch/arm/mach-imx/Kconfig       |   17 ++
>>>   arch/arm/mach-imx/Makefile      |    1 +
>>>   arch/arm/mach-imx/mach-dtsc02.c |  416
>>> +++++++++++++++++++++++++++++++++++++++
>>>   3 files changed, 434 insertions(+), 0 deletions(-)
>>>   create mode 100644 arch/arm/mach-imx/mach-dtsc02.c
>>
>> My understanding is that new board files are not allowed for ARM.
>>
>> Have you considered creating a device tree implementation instead?
>>
>>  From a quick look, all the devices you are registering are currently
>> supported on device tree.
> Later, I will add emma-pp, emma-prp, sound which is actually not working
> (error related to DMA coherent in ssi driver), coda. I will check how
> device tree works.
I am using Redboot (ecos 20090512), I supposed that is not directly 
compatible and I have to append DTS blob to zImage as specified in 
slides petazzoni-device-tree-dummies.pdf ?
>>
>> Regards,
>>
>> Fabio Estevam
>>
> Thanks.
> Ga?tan Carlier.
Thank you for help help,
Ga?tan Carlier.

  reply	other threads:[~2014-03-27 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 15:29 [PATCH 1/1] ARM: imx: Add DTSC02 platform (i.MX27) Gaëtan Carlier
2014-03-27 15:35 ` Fabio Estevam
2014-03-27 15:40   ` Gaëtan Carlier
2014-03-27 15:55     ` Gaëtan Carlier [this message]
2014-03-27 16:31       ` Fabio Estevam

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=533449F9.4090101@gmail.com \
    --to=gcembed@gmail.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