Re: trying to understand how the /boot/loader symlink is supposed to work.

On Wed, Jan 31, 2018 at 9:49 AM, Dan Nicholson <nicholson endlessm com> wrote:
Here's what /boot looks like on one of our ARM images:

├── loader -> loader.1
├── loader.1
│   ├── entries
│   │   └── ostree-eos-0.conf
│   └── uEnv.txt
├── ostree
│   └── eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277
│       ├── initramfs-3.10-trunk-meson8b
│       └── vmlinuz-3.10-trunk-meson8b
└── uEnv.txt -> loader/uEnv.txt

And just to clarify that the vmlinuz file there is actually an itb
image including the kernel and 2 device trees. Probably not the usage
pattern that ostree intended, but it works.

Our u-boot detects which board is booting and picks the right device
tree to use.
If your uboot doesn't read uEnv.txt by default then you may need to
configure the boot command like we did.

You can find those changes in
(not totally clean, apologies)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]