mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: Devicetree Maintenance in barebox
Date: Fri, 7 Feb 2014 09:47:29 +0100	[thread overview]
Message-ID: <20140207084729.GI16215@pengutronix.de> (raw)
In-Reply-To: <1391758773.537781517@f309.i.mail.ru>

On Fri, Feb 07, 2014 at 11:39:33AM +0400, Alexander Shiyan wrote:
> Hello.
> 
> Пятница,  7 февраля 2014, 8:13 +01:00 от Sascha Hauer <s.hauer@pengutronix.de>:
> > Hi All,
> > 
> > It's becoming more obvious that devicetree maintenance is painful
> > because we have to sync them to the kernel regularly. My hope was that
> > this would get simpler once the devicetrees get their own repository
> > outside the kernel, but it seems that won't happen anytime soon.
> > 
> > So my current idea to continue with barebox devicetrees is:
> > 
> > - Maintain a kernel branch which has all devicetree changes we need in
> > barebox in a clean step-by-step series
> > - rebase this branch regularly on the newer kernel
> > - Copy the resulting devicetrees to barebox
> > 
> > The upside is that we have up to date devicetrees in barebox without
> > having to resync them by hand on a per SoC basis.  Of course this also
> > means that we lose the devicetree history and breakage may be introduced
> > with some huge commits saying "Update devicetrees to Linux-3.x".
> > 
> > Any better ideas? I think we have to do something.
> 
> As far as I know, in the community have any thoughts on the transfer of the DT data
> in a separate project, but most likely it will not be soon ...

Yeah, I also don't think this will happen soon. Even if it does I think
this won't solve all problems. We will still need barebox specific
adjustments.

> 
> At the moment, I want to suggest to use only non-modified DT files, i.e. barebox
> should use to build their own files, which include the original data from the kernel.
> 
> Just for example:
> # ls
> bb_<board.dts>
> <board.dts>
> 
> # cat bb_<board.dts>
> 
> #include "<board.dts>"
> /* All overrides here */
> chosen {
>   ...
> };

I like the idea. One disadvantage may be that the structure in the dts
directory gets more unclear, but I guess we can't have everything.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-02-07  8:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  7:13 Sascha Hauer
2014-02-07  7:39 ` Alexander Shiyan
2014-02-07  8:47   ` Sascha Hauer [this message]
2014-02-07  9:01     ` Alexander Shiyan
2014-02-07  7:49 ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-07 14:10 ` Jason Cooper
2014-02-07 17:51   ` Jean-Christophe PLAGNIOL-VILLARD
2014-02-09 17:58   ` Jon Loeliger
2014-02-10 11:35     ` Ian Campbell
2014-02-10 15:06     ` Jason Cooper
2014-02-10 11:38   ` Ian Campbell
2014-02-17 19:42 ` Jason Cooper

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=20140207084729.GI16215@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=shc_work@mail.ru \
    /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