2016-12-05 19:37 GMT+01:00 Khem Raj <raj.k...@gmail.com>: > On Mon, Dec 5, 2016 at 7:26 AM, Mirza Krak <mirza.k...@gmail.com> wrote: >> Hi. >> >> I have some questions and remarks and hopefully someone here can answer them. >> >> The meta-raspberrpi layer is missing a morty release? Any time frame >> of when this will be added? > > We use master as long as possible, when we have a change that makes master > incompatible with prior releases we branch out for the prior releases > at that point.
Thank you for the clarification. > >> >> There is currently a issue when using U-boot due to some updates in >> RPi boot firmware. See [1] and [2]. Which should be noted/resolved >> before a morty release? >> >> To provide some more information about above mentioned problem. If you >> use the current firmware files (20161030 in meta-raspberrypi) together >> with U-boot (2016.03) you lose the console on U-boot and on Linux >> kernel. This is due to the fact that "newer" firmware sets a default >> uart clock to 48 MHz, but U-boot has a hard-coded value of 3 MHz, and >> since we yet do not support to "forward" the patched DTB provided by >> the firmware from U-boot to Linux we also break console on Linux. >> >> The "default" values has been updated in Linux, see [2]. But if you >> use that updated Linux kernel there is a mismatch between u-boot and >> Linux. Should be noted that U-boot 2016.11 does not have this problem >> since it does not try to initialize the UART port at all and only >> relies on firmware to set it up correctly (see [3]). > > We should drop 2016.03 and support 2016.11 for keeping it simple. Should also update Linux which contains the updated default value (since we do not yet support pass-trough of firmware DTB, I know I have seen some patches on the mailing list but nothing in upstream yet). But U-boot is in meta-openembedded, are you suggesting that we update it in meta-raspberry? Or updating it in meta-openembedded? Best Regards Mirza -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
