public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [ANNOUNCE] sunxi-babelfish (FEX-to-DT translator)
Date: Wed, 8 Jan 2014 19:29:06 +0100	[thread overview]
Message-ID: <20140108182906.GH2941@lukather> (raw)
In-Reply-To: <1389200137.27473.6.camel@kazak.uk.xensource.com>

On Wed, Jan 08, 2014 at 04:55:37PM +0000, Ian Campbell wrote:
> On Tue, 2014-01-07 at 23:03 +0100, Maxime Ripard wrote:
> > Another nice thing about it is that a FEX-to-DT compiler comes at no
> > cost afterwards. Since dtc is able to generate a DTS from
> > /proc/device-tree, you can easily generate a DTS for your previously
> > non-supported board using
> > 
> >   dtc -I fs -O dts -o my-board.dts /proc/device-tree/
> 
> I wonder if it might also be useful to compile this as a normal user
> space application which takes the fex and produces the dtb (or dts)?

At the moment, no, libfdt only operates on DTB, so we would have to
chain this somehow with dtc to at least do the DTB to DTS conversion I
guess.

It's not something that I'm pretty fond of either. Or, I don't really
see the benefit of it.

Let's say that you have such tool, I'm guessing one would want it to
mass-convert fex files to DT. But then, you'd still have to boot that
DT to be sure that everything is working, so you're pretty much losing
the mass-convertion thing, since you would have boot this with a
baremetal babelfish anyway.

> I suppose producing something upstreamable would be different/harder
> though, since it would need to not inline/merge the dtsi file but just
> leave the include stmt. That's probably a different tool.

Yeah, dtc outputs a "flat" DTS, without any include, so you still need
to edit it by hand to remove the common part, remove the duplicated
pinctrl nodes, fix the phandle, etc.

But most of that can be scripted I guess.

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140108/9d418e5e/attachment.sig>

  reply	other threads:[~2014-01-08 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 22:03 [ANNOUNCE] sunxi-babelfish (FEX-to-DT translator) Maxime Ripard
2014-01-08 13:02 ` Arnd Bergmann
2014-01-08 18:58   ` Maxime Ripard
2014-01-08 19:07     ` Arnd Bergmann
2014-01-08 16:55 ` [linux-sunxi] " Ian Campbell
2014-01-08 18:29   ` Maxime Ripard [this message]
2014-01-08 21:24     ` Ian Campbell
2014-01-09  0:15       ` Julian Calaby

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=20140108182906.GH2941@lukather \
    --to=maxime.ripard@free-electrons.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