On 26.02.18 08:19, Matwey V. Kornilov wrote: > 2018-02-26 0:06 GMT+03:00 Alexander Graf <[email protected]>: >> >> >>> Am 25.02.2018 um 16:37 schrieb Matwey V. Kornilov >>> <[email protected]>: >>> >>> 25.02.2018 18:22, Matwey V. Kornilov пишет: >>>> >>>> Hi, >>>> >>>> I am faced the issue that recent JeOS builds cannot be read by u-boot: >>>> >>>> ls mmc 1:2 / >>>> Failed to mount ext2 filesystem... >>>> ** Unrecognized filesystem type ** >>> >>> Hm, Now I see. Why do you use btrfs for having separate /boot partition? >>> Is there any reason for it? >> >> I assume that change came with the seitch to python-kiwi. I assume the main >> rationale would be snapshotting of /boot, so you can load old kernels. >> > > /lib/modules are on the separate partition, so it won't work anyway. > We could have united / and put dtb files onto separate EFI partition > for snapshotting kernels.
Nah, if you go that far, better ensure the built-in device tree from U-Boot contains a device tree that just covers everything you need. That way you don't need to load any dtb files. The dtb loading from /boot is really mostly there for cases where firmware is "broken" and does not deliver good, upstream compatible device trees. >> I guess there is an xml tag we can provide to make /boot ext4 again? I've changed the xml to explicitly have a /boot partition in ext4. Alex -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
