mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Pascal Vizeli <pascal.vizeli@syshack.ch>
To: barebox@lists.infradead.org
Subject: Re: Device Tree Overlay Support v2
Date: Sat, 2 Jun 2018 18:00:17 +0200	[thread overview]
Message-ID: <CACvFaDcTLm-XbCZH363y1izaqRMxoOXo29k2ANWrQND=tsCV7w@mail.gmail.com> (raw)
In-Reply-To: <CACvFaDchGoj77fZrfVhqp1jeUphZjn_HhoXUhfxRWXLCPUt6zg@mail.gmail.com>

Look like there is a bug with resolve __local_fixups__
I try to fix that and make a patch for this.

2018-05-27 16:44 GMT+02:00 Pascal Vizeli <pascal.vizeli@syshack.ch>:
> There was some missing files inside patches. I fix that.
> Actual version work on my local site with fresh environment.
>
> 2018-05-27 11:39 GMT+02:00 Pascal Vizeli <pvizeli@syshack.ch>:
>> Hi,
>>
>> I rebase and update the patch from Jan Luebbe. They did a amazing job with:
>> http://lists.infradead.org/pipermail/barebox/2015-March/022674.html
>>
>> I think it is now at the time to support overlay like uboot and other
>> bootloaders. They will help on raspberry, I think also on other
>> platforms, to update the device tree without a big shell script of
>> of_properties/of_fixup_status.
>>
>> This features is very common today and missed by barebox.
>> I update the dtc scripts to the same version they we use on dts kernel level.
>>
>> Patch are here:
>> https://github.com/home-assistant/hassos/tree/dev/buildroot-external/patches/barebox
>>
>> Greets

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

      reply	other threads:[~2018-06-02 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-27  9:39 Pascal Vizeli
2018-05-27 14:44 ` Pascal Vizeli
2018-06-02 16:00   ` Pascal Vizeli [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='CACvFaDcTLm-XbCZH363y1izaqRMxoOXo29k2ANWrQND=tsCV7w@mail.gmail.com' \
    --to=pascal.vizeli@syshack.ch \
    --cc=barebox@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