On Wed, 2017-12-06 at 07:53 +0100, Andre Heider wrote:
>
> I don't know what devices you work on, but I have a couple of different
> consumer armhf and arm64 devices, spread out over different
> architectures. All their device trees are updated every single kernel
> release. Often it's for new
Hello All,
On Tue, Dec 05, 2017 at 10:47:12PM +0100, Karsten Merker wrote:
> > Please don't ship dtb files at all, including the kernel images.
...
> it appears to me that this argument assumes a situation that we
> simply don't have for many devices. A lot of the ARM-based
> devices that Debian
On Tue, 5 Dec 2017 14:07:46 + Leif Lindholm
wrote:
Please don't ship dtb files at all, including the kernel images.
If firmware does not come with hardware description, that is a
shortcoming of the firmware. If a newer kernel cannot be booted with
an existing device tree, then that is a bug
X-Debbugs-CC: glik...@secretlab.ca
Please don't ship dtb files at all, including the kernel images.
If firmware does not come with hardware description, that is a
shortcoming of the firmware. If a newer kernel cannot be booted with
an existing device tree, then that is a bug and the kernel should
Source: debian-installer
Some arm64 devices (like espressobin) boot using u-boot and not using
efi. For these the kernel's corresponding dtb is required to boot.
I only checked the latest daily netboot.tar.gz, and while armhf ships
those files, arm64 does not.
When fishing out the dtb out o
5 matches
Mail list logo
