All of lore.kernel.org
 help / color / mirror / Atom feed
From: snijsure@grid-net.com (Subodh Nijsure)
To: linux-arm-kernel@lists.infradead.org
Subject: Issues when running DT enabled kernel on iMX28 from linux-next
Date: Fri, 18 May 2012 15:52:18 -0700	[thread overview]
Message-ID: <4FB6D2A2.1090400@grid-net.com> (raw)
In-Reply-To: <20120518010138.GA5427@S2101-09.ap.freescale.net>

On 05/17/2012 06:01 PM, Shawn Guo wrote:
> On Thu, May 17, 2012 at 04:03:43PM -0700, Subodh Nijsure wrote:
>> Should one be able to run top of the linux-next on MX28 EVK hardware
>> with DT support enabled?
> Yes, I'm running it well with next-20120516.

I followed the subsequent discussion on this, looks like most of you are 
booting your kernels with uBoot.
We are using linux_prep bootlets from freescale to boot linux kernel.

I have following options turned on in my setup
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y

I am building imx28-evk.dtb and appending it to zImage as in:

make  imx28-evk.dtb
cat zImage imx28-evk.dtb > zImage_w_dtb

We will investigate this further and let you know what I find, would be 
glad to hear if anybody else is using MXS platform with appended device 
tree.

-Subodh

  parent reply	other threads:[~2012-05-18 22:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 23:03 Issues when running DT enabled kernel on iMX28 from linux-next Subodh Nijsure
2012-05-18  1:01 ` Shawn Guo
2012-05-18  1:50   ` Fabio Estevam
2012-05-18  1:58     ` Shawn Guo
2012-05-18  2:00       ` Fabio Estevam
2012-05-18  2:33         ` Shawn Guo
2012-05-18  3:05           ` Fabio Estevam
2012-05-18 11:21   ` Marek Vasut
2012-05-18 22:52   ` Subodh Nijsure [this message]
2012-05-19  1:23     ` Marek Vasut
2012-05-19 12:34       ` Shawn Guo
2012-05-19 16:02         ` Marek Vasut
2012-05-20  2:00           ` Shawn Guo

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=4FB6D2A2.1090400@grid-net.com \
    --to=snijsure@grid-net.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.