- 15 Feb, 2024 28 commits
-
-
Raptor Engineering Development Team authored
This retains owner control since the images are signed and verified with the well-known public/private keypairs, but has two benefits: 1.) Component verification is enabled, which will catch corruption and eliminate the STB warning messages 2.) The secure boot chain is verified to work on production firmware, making transition on a customer-specific basis to customer keys a supported operation.
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
Raptor carries this patch in its hostboot tree
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
Data corruption occurs regularly when direct loading firmware from the squashfs mtdblock device. This is likely due to simultaneous accesses confusing the underlying OPAL flash driver, and takes the form of the following error messages: [ 6.305837] I/O error, dev mtdblock4, sector 416 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2 [ 6.305852] SQUASHFS error: Failed to read block 0x342e6: -5 [ 6.307457] I/O error, dev mtdblock4, sector 418 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2 [ 6.307472] SQUASHFS error: Failed to read block 0x346c2: -5 [ 6.308404] I/O error, dev mtdblock4, sector 416 op 0x0:(READ) flags 0x800 phys_seg 1 prio class 2 [ 6.308412] SQUASHFS error: Failed to read block 0x342e6: -5 [ 6.308415] SQUASHFS error: Unable to read data cache entry [342e6] [ 6.308417] SQUASHFS error: Unable to read page, block 342e6, size 3dc [ 6.309206] SQUASHFS error: Unable to read data cache entry [342e6] [ 6.309210] SQUASHFS error: Unable to read page, block 342e6, size 3dc [ 6.309233] amdgpu 0033:01:00.0: loading /lib/firmware/amdgpu/polaris10_mec_2.bin failed with error -5 [ 6.309241] amdgpu 0033:01:00.0: Direct firmware load for amdgpu/polaris10_mec_2.bin failed with error -5
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
Use current version of 6.6 LTS kernel series for Petitboot
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
This avoids the potential for accidental inclusion of closed-source proprietary firmware components in future firmware builds.
-
Raptor Engineering Development Team authored
-
- 09 Feb, 2024 12 commits
-
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
* Nouveau driver (mostly fails on POWER w/ 64k pages anyway) * Non-English locales * Discrete HWDB files Once the -Os build failure has been resolved upstream, these can likely be reenabled.
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-
Raptor Engineering Development Team authored
-