On Wed, 30 Nov 2016 10:14:01 +1100 Jonathan Liu <[email protected]> wrote:
> Hi Paul, > > On 30 November 2016 at 07:39, Paul Barker <[email protected]> wrote: > > > On Sun, 27 Nov 2016 17:37:53 +1100 > > Jonathan Liu <[email protected]> wrote: > > > > > A patch is backported to check if the firmware loaded a device tree blob > > > into memory and set the fdt_addr variable if it is found. The U-Boot > > > script will then read the command line arguments generated by the > > > firmware from the device tree and boot the kernel with the command > > > line arguments and the loaded device tree. > > > > > > This allows things like MAC address, board revision and serial number > > > to be correctly configured and options in config.txt to be used. > > > > > > Signed-off-by: Jonathan Liu <[email protected]> > > > --- > > > Changes in v4: > > > - Backport patch from upstream instead of using own patch > > > > I had to make a few additional changes on top of this patch to get a > > successful compile with u-boot v2016.03. These changes can be seen here: > > > > https://gitlab.com/pbarker/meta-raspberrypi/commit/ > > f880569e62d431cbead1555cf6c47342fe79c969 > > > > After those changes though, everything worked as expected on both an > > original rpi B+ and an rpi3. > > > > Does your patch work cleanly on a later version of u-boot? I know > > oe-core is likely to upgrade to v2016.11 any day now. We could either > > apply the changes I've linked to above or hold off until v2016.11 is > > merged to oe-core if that's what you've tested with. > > > > Yes, my patch applies cleanly to v2016.11 as well. I only tested with > Raspberry Pi 3 as I didn't have a Raspberry Pi 2 around at the time. > The upstream commits landed in master after v2016.11 so backports will be > needed until at least v2017.01. > > Are you able to squash your changes into this patch and submit a v5 with > your Signed-off-by tag? > Will do. Currently in progress, will send once I've given it a quick test. Thanks, Paul Barker -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
