On 20 Jul 2016, at 09:29, Matwey V. Kornilov <matwey@opensuse.org> wrote:

18.07.2016, 11:15, "Guillaume Gardet" <guillaume.gardet@free.fr>:

...

Le 18/07/2016 à 09:55, Guillaume GARDET a écrit :

Le 17/07/2016 à 05:12, Andreas Färber a écrit : Am 11.07.2016 um 02:17 schrieb Andreas Färber: Here are some mixed test results of 4.7.0-rc6-4.g3146576: Updates for kernel 4.7.0-rc6-5.gcc11143 / U-Boot 2016.07:

Jetson TK1: * lpae works but only with Tumbleweed kernel-firmware, oops otherwise * lpae works with either kernel-firmware * udev-induced oops still happens, but with some patience recovers http://paste.opensuse.org/ddbac180 <http://paste.opensuse.org/ddbac180> * U-Boot 2016.07 works

* 4.6.2-1-lpae boots okay with dtb-tegra124 4.7.rc6

Cubietruck: * lpae broken, no output * lpae and default still broken

* 4.6.2-1-lpae boots with dtb-sun7i 4.7.rc6 * Only boot.scr works, no output with GRUB (u-boot-cubietruck 2016.05) * U-Boot 2016.07 still boots with boot.scr only

Raspberry Pi 3: * U-Boot 2016.07 works

Raspberry Pi 2: * default and lpae broken, no output * default and lpae still broken

* 4.6.2-1-default boots with dtb-bcm2836 4.7.rc6 (-lpae known broken) * U-Boot 2016.07 works

Raspberry Pi: * default boots fine, except for some deadbeef vc4 error * default still boots

* 4.6.2-1-default boots with dtb-bcm2835 4.7.rc6 * U-Boot 2016.07 works

BeagleBone Black: * default boots fine * 4.6.2-1-default does _not_ boot with dtb-am335x 4.7.rc6: "irq 22: nobody cared" triggered by udev / omap_aes * u-boot-am335xevm 2016.07 _broken_: stuck after "DRAM: 512 MiB", reboots continuously (watchdog?); reverting to 2016.05 fixes

You could try u-boot-am335xboneblack and/or upstream version. If upstream version is broken, please report it upstream.

A quick test shows that : * upstream u-boot-am335xboneblack : boots on Beagle Bone Black * upstream u-boot-am335xevm : is broken on Beagle Bone Black

Don't they differ only in config?

Yes, as do all targets :). I think the main difference (and reason for breakage) is that evm is trying to read from NAND. Either way, I see little reason to not switch to the beaglebone u-boot target. Could someone please verify that this one works correctly (read: does more than just boot)? Then I’ll switch the package inclusion in JeOS. Alex