Bug#989579: arm-trusted-firmware: Raspberry pi builds
On 6/8/21 8:46 PM, Vagrant Cascadian wrote: I ended up uploading to experimental with both rpi4 and rpi3. The rpi3 build instructions were confusing; hopefully the defaults are reasonable. Please test it when you get a chance! Awesome, thanks for putting this together! Not a comprehensive test, but it boots to u-boot and then on to Linux userspace on my pi4. Adds a few seconds to boot time, which is more than I expected, but also perfectly fine. I don't have a pi3 handy, so I tried qemu's raspi3b machine type, using "-bios bl31.bin". Qemu segfaulted pretty much instantly in arm_setup_firmware_boot trying to set the kernel commandline in fw_cfg. This probably doesn't tell us much about how well it would work on a real pi3... - nolan
Bug#989579: arm-trusted-firmware: Raspberry pi builds
On 2021-06-07, Vagrant Cascadian wrote: > On 2021-06-07, Nolan wrote: >> While it won't provide any real security features, it would let people >> "fix" the pi's missing PSCI, which would enable the use of kexec. > > There appear to be two rpi platforms in arm-trusted-firmware > v2.4. Reading the documentation on rpi3: > > > https://salsa.debian.org/debian/arm-trusted-firmware/-/blob/0f7062a50552947943316e83557dddb47fba3efe/docs/plat/rpi3.rst > > There appear to be many permutations of possible configuration options, > so it is unclear exactly what to enable... > > > The documentation for rpi4: > > > https://salsa.debian.org/debian/arm-trusted-firmware/-/blob/0f7062a50552947943316e83557dddb47fba3efe/docs/plat/rpi4.rst > > Is relatively simple and clear, though! > > > Could you spell out a little more what you'd like enabled, ideally with > a tested patch? :) I ended up uploading to experimental with both rpi4 and rpi3. The rpi3 build instructions were confusing; hopefully the defaults are reasonable. Please test it when you get a chance! live well, vagrant signature.asc Description: PGP signature
Bug#989579: arm-trusted-firmware: Raspberry pi builds
On 2021-06-07, Nolan wrote: > While it won't provide any real security features, it would let people > "fix" the pi's missing PSCI, which would enable the use of kexec. There appear to be two rpi platforms in arm-trusted-firmware v2.4. Reading the documentation on rpi3: https://salsa.debian.org/debian/arm-trusted-firmware/-/blob/0f7062a50552947943316e83557dddb47fba3efe/docs/plat/rpi3.rst There appear to be many permutations of possible configuration options, so it is unclear exactly what to enable... The documentation for rpi4: https://salsa.debian.org/debian/arm-trusted-firmware/-/blob/0f7062a50552947943316e83557dddb47fba3efe/docs/plat/rpi4.rst Is relatively simple and clear, though! Could you spell out a little more what you'd like enabled, ideally with a tested patch? :) live well, vagrant signature.asc Description: PGP signature
Bug#989579: arm-trusted-firmware: Raspberry pi builds
Source: arm-trusted-firmware Severity: wishlist Hello, While it won't provide any real security features, it would let people "fix" the pi's missing PSCI, which would enable the use of kexec. - nolan
