All of lore.kernel.org
 help / color / mirror / Atom feed
From: pabs3@bonedaddy.net (Paul Wise)
To: kernelnewbies@lists.kernelnewbies.org
Subject: guides to board files -> device-tree and Android -> mainline?
Date: Wed, 30 Jan 2013 10:16:07 +0800	[thread overview]
Message-ID: <1359512167.27343.24.camel@chianamo> (raw)
In-Reply-To: <20130129155109.07ab0340@skate>

On Tue, 2013-01-29 at 15:51 +0100, Thomas Petazzoni wrote:

> 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.

I see, is there at least a guide for the conversion?

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

Many devices with an ARM SoC and or an Android kernel aren't fully
supported by mainline. The devices that I own in this situation are the
OpenMoko FreeRunner (gta02) and the Samsung Galaxy S (galaxysmtd).

gta02:
git://git.openmoko.org/git/kernel.git
git://github.com/shr-distribution/linux.git

galaxysmtd (and a bunch of other devices):
git://gitorious.org/replicant/kernel_samsung_aries.git

-- 
bye,
pabs

http://bonedaddy.net/pabs3/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130130/2dd617ac/attachment.bin 

      reply	other threads:[~2013-01-30  2:16 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
2013-01-30  2:16       ` Paul Wise [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=1359512167.27343.24.camel@chianamo \
    --to=pabs3@bonedaddy.net \
    --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.