skiboot
skiboot copied to clipboard
open-power
OPAL boot and runtime firmware for POWER
``` [ 71.035066444,5] INIT: 64-bit LE kernel discovered [ 71.078038665,5] STB: EV_SEPARATOR measured on pcr0 (tpm0, evType 0x4, evLogLen 2649) [ 71.121106055,5] STB: EV_SEPARATOR measured on pcr1 (tpm0, evType 0x4,...
Running @legoater 's qemu tree (3.1 based) with the powernv model: ``` [ 0.270844220,5] PCI: Resetting PHBs and training links... [ 0.272165254,7] PHB#0000: FRESET: Assert skipped [ 0.272202593,7] PHB#0000: FRESET:...
Host: dtc -I fs -O dts /proc/device-tree > foo.dts Warning (reg_format): "reg" property in /ibm,opal/flash@0 has invalid length (8 bytes) (#address-cells == 0, #size-cells == 0) Warning (unit_address_vs_reg): Node /vpd/dimm@30000...
``` 66.01168|====================[ 66.011887081,5] OPAL skiboot-v5.9-240-g081882690163-pcbedce4 starting... [ 66.011894300,7] initial console log level: memory 7, driver 5 [ 66.011896673,6] CPU: P9 generation processor (max 4 threads/core) [ 66.011898763,7] CPU: Boot CPU...
Currently we need to 'touch outputfile.ffs' before running ffspart. There's a TODO in ffspart.c for this. We should instead fail when the output file exists, to stop people overwriting things...
In order to write good tests, reading the generated file is required (see https://github.com/open-power/skiboot/issues/202). Ideas on how to make a pflash available for the test harness are welcome. We could...
Currently the ffspart command line requires you to specify: - block size (in hex?!) - number of blocks A friendlier UI would be to specify the: - optionally, total output...