Merge patch series "vepxpress64: disable CRC32 by default and add FVP with TF-A guide"

Harrison Mutai <harrison.mutai@arm.com> says:

This patch introduces two updates to the vexpress64 project:

- Disable CRC32 by default to prevent aborts in a standard FVP setup.
- Add a guide for running FVP with TF-A, providing a clear starting point for
  users.

Link: https://lore.kernel.org/r/20250304165204.53097-1-harrison.mutai@arm.com

diff --cc doc/board/armltd/vexpress64.rst
index a732fac,434cc78..109337d
--- 1/doc/board/armltd/vexpress64.rst
--- 2/doc/board/armltd/vexpress64.rst
+++ b/doc/board/armltd/vexpress64.rst
@@@ -31,6 -36,50 +36,50 @@@ into the TF-A build: ``make PLAT=<platf
  
  The FVPs can be debugged using Arm Development Studio [2]_.
  
 -TF-A's FIP format [5]. It contains all images executed by TF-A, including U-Boot.
+ Building U-Boot
+ ^^^^^^^^^^^^^^^
+ 
+ Set the ``CROSS_COMPILE`` environment variable as usual, and run:
+ 
+ .. code-block:: bash
+ 
+     make vexpress_fvp_defconfig
+     make
+ 
+ Running U-Boot
+ ^^^^^^^^^^^^^^
+ 
+ Set ``CROSS_COMPILE`` as usual and build TF-A:
+ 
+ .. code-block:: bash
+ 
+     git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
+     cd trusted-firmware-a
+     make PLAT=fvp BL33=/path/to/u-boot.bin fiptool all fip
+ 
+ This command generates the ROM image `bl1.bin`, and a boot image `fip.bin` in
++TF-A's FIP format [5]_. It contains all images executed by TF-A, including U-Boot.
+ Note that TF-A outputs the built binaries into `build/fvp/release/`.
+ 
+ If you already have a FIP image, and are primarily interested in updating the BL33
+ image (i.e., U-Boot), use `fiptool` from TF-A:
+ 
+ .. code-block:: bash
+ 
+     make fiptool
+     tools/fiptool/fiptool update --nt-fw=/path/to/u-boot.bin /path/to/fip.bin
+ 
+ To run the FVP:
+ 
+ .. code-block:: bash
+ 
+     FVP_Base_RevC-2xAEMvA -C bp.flashloader0.fname=fip.bin \
+         -C bp.secureflashloader.fname=bl1.bin \
+         -C bp.vis.disable_visualisation=1
+ 
+ This setup relies on semi-hosting, as well as, having a kernel image (``Image``)
+ and ramdisk (``ramdisk.img``) in the current working directory.
+ 
  Juno
  ----