summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/README.qemu-arm6
-rw-r--r--doc/driver-model/MIGRATION.txt4
2 files changed, 9 insertions, 1 deletions
diff --git a/doc/README.qemu-arm b/doc/README.qemu-arm
index 260165638aa..e67bc13f701 100644
--- a/doc/README.qemu-arm
+++ b/doc/README.qemu-arm
@@ -47,6 +47,12 @@ The minimal QEMU command line to get U-Boot up and running is:
Note that for some odd reason qemu-system-aarch64 needs to be explicitly
told to use a 64-bit CPU or it will boot in 32-bit mode.
+Additional persistent U-boot environment support can be added as follows:
+- Create envstore.img using qemu-img:
+ qemu-img create -f raw envstore.img 64M
+- Add a pflash drive parameter to the command line:
+ -drive if=pflash,format=raw,index=1,file=envstore.img
+
Additional peripherals that have been tested to work in both U-Boot and Linux
can be enabled with the following command line parameters:
diff --git a/doc/driver-model/MIGRATION.txt b/doc/driver-model/MIGRATION.txt
index 6b691338b4e..dce4aa3e1dc 100644
--- a/doc/driver-model/MIGRATION.txt
+++ b/doc/driver-model/MIGRATION.txt
@@ -44,7 +44,9 @@ Deadline: 2019.07
In concert with maintainers migrating their block device usage to the
appropriate DM driver, CONFIG_BLK needs to be set as well. The final deadline
here coincides with the final deadline for migration of the various block
-subsystems.
+subsystems. At this point we will be able to audit and correct the logic in
+Kconfig around using CONFIG_PARTITIONS and CONFIG_HAVE_BLOCK_DEVICE and make
+use of CONFIG_BLK / CONFIG_SPL_BLK as needed.
CONFIG_DM_SPI
CONFIG_DM_SPI_FLASH