All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: kernelnewbies@lists.kernelnewbies.org
Subject: guides to board files -> device-tree and Android -> mainline?
Date: Tue, 29 Jan 2013 15:51:09 +0100	[thread overview]
Message-ID: <20130129155109.07ab0340@skate> (raw)
In-Reply-To: <1359423808.27343.16.camel@chianamo>

Dear Paul Wise,

On Tue, 29 Jan 2013 09:43:28 +0800, Paul Wise wrote:

> > If you want to add the board itself and it is ARM based, then you have
> > to create a device tree file. I think the older board files are no
> > more accepted in the mainline kernel.
> 
> I'm aware of that, my question was how do I convert existing board files
> to device tree files? Is there an automated tool, or a guide for that?

No, there is no automated tool, because it is not possible to do that
automatically. The device drivers used by your board must have a Device
Tree binding, and writing the Device Tree source cannot directly be
done from the C board file. It requires human knowledge and
intervention.

Could you be more specific about the platform you would look to convert
to the Device Tree? Where is the existing source code?

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-29 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26  4:50 guides to board files -> device-tree and Android -> mainline? Paul Wise
2013-01-26 15:13 ` Matthias Brugger
2013-01-29  1:43   ` Paul Wise
2013-01-29 14:51     ` Thomas Petazzoni [this message]
2013-01-30  2:16       ` Paul Wise

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=20130129155109.07ab0340@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.