From: Christian Hewitt <christianshewitt@gmail.com>
To: u-boot@lists.denx.de, u-boot-amlogic@groups.io,
linux-amlogic@lists.infradead.org
Subject: [PATCH 10/33] doc: boards: amlogic: update documentation for Khadas VIM3
Date: Mon, 20 Mar 2023 11:45:46 +0000 [thread overview]
Message-ID: <20230320114609.930145-11-christianshewitt@gmail.com> (raw)
In-Reply-To: <20230320114609.930145-1-christianshewitt@gmail.com>
Improve documentation.
Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
---
doc/board/amlogic/khadas-vim3.rst | 137 +++++++++++++++---------------
1 file changed, 68 insertions(+), 69 deletions(-)
diff --git a/doc/board/amlogic/khadas-vim3.rst b/doc/board/amlogic/khadas-vim3.rst
index 73dc32b79b..88f2e0ebbe 100644
--- a/doc/board/amlogic/khadas-vim3.rst
+++ b/doc/board/amlogic/khadas-vim3.rst
@@ -1,10 +1,10 @@
.. SPDX-License-Identifier: GPL-2.0+
-U-Boot for Khadas VIM3
-======================
+U-Boot for Khadas VIM3 (A311D)
+==============================
-Khadas VIM3 is a single board computer manufactured by Shenzhen Wesion
-Technology Co., Ltd. with the following specifications:
+Khadas VIM3 is a Single Board Computer manufactured by Shenzhen Wesion Technology Co. Ltd
+with the following specifications:
- Amlogic A311D Arm Cortex-A53 dual-core + Cortex-A73 quad-core SoC
- 4GB LPDDR4 SDRAM
@@ -20,32 +20,27 @@ Schematics are available on the manufacturer website.
PCIe Setup
----------
-The VIM3 on-board MCU can mux the PCIe/USB3.0 shared differential
-lines using a FUSB340TMX USB 3.1 SuperSpeed Data Switch between
-an USB3.0 Type A connector and a M.2 Key M slot.
-The PHY driving these differential lines is shared between
-the USB3.0 controller and the PCIe Controller, thus only
-a single controller can use it.
-To setup for PCIe, run the following commands from U-Boot:
+The on-board MCU can mux the PCIe/USB3.0 shared differential lines using a FUSB340TMX USB
+3.1 SuperSpeed Data Switch between a USB3.0 Type-A connector and an M.2 Key M slot. The
+PHY driving these differential lines is shared between the USB3.0 controller and the PCIe
+Controller, thus only a single controller can use it.
+
+To setup for PCIe run the following commands from U-Boot then power-cycle the board:
.. code-block:: none
i2c dev i2c@5000
i2c mw 0x18 0x33 1
-Then power-cycle the board.
-
-To set back to USB3.0, run the following commands from U-Boot:
+To revert to USB3.0 run the following commands from U-Boot then power-cycle the board:
.. code-block:: none
i2c dev i2c@5000
i2c mw 0x18 0x33 0
-Then power-cycle the board.
-
-U-Boot compilation
+U-Boot Compilation
------------------
.. code-block:: bash
@@ -54,14 +49,20 @@ U-Boot compilation
$ make khadas-vim3_defconfig
$ make
-Image creation
---------------
+U-Boot Signing with Pre-Built FIP repo
+--------------------------------------
+
+.. code-block:: bash
+ $ git clone https://github.com/LibreELEC/amlogic-boot-fip --depth=1
+ $ cd amlogic-boot-fip
+ $ mkdir my-output-dir
+ $ ./build-fip.sh khadas-vim3 /path/to/u-boot/u-boot.bin my-output-dir
-For simplified usage, pleaser refer to :doc:`pre-generated-fip` with codename `khadas-vim3`
+U-Boot Manual Signing
+---------------------
-Amlogic doesn't provide sources for the firmware and for tools needed
-to create the bootloader image, so it is necessary to obtain them from
-the git tree published by the board vendor:
+Amlogic does not provide sources for the firmware and tools needed to create a bootloader
+image so it is necessary to obtain binaries from sources published by the board vendor:
.. code-block:: bash
@@ -72,16 +73,14 @@ the git tree published by the board vendor:
$ export PATH=$PWD/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux/bin:$PWD/gcc-linaro-arm-none-eabi-4.8-2013.11_linux/bin:$PATH
$ DIR=vim3-u-boot
- $ git clone --depth 1 \
- https://github.com/khadas/u-boot.git -b khadas-vims-v2015.01 \
- $DIR
+ $ git clone --depth 1 https://github.com/khadas/u-boot.git -b khadas-vims-v2015.01 $DIR
$ cd vim3-u-boot
$ make kvim3_defconfig
$ make CROSS_COMPILE=aarch64-none-elf-
$ export UBOOTDIR=$PWD
-Go back to mainline U-Boot source tree then :
+Go back to the mainline U-Boot source tree then:
.. code-block:: bash
@@ -105,58 +104,58 @@ Go back to mainline U-Boot source tree then :
$ cp u-boot.bin fip/bl33.bin
$ bash fip/blx_fix.sh \
- fip/bl30.bin \
- fip/zero_tmp \
- fip/bl30_zero.bin \
- fip/bl301.bin \
- fip/bl301_zero.bin \
- fip/bl30_new.bin \
- bl30
+ fip/bl30.bin \
+ fip/zero_tmp \
+ fip/bl30_zero.bin \
+ fip/bl301.bin \
+ fip/bl301_zero.bin \
+ fip/bl30_new.bin \
+ bl30
$ bash fip/blx_fix.sh \
- fip/bl2.bin \
- fip/zero_tmp \
- fip/bl2_zero.bin \
- fip/acs.bin \
- fip/bl21_zero.bin \
- fip/bl2_new.bin \
- bl2
+ fip/bl2.bin \
+ fip/zero_tmp \
+ fip/bl2_zero.bin \
+ fip/acs.bin \
+ fip/bl21_zero.bin \
+ fip/bl2_new.bin \
+ bl2
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl30sig --input fip/bl30_new.bin \
- --output fip/bl30_new.bin.g12a.enc \
- --level v3
+ --output fip/bl30_new.bin.g12a.enc \
+ --level v3
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl30_new.bin.g12a.enc \
- --output fip/bl30_new.bin.enc \
- --level v3 --type bl30
+ --output fip/bl30_new.bin.enc \
+ --level v3 --type bl30
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl31.img \
- --output fip/bl31.img.enc \
- --level v3 --type bl31
+ --output fip/bl31.img.enc \
+ --level v3 --type bl31
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl33.bin --compress lz4 \
- --output fip/bl33.bin.enc \
- --level v3 --type bl33 --compress lz4
+ --output fip/bl33.bin.enc \
+ --level v3 --type bl33 --compress lz4
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl2sig --input fip/bl2_new.bin \
- --output fip/bl2.n.bin.sig
+ --output fip/bl2.n.bin.sig
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bootmk \
- --output fip/u-boot.bin \
- --bl2 fip/bl2.n.bin.sig \
- --bl30 fip/bl30_new.bin.enc \
- --bl31 fip/bl31.img.enc \
- --bl33 fip/bl33.bin.enc \
- --ddrfw1 fip/ddr4_1d.fw \
- --ddrfw2 fip/ddr4_2d.fw \
- --ddrfw3 fip/ddr3_1d.fw \
- --ddrfw4 fip/piei.fw \
- --ddrfw5 fip/lpddr4_1d.fw \
- --ddrfw6 fip/lpddr4_2d.fw \
- --ddrfw7 fip/diag_lpddr4.fw \
- --ddrfw8 fip/aml_ddr.fw \
- --ddrfw9 fip/lpddr3_1d.fw \
- --level v3
-
-and then write the image to SD with:
+ --output fip/u-boot.bin \
+ --bl2 fip/bl2.n.bin.sig \
+ --bl30 fip/bl30_new.bin.enc \
+ --bl31 fip/bl31.img.enc \
+ --bl33 fip/bl33.bin.enc \
+ --ddrfw1 fip/ddr4_1d.fw \
+ --ddrfw2 fip/ddr4_2d.fw \
+ --ddrfw3 fip/ddr3_1d.fw \
+ --ddrfw4 fip/piei.fw \
+ --ddrfw5 fip/lpddr4_1d.fw \
+ --ddrfw6 fip/lpddr4_2d.fw \
+ --ddrfw7 fip/diag_lpddr4.fw \
+ --ddrfw8 fip/aml_ddr.fw \
+ --ddrfw9 fip/lpddr3_1d.fw \
+ --level v3
+
+Then write U-Boot to SD or eMMC with:
.. code-block:: bash
- $ DEV=/dev/your_sd_device
+ $ DEV=/dev/boot_device
$ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=512 skip=1 seek=1
- $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=444
+ $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=440
--
2.34.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Christian Hewitt <christianshewitt@gmail.com>
To: u-boot@lists.denx.de, u-boot-amlogic@groups.io,
linux-amlogic@lists.infradead.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: [PATCH 10/33] doc: boards: amlogic: update documentation for Khadas VIM3
Date: Mon, 20 Mar 2023 11:45:46 +0000 [thread overview]
Message-ID: <20230320114609.930145-11-christianshewitt@gmail.com> (raw)
In-Reply-To: <20230320114609.930145-1-christianshewitt@gmail.com>
Improve documentation.
Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
---
doc/board/amlogic/khadas-vim3.rst | 137 +++++++++++++++---------------
1 file changed, 68 insertions(+), 69 deletions(-)
diff --git a/doc/board/amlogic/khadas-vim3.rst b/doc/board/amlogic/khadas-vim3.rst
index 73dc32b79b..88f2e0ebbe 100644
--- a/doc/board/amlogic/khadas-vim3.rst
+++ b/doc/board/amlogic/khadas-vim3.rst
@@ -1,10 +1,10 @@
.. SPDX-License-Identifier: GPL-2.0+
-U-Boot for Khadas VIM3
-======================
+U-Boot for Khadas VIM3 (A311D)
+==============================
-Khadas VIM3 is a single board computer manufactured by Shenzhen Wesion
-Technology Co., Ltd. with the following specifications:
+Khadas VIM3 is a Single Board Computer manufactured by Shenzhen Wesion Technology Co. Ltd
+with the following specifications:
- Amlogic A311D Arm Cortex-A53 dual-core + Cortex-A73 quad-core SoC
- 4GB LPDDR4 SDRAM
@@ -20,32 +20,27 @@ Schematics are available on the manufacturer website.
PCIe Setup
----------
-The VIM3 on-board MCU can mux the PCIe/USB3.0 shared differential
-lines using a FUSB340TMX USB 3.1 SuperSpeed Data Switch between
-an USB3.0 Type A connector and a M.2 Key M slot.
-The PHY driving these differential lines is shared between
-the USB3.0 controller and the PCIe Controller, thus only
-a single controller can use it.
-To setup for PCIe, run the following commands from U-Boot:
+The on-board MCU can mux the PCIe/USB3.0 shared differential lines using a FUSB340TMX USB
+3.1 SuperSpeed Data Switch between a USB3.0 Type-A connector and an M.2 Key M slot. The
+PHY driving these differential lines is shared between the USB3.0 controller and the PCIe
+Controller, thus only a single controller can use it.
+
+To setup for PCIe run the following commands from U-Boot then power-cycle the board:
.. code-block:: none
i2c dev i2c@5000
i2c mw 0x18 0x33 1
-Then power-cycle the board.
-
-To set back to USB3.0, run the following commands from U-Boot:
+To revert to USB3.0 run the following commands from U-Boot then power-cycle the board:
.. code-block:: none
i2c dev i2c@5000
i2c mw 0x18 0x33 0
-Then power-cycle the board.
-
-U-Boot compilation
+U-Boot Compilation
------------------
.. code-block:: bash
@@ -54,14 +49,20 @@ U-Boot compilation
$ make khadas-vim3_defconfig
$ make
-Image creation
---------------
+U-Boot Signing with Pre-Built FIP repo
+--------------------------------------
+
+.. code-block:: bash
+ $ git clone https://github.com/LibreELEC/amlogic-boot-fip --depth=1
+ $ cd amlogic-boot-fip
+ $ mkdir my-output-dir
+ $ ./build-fip.sh khadas-vim3 /path/to/u-boot/u-boot.bin my-output-dir
-For simplified usage, pleaser refer to :doc:`pre-generated-fip` with codename `khadas-vim3`
+U-Boot Manual Signing
+---------------------
-Amlogic doesn't provide sources for the firmware and for tools needed
-to create the bootloader image, so it is necessary to obtain them from
-the git tree published by the board vendor:
+Amlogic does not provide sources for the firmware and tools needed to create a bootloader
+image so it is necessary to obtain binaries from sources published by the board vendor:
.. code-block:: bash
@@ -72,16 +73,14 @@ the git tree published by the board vendor:
$ export PATH=$PWD/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux/bin:$PWD/gcc-linaro-arm-none-eabi-4.8-2013.11_linux/bin:$PATH
$ DIR=vim3-u-boot
- $ git clone --depth 1 \
- https://github.com/khadas/u-boot.git -b khadas-vims-v2015.01 \
- $DIR
+ $ git clone --depth 1 https://github.com/khadas/u-boot.git -b khadas-vims-v2015.01 $DIR
$ cd vim3-u-boot
$ make kvim3_defconfig
$ make CROSS_COMPILE=aarch64-none-elf-
$ export UBOOTDIR=$PWD
-Go back to mainline U-Boot source tree then :
+Go back to the mainline U-Boot source tree then:
.. code-block:: bash
@@ -105,58 +104,58 @@ Go back to mainline U-Boot source tree then :
$ cp u-boot.bin fip/bl33.bin
$ bash fip/blx_fix.sh \
- fip/bl30.bin \
- fip/zero_tmp \
- fip/bl30_zero.bin \
- fip/bl301.bin \
- fip/bl301_zero.bin \
- fip/bl30_new.bin \
- bl30
+ fip/bl30.bin \
+ fip/zero_tmp \
+ fip/bl30_zero.bin \
+ fip/bl301.bin \
+ fip/bl301_zero.bin \
+ fip/bl30_new.bin \
+ bl30
$ bash fip/blx_fix.sh \
- fip/bl2.bin \
- fip/zero_tmp \
- fip/bl2_zero.bin \
- fip/acs.bin \
- fip/bl21_zero.bin \
- fip/bl2_new.bin \
- bl2
+ fip/bl2.bin \
+ fip/zero_tmp \
+ fip/bl2_zero.bin \
+ fip/acs.bin \
+ fip/bl21_zero.bin \
+ fip/bl2_new.bin \
+ bl2
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl30sig --input fip/bl30_new.bin \
- --output fip/bl30_new.bin.g12a.enc \
- --level v3
+ --output fip/bl30_new.bin.g12a.enc \
+ --level v3
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl30_new.bin.g12a.enc \
- --output fip/bl30_new.bin.enc \
- --level v3 --type bl30
+ --output fip/bl30_new.bin.enc \
+ --level v3 --type bl30
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl31.img \
- --output fip/bl31.img.enc \
- --level v3 --type bl31
+ --output fip/bl31.img.enc \
+ --level v3 --type bl31
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl3sig --input fip/bl33.bin --compress lz4 \
- --output fip/bl33.bin.enc \
- --level v3 --type bl33 --compress lz4
+ --output fip/bl33.bin.enc \
+ --level v3 --type bl33 --compress lz4
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bl2sig --input fip/bl2_new.bin \
- --output fip/bl2.n.bin.sig
+ --output fip/bl2.n.bin.sig
$ $UBOOTDIR/fip/g12b/aml_encrypt_g12b --bootmk \
- --output fip/u-boot.bin \
- --bl2 fip/bl2.n.bin.sig \
- --bl30 fip/bl30_new.bin.enc \
- --bl31 fip/bl31.img.enc \
- --bl33 fip/bl33.bin.enc \
- --ddrfw1 fip/ddr4_1d.fw \
- --ddrfw2 fip/ddr4_2d.fw \
- --ddrfw3 fip/ddr3_1d.fw \
- --ddrfw4 fip/piei.fw \
- --ddrfw5 fip/lpddr4_1d.fw \
- --ddrfw6 fip/lpddr4_2d.fw \
- --ddrfw7 fip/diag_lpddr4.fw \
- --ddrfw8 fip/aml_ddr.fw \
- --ddrfw9 fip/lpddr3_1d.fw \
- --level v3
-
-and then write the image to SD with:
+ --output fip/u-boot.bin \
+ --bl2 fip/bl2.n.bin.sig \
+ --bl30 fip/bl30_new.bin.enc \
+ --bl31 fip/bl31.img.enc \
+ --bl33 fip/bl33.bin.enc \
+ --ddrfw1 fip/ddr4_1d.fw \
+ --ddrfw2 fip/ddr4_2d.fw \
+ --ddrfw3 fip/ddr3_1d.fw \
+ --ddrfw4 fip/piei.fw \
+ --ddrfw5 fip/lpddr4_1d.fw \
+ --ddrfw6 fip/lpddr4_2d.fw \
+ --ddrfw7 fip/diag_lpddr4.fw \
+ --ddrfw8 fip/aml_ddr.fw \
+ --ddrfw9 fip/lpddr3_1d.fw \
+ --level v3
+
+Then write U-Boot to SD or eMMC with:
.. code-block:: bash
- $ DEV=/dev/your_sd_device
+ $ DEV=/dev/boot_device
$ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=512 skip=1 seek=1
- $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=444
+ $ dd if=fip/u-boot.bin.sd.bin of=$DEV conv=fsync,notrunc bs=1 count=440
--
2.34.1
next prev parent reply other threads:[~2023-03-20 11:46 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 11:45 [PATCH 00/33] doc: board: amlogic: spring clean-up of Amlogic docs Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 01/33] doc: boards: amlogic: update documentation for index page Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 02/33] doc: boards: amlogic: update documentation for boot-flow Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 03/33] doc: boards: amlogic: update documentation for pre-generated-fip's Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 04/33] doc: boards: amlogic: update documentation for Beelink GT-King Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 05/33] doc: boards: amlogic: update documentation for Beelink GT-King Pro Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 06/33] doc: boards: amlogic: update documentation for JetHub J100 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 07/33] doc: boards: amlogic: update documentation for JetHub J80 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 08/33] doc: boards: amlogic: update documentation for Khadas VIM Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 09/33] doc: boards: amlogic: update documentation for Khadas VIM2 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt [this message]
2023-03-20 11:45 ` [PATCH 10/33] doc: boards: amlogic: update documentation for Khadas VIM3 Christian Hewitt
2023-03-20 11:45 ` [PATCH 11/33] doc: boards: amlogic: update documentation for Khadas VIM3L Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 12/33] doc: boards: amlogic: update documentation for LaFrite Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 13/33] doc: boards: amlogic: update documentation for LePotato Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 14/33] doc: boards: amlogic: update documentation for NanoPi-K2 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 15/33] doc: boards: amlogic: update documentation for ODROID-C2 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 16/33] doc: boards: amlogic: update documentation for ODROID-C4 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 17/33] doc: boards: amlogic: update documentation for ODROID GO ULTRA Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 18/33] doc: boards: amlogic: update documentation for ODROID-N2/N2+ Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 19/33] doc: boards: amlogic: update documentation for ODROID-N2L Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 20/33] doc: boards: amlogic: update documentation for P200 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 21/33] doc: boards: amlogic: update documentation for P201 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 22/33] doc: boards: amlogic: update documentation for Q200 Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:45 ` [PATCH 23/33] doc: boards: amlogic: update documentation for Radxa Zero Christian Hewitt
2023-03-20 11:45 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 24/33] doc: boards: amlogic: update documentation for S400 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 25/33] doc: boards: amlogic: update documentation for SEI510 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 26/33] doc: boards: amlogic: update documentation for SEI610 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 27/33] doc: boards: amlogic: update documentation for U200 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 28/33] doc: boards: amlogic: update documentation for W400 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 29/33] doc: boards: amlogic: update documentation for WeTek Core2 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 18:40 ` Simon Glass
2023-03-20 18:40 ` Simon Glass
2023-03-21 5:10 ` Christian Hewitt
2023-03-21 5:10 ` Christian Hewitt
2023-04-01 6:33 ` Simon Glass
2023-04-01 6:33 ` Simon Glass
2023-03-20 11:46 ` [PATCH 30/33] doc: boards: amlogic: add documentation for BananaPi CM4IO Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 12:13 ` Neil Armstrong
2023-03-20 12:13 ` Neil Armstrong
2023-03-20 12:23 ` Christian Hewitt
2023-03-20 12:23 ` Christian Hewitt
2023-03-20 12:25 ` neil.armstrong
2023-03-20 12:25 ` Neil Armstrong
2023-03-20 12:25 ` neil.armstrong
2023-03-20 11:46 ` [PATCH 31/33] doc: boards: amlogic: add documentation for BananaPi M5 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 32/33] doc: boards: amlogic: add documentation for GS-King-X Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2023-03-20 11:46 ` [PATCH 33/33] doc: boards: amlogic: add documentation for ODROID-HC4 Christian Hewitt
2023-03-20 11:46 ` Christian Hewitt
2024-04-05 8:03 ` Heinrich Schuchardt
2024-04-05 8:03 ` Heinrich Schuchardt
2023-03-22 14:26 ` [PATCH 00/33] doc: board: amlogic: spring clean-up of Amlogic docs Neil Armstrong
2023-03-22 14:26 ` Neil Armstrong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230320114609.930145-11-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.