Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs: beaglebone: update kernel to 4.1.13 and u-boot to 2015.10
Date: Thu, 14 Jan 2016 22:41:52 +0100	[thread overview]
Message-ID: <56981620.5020805@mind.be> (raw)
In-Reply-To: <20160113095153.6b4f95cb@free-electrons.com>

On 13-01-16 09:51, Thomas Petazzoni wrote:
> Zoltan,
> 
> On Wed, 13 Jan 2016 03:52:22 +0100, Zoltan Gyarmati wrote:
> 
[snip]
>>  ...comment-block-of-fdt_get_property_namelen.patch |   32 +
>>  .../0002-fdt-Add-a-function-to-count-strings.patch |  246 +++
>>  ...d-a-function-to-get-the-index-of-a-string.patch |  159 ++
>>  ...004-fdt-Add-functions-to-retrieve-strings.patch |  173 ++
> 
> I am not supper happy with the solution of having those DTC patches
> specifically for the BeagleBone platform. If I understand correctly,
> those patches are needed to get the DT overlay to work, right ?

 I was the one suggesting that approach...


> We had the same problem for the C.H.I.P platform, so it would also be
> useful for us to have a overlay-capable DTC. You can see what my
> colleague Antoine T?nart did:
> 
>   https://github.com/NextThingCo/CHIP-buildroot/commit/1a73b514d204d0c6e9100d53011a11d99fd8b778
>   https://github.com/NextThingCo/CHIP-buildroot/commit/f3334df58611ff3cae5fd62906423fdce3d80d24
>   https://github.com/NextThingCo/CHIP-buildroot/commit/c4457eba3099f5ca514c06bb35b42772178a151a
> 
> It is not ideal because it relies on a separate dtc-overlay package,
> which packages a different version of dtc, which Antoine has cooked on
> his own github repository.
> 
> We really need to find a solution that is acceptable in the upstream
> Buildroot, and applies to multiple platforms.

 Just thinking out loud: we could add an option to the dtc package that selects
the overlay version.

 The canonical approach, however, would be to convert dtc to a virtual package
with a dtc-kernel-org and a dtc-overlay implementation.

 Regards,
 Arnout

[snip]

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-01-14 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  2:52 [Buildroot] [PATCH 1/1] configs: beaglebone: update kernel to 4.1.13 and u-boot to 2015.10 Zoltan Gyarmati
2016-01-13  8:51 ` Thomas Petazzoni
2016-01-14 21:41   ` Arnout Vandecappelle [this message]
2016-01-15  5:13     ` Zoltan Gyarmati
2016-01-15  8:21       ` Thomas Petazzoni
2016-01-16 13:36         ` Zoltan Gyarmati
2016-01-16 14:45           ` Chris LaRocque
2016-01-15  1:53   ` Zoltan Gyarmati
2016-03-08 16:36 ` Thomas Petazzoni
2016-05-25 12:35 ` Thomas Petazzoni

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=56981620.5020805@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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