Bug#781999: Please install device-tree blobs in /boot

2015-05-17 Thread Ian Campbell
On Mon, 2015-04-06 at 12:08 +0200, Sjoerd Simons wrote:
 For reference when using linux-image-3.19.0-trunk-armmp this would add ~8 
 mbyte
 of dtb files to /boot, current linux-next's multi_v7 configuration generates
 around ~11 mbyte of dtb files.

That's a gain of a couple of M in the space of a couple of releases, how
long before it is 16M or 32M? Might that start proving a problem for
some smaller systems?

You mention generic ARM images, perhaps the tools which generate these
should take care of this? In much the same way as flash-kernel takes
care of it on a machine-by-machine basis.

Ian.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1431872296.5748.68.ca...@debian.org



Bug#781999: Please install device-tree blobs in /boot

2015-04-06 Thread Sjoerd Simons
Package: linux
Severity: wishlist

Hey,

The ARM linux image packages install DTB files in /usr/lib/kernel version/,
as a DTB is required to boot most modern arm systems typically the right file
has to be copied to a bootloader accessible filesystem before usage (e.g.
/boot). On current Debian systems this tends to be done by flash-kernel.
This ofcourse works fine for device-specific images, however for generic ARM
images that's pretty nasty.

I've recently started using the newish u-boot generic distro support on my
boards[0], which among other things allows one to simply specify a directory
containing the DTB files and u-boot will pick the right one based on the board
it's booting on.. Allowing generic images to be booted on boards where u-boot
is in e.g. flash. Ofcourse, this means all potentially used dtb files should be
on a boot-loader accessible partition, not just one specific board.

As such the request to install dtb files in /boot, which also follows the
convention in the upstream build system.

For reference when using linux-image-3.19.0-trunk-armmp this would add ~8 mbyte
of dtb files to /boot, current linux-next's multi_v7 configuration generates
around ~11 mbyte of dtb files.

0: http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.distro;hb=HEAD


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150406100845.10859.68883.reportbug@dusk