From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Devicetree Maintenance in barebox
Date: Fri, 7 Feb 2014 08:49:55 +0100 [thread overview]
Message-ID: <20140207074955.GH9671@ns203013.ovh.net> (raw)
In-Reply-To: <20140207071332.GE16215@pengutronix.de>
On 08:13 Fri 07 Feb , Sascha Hauer wrote:
> 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.
push the kernel to split the tree as a sub module at least
so other project can import it
Best Regards,
J.
>
> 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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-02-07 7:49 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
2014-02-07 9:01 ` Alexander Shiyan
2014-02-07 7:49 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
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=20140207074955.GH9671@ns203013.ovh.net \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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