Hi, On Tue, Feb 05, 2019 at 09:28:18PM +0100, Alexandre GRIVEAUX wrote: > Thanks for your reply and i understand our not part of Debian boot > team, effectively I made some mistake for these boards: > > Machine: Raspberry Pi 3 Compute Module > > The DT should be: > > bcm2837-rpi-cm3-io3.dtb Right. Adding that one looks sensible to me. I suggest to send this separately from the remaining changes. > Machine: Raspberry Pi 1 Model B > > The DT should be: > > bcm2835-rpi-b.dtb Ok. > For Raspberry Pi 1, the DTB is present inside armhf kernel files and i > doesn't find the armel kernel: > > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-a-plus.dtb > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-a.dtb > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-b-plus.dtb > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-b-rev2.dtb > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-b.dtb > /usr/lib/linux-image-4.9.0-8-armmp/bcm2835-rpi-zero.dtb They may be inside the armhf kernel package, but those machines should only be used with armel in Debian. Debian's armhf binaries may contain instructions, that are not available on the RPi 1 CPU. > My goal is to use Debian with the kernel packaged no the Rasbian > one. Ok. In Debian the RPi 1 hardware needs to use armel instead of armhf. There is currently no suitable kernel, but this is WIP (see message from Ben). I suppose adding these entries only makes sense after there is a kernel package for RPi 1. > For test purpose, I only used Raspberry Pi 2 So basically all of this is untested, since RPi 2 is not part of this patch. Also note, that only the first generation is problematic with armhf, since the second generation is supported by armhf. -- Sebastian
Attachment:
signature.asc
Description: PGP signature