January 2020 - U-Boot

[PATCH] net: zynq: Add a note about RX_BUF macro
by Michal Simek 16 Jan '20

16 Jan '20

Record note about reducing number of BDs. Signed-off-by: Michal Simek <michal.simek(a)xilinx.com> --- drivers/net/zynq_gem.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/zynq_gem.c b/drivers/net/zynq_gem.c index 78f94148b411..c3fe8e3c563f 100644 --- a/drivers/net/zynq_gem.c +++ b/drivers/net/zynq_gem.c @@ -173,6 +173,7 @@ struct emac_bd { #endif }; +/* Reduce amount of BUFs if you have limited amount of memory */ #define RX_BUF 32 /* Page table entries are set to 1MB, or multiples of 1MB * (not < 1MB). driver uses less bd's so use 1MB bdspace. -- 2.24.0

2 1

[PATCH 0/8] xilinx: Various DT changes and syncups
by Michal Simek 16 Jan '20

16 Jan '20

Hi, I am sending some patches to fix bugs we found in xilinx release cycle. Also do some syncs to keep kernel/u-boot dts in pseudo sync. Thanks, Michal Jan Kiszka (1): arm64: dts: zcu100-revC: Give wifi some time after power-on Michal Simek (4): arm64: zynqmp: Remove incorrect phy from DT for zcu102-revB up arm64: dts: zynqmp: Fix node names which contain "_" arm64: zynqmp: Sync gpio-controller name location arm64: zynqmp: Sync gem clock nodes with mainline Linux Rob Herring (1): arm64: dts: Remove inconsistent use of 'arm,armv8' compatible string Sudeep Holla (1): arm64: dts: zynqmp: replace gpio-key,wakeup with wakeup-source property Zumeng Chen (1): ARM: dts: zynq: enablement of coresight topology arch/arm/dts/zynq-7000.dtsi | 135 ++++++++++++++++++++++++++++ arch/arm/dts/zynqmp-clk-ccf.dtsi | 22 +++-- arch/arm/dts/zynqmp-clk.dtsi | 4 +- arch/arm/dts/zynqmp-zcu100-revC.dts | 7 +- arch/arm/dts/zynqmp-zcu102-revA.dts | 12 +-- arch/arm/dts/zynqmp-zcu102-revB.dts | 2 +- arch/arm/dts/zynqmp-zcu106-revA.dts | 4 +- arch/arm/dts/zynqmp-zcu111-revA.dts | 4 +- arch/arm/dts/zynqmp.dtsi | 14 +-- 9 files changed, 172 insertions(+), 32 deletions(-) -- 2.24.0

3 11

[PATCH v2 00/19] i2c: designware_ic2: Improvements to timing and general cleanup
by Simon Glass 16 Jan '20

16 Jan '20

This series updates the Designware I2C driver to support reading its timing from the device tree and handling it in units of nanoseconds instead of clock cycles. A new function converts from nanoseconds to the units used by the I2C controller and makes sure that the requested bus speed is not exceeded. This is more accurate than the existing method. The series includes a few smaller clean-ups in the same driver. In addition the v2 series adds enums for i2c speed and updates drivers to use them. There is currently an existing configuration method used just for a few x86 boards (Baytrail). This method is retained but it should be removed in favour of using the device tree. I have not done this in this series since I am not sure of the timings to use. Changes in v2: - Fix 'previde' typo - Add a few more clean-up patches for i2c Simon Glass (19): i2c: designware_i2c: Add more registers i2c: designware_i2c: Don't allow changing IC_CLK i2c: designware_i2c: Include clk.h in the header file i2c: designware_i2c: Rename 'max' speed to 'high' speed i2c: designware_i2c: Use an enum for selected speed mode i2c: designware_i2c: Use an accurate bus clock instead of MHz i2c: designware_i2c: Bring in the binding file i2c: designware_i2c: Read device-tree properties i2c: designware_i2c: Drop scl_sda_cfg parameter i2c: designware_i2c: Put hold config in a struct i2c: designware_i2c: Rewrite timing calculation i2c: designware_i2c: Add spike supression i2c: Add enums for i2c speed and address size i2c: ast_i2c: Update to use standard enums for speed i2c: designware_i2c: Update to use standard enums for speed i2c: kona_i2c: Update to use standard enums for speed i2c: omap: Update to use standard enums for speed i2c: stm32: Update to use standard enums for speed i2c: Update drivers to use enum for speed .../i2c/i2c-designware.txt | 73 +++++ drivers/i2c/ast_i2c.c | 2 +- drivers/i2c/ast_i2c.h | 2 - drivers/i2c/designware_i2c.c | 265 ++++++++++++++---- drivers/i2c/designware_i2c.h | 50 ++-- drivers/i2c/designware_i2c_pci.c | 4 +- drivers/i2c/exynos_hs_i2c.c | 4 +- drivers/i2c/fsl_i2c.c | 3 +- drivers/i2c/i2c-cdns.c | 2 +- drivers/i2c/i2c-uclass.c | 12 +- drivers/i2c/i2c-uniphier-f.c | 2 +- drivers/i2c/i2c-uniphier.c | 2 +- drivers/i2c/imx_lpi2c.c | 8 +- drivers/i2c/kona_i2c.c | 28 +- drivers/i2c/mv_i2c.c | 4 +- drivers/i2c/mvtwsi.c | 5 +- drivers/i2c/omap24xx_i2c.c | 5 +- drivers/i2c/omap24xx_i2c.h | 4 - drivers/i2c/rcar_i2c.c | 2 +- drivers/i2c/rcar_iic.c | 2 +- drivers/i2c/s3c24x0_i2c.c | 4 +- drivers/i2c/sandbox_i2c.c | 3 +- drivers/i2c/stm32f7_i2c.c | 43 ++- include/i2c.h | 26 ++ 24 files changed, 410 insertions(+), 145 deletions(-) create mode 100644 doc/device-tree-bindings/i2c/i2c-designware.txt -- 2.24.1.735.g03f4e72817-goog

4 44

How to debug HW startup?
by Mauro Condarelli 16 Jan '20

16 Jan '20

I managed to brick my target. Situation: I have a board with a paleolithic (1.1.3) version of u-boot. I had been testing by loading in ram from USB: usb reset; fatload usb 0 80010000 u-boot.bin; go 80010000 and everything was ok. I changed a few settings (both defconfigs are attached below) and tried "the real thing" Unfortunately reflashing the actual boot produced a brick. It does not utter a single byte. I will have to reflash the original using an external apparatus (which I don't have here, so I'll have to take target to another location, probably tomorrow morning), but question is: how do I debug such a situation? What could I have done so wrong? As You can see I changed only a few settings: --- configs/vocore_vocore2-ram_defconfig 2020-01-09 16:11:12.568096050 +0100 +++ configs/vocore_vocore2_defconfig 2020-01-09 16:07:10.528267378 +0100 @@ -1,9 +1,12 @@ CONFIG_MIPS=y -CONFIG_SYS_TEXT_BASE=0x80010000 +CONFIG_SYS_TEXT_BASE=0x9c000000 CONFIG_ENV_SIZE=0x00001000 CONFIG_NR_DRAM_BANKS=1 CONFIG_ARCH_MTMIPS=y CONFIG_BOARD_VOCORE2=y +CONFIG_BOOT_ROM=y +CONFIG_ONBOARD_DDR2_SIZE_1024MBIT=y +CONFIG_ONBOARD_DDR2_CHIP_WIDTH_16BIT=y CONFIG_MIPS_BOOT_FDT=y CONFIG_ENV_VARS_UBOOT_CONFIG=y CONFIG_SYS_BOOT_GET_CMDLINE=y ... in a way that's very similar to boards based on the same SoC (linkit-smart-7688 and gardena-smart-gateway-mt7688). In the ancient u-boot I had to remove a header from the RAM version, but this was not needed with current u-boot. Did I forget some step? Any hint welcome Thanks in advance Mauro

3 29

[U-Boot] [PATCH v2 0/2] env: Access Environment in SPI flashes before relocation
by Heiko Schocher 16 Jan '20

16 Jan '20

Add the possibility to access Environment stored in SPI NOR Flash before relocation. This is used in DM/DTS rework for the aristainetos boards. There mutliple DTS are packed into a FIT image and through a variable in the Environment the correct DTS will be selected. For this we need very early access to the Environment. Also may this is good for selecting the console baudrate again through Environment which I think currently does not work for any board based on DM/DTS and with Environment in SPI NOR flash. base: 3ff1ff3ff7 - Merge branch '2019-11-12-migrate-SYS_REDUNDAND_ENVIRONMENT' travis build: https://travis-ci.org/hsdenx/u-boot-test/builds/612239100 (travis has currently some problems...) Therefore I started an build on azure, which worked, see: https://dev.azure.com/hs0298/hs/_build/results?buildId=1&view=results Changes in v2: - patch "env: split env_import_redund into 2 functions" is new in version 2. Idea is to not duplicate too much code as Simon suggested. - env_sf_init_early() always return 0 now. If we do not return 0 in this function, env_set_inited() never get called, which has the consequence that env_load/save/erase never work, because they check if the init bit is set. Heiko Schocher (2): env: split env_import_redund() into 2 functions env: Access Environment in SPI flashes before relocation env/Kconfig | 8 +++++ env/common.c | 40 +++++++++++++++++++------ env/sf.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++ include/env.h | 18 ++++++++++++ 4 files changed, 138 insertions(+), 9 deletions(-) -- 2.21.0

2 6

[PATCH] doc: android: Convert to Sphinx format
by Sam Protsenko 16 Jan '20

16 Jan '20

Convert Android documentation from regular txt format to Sphinx (RST). Also add Android index.rst file and reference it in root index.rst, so that Android documentation is visible. Test: $ make htmldocs $ xdg-open doc/output/index.html Signed-off-by: Sam Protsenko <joe.skb7(a)gmail.com> --- MAINTAINERS | 4 +- cmd/Kconfig | 2 +- doc/android/{ab.txt => ab.rst} | 39 ++--- doc/android/avb2.rst | 133 ++++++++++++++++++ doc/android/avb2.txt | 115 --------------- doc/android/bcb.rst | 100 +++++++++++++ doc/android/bcb.txt | 89 ------------ ...oot-protocol.txt => fastboot-protocol.rst} | 45 +++--- doc/android/{fastboot.txt => fastboot.rst} | 92 ++++++------ doc/android/index.rst | 14 ++ doc/index.rst | 12 ++ test/py/tests/test_android/test_avb.py | 2 +- 12 files changed, 351 insertions(+), 296 deletions(-) rename doc/android/{ab.txt => ab.rst} (52%) create mode 100644 doc/android/avb2.rst delete mode 100644 doc/android/avb2.txt create mode 100644 doc/android/bcb.rst delete mode 100644 doc/android/bcb.txt rename doc/android/{fastboot-protocol.txt => fastboot-protocol.rst} (82%) rename doc/android/{fastboot.txt => fastboot.rst} (79%) create mode 100644 doc/android/index.rst diff --git a/MAINTAINERS b/MAINTAINERS index 438fb225ab..b9e7cd9944 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -56,7 +56,7 @@ R: Sam Protsenko <semen.protsenko(a)linaro.org> S: Maintained F: cmd/ab_select.c F: common/android_ab.c -F: doc/android/ab.txt +F: doc/android/ab.rst F: include/android_ab.h F: test/py/tests/test_android/test_ab.py @@ -65,7 +65,7 @@ M: Igor Opaniuk <igor.opaniuk(a)gmail.com> S: Maintained F: cmd/avb.c F: common/avb_verify.c -F: doc/android/avb2.txt +F: doc/android/avb2.rst F: include/avb_verify.h F: lib/libavb/ F: test/py/tests/test_android/test_avb.py diff --git a/cmd/Kconfig b/cmd/Kconfig index 98d944fb0a..6833185805 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -866,7 +866,7 @@ config CMD_FASTBOOT Android devices. Fastboot requires either the network stack enabled or support for acting as a USB device. - See doc/android/fastboot.txt for more information. + See doc/android/fastboot.rst for more information. config CMD_FDC bool "fdcboot - Boot from floppy device" diff --git a/doc/android/ab.txt b/doc/android/ab.rst similarity index 52% rename from doc/android/ab.txt rename to doc/android/ab.rst index 9f37ed5c58..961895c32e 100644 --- a/doc/android/ab.txt +++ b/doc/android/ab.rst @@ -1,3 +1,5 @@ +.. SPDX-License-Identifier: GPL-2.0+ + Android A/B updates =================== @@ -7,41 +9,44 @@ Overview A/B system updates ensures modern approach for system update. This feature allows one to use two sets (or more) of partitions referred to as slots (normally slot A and slot B). The system runs from the current slot while the -partitions in the unused slot can be updated [1]. +partitions in the unused slot can be updated [1]_. A/B enablement -------------- The A/B updates support can be activated by specifying next options in -your board configuration file: +your board configuration file:: CONFIG_ANDROID_AB=y CONFIG_CMD_AB_SELECT=y The disk space on target device must be partitioned in a way so that each partition which needs to be updated has two or more instances. The name of -each instance must be formed by adding suffixes: _a, _b, _c, etc. -For example: boot_a, boot_b, system_a, system_b, vendor_a, vendor_b. +each instance must be formed by adding suffixes: ``_a``, ``_b``, ``_c``, etc. +For example: ``boot_a``, ``boot_b``, ``system_a``, ``system_b``, ``vendor_a``, +``vendor_b``. -As a result you can use 'ab_select' command to ensure A/B boot process in your +As a result you can use ``ab_select`` command to ensure A/B boot process in your boot script. This command analyzes and processes A/B metadata stored on a -special partition (e.g. "misc") and determines which slot should be used for +special partition (e.g. ``misc``) and determines which slot should be used for booting up. Command usage ------------- +.. code-block:: none + ab_select <slot_var_name> <interface> <dev[:part_number|#part_name]> -for example: +for example:: => ab_select slot_name mmc 1:4 -or +or:: => ab_select slot_name mmc 1#misc -Result: +Result:: => printenv slot_name slot_name=a @@ -49,19 +54,19 @@ Result: Based on this slot information, the current boot partition should be defined, and next kernel command line parameters should be generated: - - androidboot.slot_suffix= - - root= +* ``androidboot.slot_suffix=`` +* ``root=`` -For example: +For example:: androidboot.slot_suffix=_a root=/dev/mmcblk1p12 -A/B metadata is organized according to AOSP reference [2]. On the first system -start with A/B enabled, when 'misc' partition doesn't contain required data, -the default A/B metadata will be created and written to 'misc' partition. +A/B metadata is organized according to AOSP reference [2]_. On the first system +start with A/B enabled, when ``misc`` partition doesn't contain required data, +the default A/B metadata will be created and written to ``misc`` partition. References ---------- -[1] https://source.android.com/devices/tech/ota/ab -[2] bootable/recovery/bootloader_message/include/bootloader_message/bootloader_message.h +.. [1] https://source.android.com/devices/tech/ota/ab +.. [2] https://android.googlesource.com/platform/bootable/recovery/+/refs/tags/and… diff --git a/doc/android/avb2.rst b/doc/android/avb2.rst new file mode 100644 index 0000000000..a072119574 --- /dev/null +++ b/doc/android/avb2.rst @@ -0,0 +1,133 @@ +.. SPDX-License-Identifier: GPL-2.0+ + +Android Verified Boot 2.0 +========================= + +This file contains information about the current support of Android Verified +Boot 2.0 in U-Boot. + +Overview +-------- + +Verified Boot establishes a chain of trust from the bootloader to system images: + +* Provides integrity checking for: + + * Android Boot image: Linux kernel + ramdisk. RAW hashing of the whole + partition is done and the hash is compared with the one stored in + the VBMeta image + * ``system``/``vendor`` partitions: verifying root hash of dm-verity hashtrees + +* Provides capabilities for rollback protection + +Integrity of the bootloader (U-Boot BLOB and environment) is out of scope. + +For additional details check [1]_. + +AVB using OP-TEE (optional) +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +If AVB is configured to use OP-TEE (see `Enable on your board`_) rollback +indexes and device lock state are stored in RPMB. The RPMB partition is managed +by OP-TEE (see [2]_ for details) which is a secure OS leveraging ARM +TrustZone. + +AVB 2.0 U-Boot shell commands +----------------------------- + +Provides CLI interface to invoke AVB 2.0 verification + misc. commands for +different testing purposes:: + + avb init <dev> - initialize avb 2.0 for <dev> + avb verify - run verification process using hash data from vbmeta structure + avb read_rb <num> - read rollback index at location <num> + avb write_rb <num> <rb> - write rollback index <rb> to <num> + avb is_unlocked - returns unlock status of the device + avb get_uuid <partname> - read and print uuid of partition <partname> + avb read_part <partname> <offset> <num> <addr> - read <num> bytes from + partition <partname> to buffer <addr> + avb write_part <partname> <offset> <num> <addr> - write <num> bytes to + <partname> by <offset> using data from <addr> + +Partitions tampering (example) +------------------------------ + +Boot or system/vendor (dm-verity metadata section) is tampered:: + + => avb init 1 + => avb verify + avb_slot_verify.c:175: ERROR: boot: Hash of data does not match digest in + descriptor. + Slot verification result: ERROR_IO + +Vbmeta partition is tampered:: + + => avb init 1 + => avb verify + avb_vbmeta_image.c:206: ERROR: Hash does not match! + avb_slot_verify.c:388: ERROR: vbmeta: Error verifying vbmeta image: + HASH_MISMATCH + Slot verification result: ERROR_IO + +Enable on your board +-------------------- + +The following options must be enabled:: + + CONFIG_LIBAVB=y + CONFIG_AVB_VERIFY=y + CONFIG_CMD_AVB=y + +In addtion optionally if storing rollback indexes in RPMB with help of +OP-TEE:: + + CONFIG_TEE=y + CONFIG_OPTEE=y + CONFIG_OPTEE_TA_AVB=y + CONFIG_SUPPORT_EMMC_RPMB=y + +Then add ``avb verify`` invocation to your android boot sequence of commands, +e.g.:: + + => avb_verify=avb init $mmcdev; avb verify; + => if run avb_verify; then \ + echo AVB verification OK. Continue boot; \ + set bootargs $bootargs $avb_bootargs; \ + else \ + echo AVB verification failed; \ + exit; \ + fi; \ + + => emmc_android_boot= \ + echo Trying to boot Android from eMMC ...; \ + ... \ + run avb_verify; \ + mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; \ + mmc read ${loadaddr} ${boot_start} ${boot_size}; \ + bootm $loadaddr $loadaddr $fdtaddr; \ + +If partitions you want to verify are slotted (have A/B suffixes), then current +slot suffix should be passed to ``avb verify`` sub-command, e.g.:: + + => avb verify _a + +To switch on automatic generation of vbmeta partition in AOSP build, add these +lines to device configuration mk file:: + + BOARD_AVB_ENABLE := true + BOARD_AVB_ALGORITHM := SHA512_RSA4096 + BOARD_BOOTIMAGE_PARTITION_SIZE := <boot partition size> + +After flashing U-Boot don't forget to update environment and write new +partition table:: + + => env default -f -a + => setenv partitions $partitions_android + => env save + => gpt write mmc 1 $partitions_android + +References +---------- + +.. [1] https://android.googlesource.com/platform/external/avb/+/master/README.md +.. [2] https://www.op-tee.org/ diff --git a/doc/android/avb2.txt b/doc/android/avb2.txt deleted file mode 100644 index 48e9297c75..0000000000 --- a/doc/android/avb2.txt +++ /dev/null @@ -1,115 +0,0 @@ -Android Verified Boot 2.0 - -This file contains information about the current support of Android Verified -Boot 2.0 in U-boot - -1. OVERVIEW ---------------------------------- -Verified Boot establishes a chain of trust from the bootloader to system images -* Provides integrity checking for: - - Android Boot image: Linux kernel + ramdisk. RAW hashing of the whole - partition is done and the hash is compared with the one stored in - the VBMeta image - - system/vendor partitions: verifying root hash of dm-verity hashtrees. -* Provides capabilities for rollback protection. - -Integrity of the bootloader (U-boot BLOB and environment) is out of scope. - -For additional details check: -https://android.googlesource.com/platform/external/avb/+/master/README.md - -1.1. AVB using OP-TEE (optional) ---------------------------------- -If AVB is configured to use OP-TEE (see 4. below) rollback indexes and -device lock state are stored in RPMB. The RPMB partition is managed by -OP-TEE (https://www.op-tee.org/) which is a secure OS leveraging ARM -TrustZone. - - -2. AVB 2.0 U-BOOT SHELL COMMANDS ------------------------------------ -Provides CLI interface to invoke AVB 2.0 verification + misc. commands for -different testing purposes: - -avb init <dev> - initialize avb 2.0 for <dev> -avb verify - run verification process using hash data from vbmeta structure -avb read_rb <num> - read rollback index at location <num> -avb write_rb <num> <rb> - write rollback index <rb> to <num> -avb is_unlocked - returns unlock status of the device -avb get_uuid <partname> - read and print uuid of partition <partname> -avb read_part <partname> <offset> <num> <addr> - read <num> bytes from -partition <partname> to buffer <addr> -avb write_part <partname> <offset> <num> <addr> - write <num> bytes to -<partname> by <offset> using data from <addr> - - -3. PARTITIONS TAMPERING (EXAMPLE) ------------------------------------ -Boot or system/vendor (dm-verity metadata section) is tampered: -=> avb init 1 -=> avb verify -avb_slot_verify.c:175: ERROR: boot: Hash of data does not match digest in -descriptor. -Slot verification result: ERROR_IO - -Vbmeta partition is tampered: -=> avb init 1 -=> avb verify -avb_vbmeta_image.c:206: ERROR: Hash does not match! -avb_slot_verify.c:388: ERROR: vbmeta: Error verifying vbmeta image: -HASH_MISMATCH -Slot verification result: ERROR_IO - - -4. ENABLE ON YOUR BOARD ------------------------------------ -The following options must be enabled: -CONFIG_LIBAVB=y -CONFIG_AVB_VERIFY=y -CONFIG_CMD_AVB=y - -In addtion optionally if storing rollback indexes in RPMB with help of -OP-TEE: -CONFIG_TEE=y -CONFIG_OPTEE=y -CONFIG_OPTEE_TA_AVB=y -CONFIG_SUPPORT_EMMC_RPMB=y - -Then add `avb verify` invocation to your android boot sequence of commands, -e.g.: - -=> avb_verify=avb init $mmcdev; avb verify; -=> if run avb_verify; then \ - echo AVB verification OK. Continue boot; \ - set bootargs $bootargs $avb_bootargs; \ - else \ - echo AVB verification failed; \ - exit; \ - fi; \ - -=> emmc_android_boot= \ - echo Trying to boot Android from eMMC ...; \ - ... \ - run avb_verify; \ - mmc read ${fdtaddr} ${fdt_start} ${fdt_size}; \ - mmc read ${loadaddr} ${boot_start} ${boot_size}; \ - bootm $loadaddr $loadaddr $fdtaddr; \ - -If partitions you want to verify are slotted (have A/B suffixes), then current -slot suffix should be passed to 'avb verify' sub-command, e.g.: - -=> avb verify _a - -To switch on automatic generation of vbmeta partition in AOSP build, add these -lines to device configuration mk file: - -BOARD_AVB_ENABLE := true -BOARD_AVB_ALGORITHM := SHA512_RSA4096 -BOARD_BOOTIMAGE_PARTITION_SIZE := <boot partition size> - -After flashing U-boot don't forget to update environment and write new -partition table: -=> env default -f -a -=> setenv partitions $partitions_android -=> env save -=> gpt write mmc 1 $partitions_android diff --git a/doc/android/bcb.rst b/doc/android/bcb.rst new file mode 100644 index 0000000000..8861608300 --- /dev/null +++ b/doc/android/bcb.rst @@ -0,0 +1,100 @@ +.. SPDX-License-Identifier: GPL-2.0+ + +Android Bootloader Control Block (BCB) +====================================== + +The purpose behind this file is to: + +* give an overview of BCB w/o duplicating public documentation +* describe the main BCB use-cases which concern U-Boot +* reflect current support status in U-Boot +* mention any relevant U-Boot build-time tunables +* precisely exemplify one or more use-cases + +Additions and fixes are welcome! + +Overview +-------- + +Bootloader Control Block (BCB) is a well established term/acronym in +the Android namespace which refers to a location in a dedicated raw +(i.e. FS-unaware) flash (e.g. eMMC) partition, usually called ``misc``, +which is used as media for exchanging messages between Android userspace +(particularly recovery [1]_) and an Android-capable bootloader. + +On higher level, BCB provides a way to implement a subset of Android +Bootloader Requirements [2]_, amongst which are: + +* Android-specific bootloader flow [3]_ +* Get the "reboot reason" (and act accordingly) [4]_ +* Get/pass a list of commands from/to recovery [1]_ +* TODO + + +'bcb'. Shell command overview +----------------------------- + +The ``bcb`` command provides a CLI to facilitate the development of the +requirements enumerated above. Below is the command's help message:: + + => bcb + bcb - Load/set/clear/test/dump/store Android BCB fields + + Usage: + bcb load <dev> <part> - load BCB from mmc <dev>:<part> + bcb set <field> <val> - set BCB <field> to <val> + bcb clear [<field>] - clear BCB <field> or all fields + bcb test <field> <op> <val> - test BCB <field> against <val> + bcb dump <field> - dump BCB <field> + bcb store - store BCB back to mmc + + Legend: + <dev> - MMC device index containing the BCB partition + <part> - MMC partition index or name containing the BCB + <field> - one of {command,status,recovery,stage,reserved} + <op> - the binary operator used in 'bcb test': + '=' returns true if <val> matches the string stored in <field> + '~' returns true if <val> matches a subset of <field>'s string + <val> - string/text provided as input to bcb {set,test} + NOTE: any ':' character in <val> will be replaced by line feed + during 'bcb set' and used as separator by upper layers + + +'bcb'. Example of getting reboot reason +--------------------------------------- + +.. code-block:: bash + + if bcb load 1 misc; then + # valid BCB found + if bcb test command = bootonce-bootloader; then + bcb clear command; bcb store; + # do the equivalent of AOSP ${fastbootcmd} + # i.e. call fastboot + else if bcb test command = boot-recovery; then + bcb clear command; bcb store; + # do the equivalent of AOSP ${recoverycmd} + # i.e. do anything required for booting into recovery + else + # boot Android OS normally + fi + else + # corrupted/non-existent BCB + # report error or boot non-Android OS (platform-specific) + fi + + +Enable on your board +-------------------- + +The following Kconfig options must be enabled:: + + CONFIG_PARTITIONS=y + CONFIG_MMC=y + CONFIG_BCB=y + +.. [1] https://android.googlesource.com/platform/bootable/recovery +.. [2] https://source.android.com/devices/bootloader +.. [3] https://patchwork.ozlabs.org/patch/746835/ + ("[U-Boot,5/6] Initial support for the Android Bootloader flow") +.. [4] https://source.android.com/devices/bootloader/boot-reason diff --git a/doc/android/bcb.txt b/doc/android/bcb.txt deleted file mode 100644 index 7b7177cacf..0000000000 --- a/doc/android/bcb.txt +++ /dev/null @@ -1,89 +0,0 @@ -Android Bootloader Control Block (BCB) - -The purpose behind this file is to: - - give an overview of BCB w/o duplicating public documentation - - describe the main BCB use-cases which concern U-Boot - - reflect current support status in U-Boot - - mention any relevant U-Boot build-time tunables - - precisely exemplify one or more use-cases - -Additions and fixes are welcome! - - -1. OVERVIEW ---------------------------------- -Bootloader Control Block (BCB) is a well established term/acronym in -the Android namespace which refers to a location in a dedicated raw -(i.e. FS-unaware) flash (e.g. eMMC) partition, usually called "misc", -which is used as media for exchanging messages between Android userspace -(particularly recovery [1]) and an Android-capable bootloader. - -On higher level, BCB provides a way to implement a subset of Android -Bootloader Requirements [2], amongst which are: - - Android-specific bootloader flow [3] - - Get the "reboot reason" (and act accordingly) [4] - - Get/pass a list of commands from/to recovery [1] - - TODO - - -2. 'BCB'. SHELL COMMAND OVERVIEW ------------------------------------ -The 'bcb' command provides a CLI to facilitate the development of the -requirements enumerated above. Below is the command's help message: - -=> bcb -bcb - Load/set/clear/test/dump/store Android BCB fields - -Usage: -bcb load <dev> <part> - load BCB from mmc <dev>:<part> -bcb set <field> <val> - set BCB <field> to <val> -bcb clear [<field>] - clear BCB <field> or all fields -bcb test <field> <op> <val> - test BCB <field> against <val> -bcb dump <field> - dump BCB <field> -bcb store - store BCB back to mmc - -Legend: -<dev> - MMC device index containing the BCB partition -<part> - MMC partition index or name containing the BCB -<field> - one of {command,status,recovery,stage,reserved} -<op> - the binary operator used in 'bcb test': - '=' returns true if <val> matches the string stored in <field> - '~' returns true if <val> matches a subset of <field>'s string -<val> - string/text provided as input to bcb {set,test} - NOTE: any ':' character in <val> will be replaced by line feed - during 'bcb set' and used as separator by upper layers - - -3. 'BCB'. EXAMPLE OF GETTING REBOOT REASON ------------------------------------ -if bcb load 1 misc; then - # valid BCB found - if bcb test command = bootonce-bootloader; then - bcb clear command; bcb store; - # do the equivalent of AOSP ${fastbootcmd} - # i.e. call fastboot - else if bcb test command = boot-recovery; then - bcb clear command; bcb store; - # do the equivalent of AOSP ${recoverycmd} - # i.e. do anything required for booting into recovery - else - # boot Android OS normally - fi -else - # corrupted/non-existent BCB - # report error or boot non-Android OS (platform-specific) -fi - - -4. ENABLE ON YOUR BOARD ------------------------------------ -The following Kconfig options must be enabled: -CONFIG_PARTITIONS=y -CONFIG_MMC=y -CONFIG_BCB=y - -[1] https://android.googlesource.com/platform/bootable/recovery -[2] https://source.android.com/devices/bootloader -[3] https://patchwork.ozlabs.org/patch/746835/ - ("[U-Boot,5/6] Initial support for the Android Bootloader flow") -[4] https://source.android.com/devices/bootloader/boot-reason diff --git a/doc/android/fastboot-protocol.txt b/doc/android/fastboot-protocol.rst similarity index 82% rename from doc/android/fastboot-protocol.txt rename to doc/android/fastboot-protocol.rst index e9e7166a26..e723659e49 100644 --- a/doc/android/fastboot-protocol.txt +++ b/doc/android/fastboot-protocol.rst @@ -1,12 +1,13 @@ -FastBoot Version 0.4 ----------------------- +.. SPDX-License-Identifier: GPL-2.0+ + +FastBoot Version 0.4 +==================== The fastboot protocol is a mechanism for communicating with bootloaders over USB. It is designed to be very straightforward to implement, to allow it to be used across a wide range of devices and from hosts running Linux, Windows, or OSX. - Basic Requirements ------------------ @@ -66,31 +67,33 @@ Transport and Framing Example Session --------------- -Host: "getvar:version" request version variable +.. code-block:: none + + Host: "getvar:version" request version variable -Client: "OKAY0.4" return version "0.4" + Client: "OKAY0.4" return version "0.4" -Host: "getvar:nonexistant" request some undefined variable + Host: "getvar:nonexistant" request some undefined variable -Client: "OKAY" return value "" + Client: "OKAY" return value "" -Host: "download:00001234" request to send 0x1234 bytes of data + Host: "download:00001234" request to send 0x1234 bytes of data -Client: "DATA00001234" ready to accept data + Client: "DATA00001234" ready to accept data -Host: < 0x1234 bytes > send data + Host: < 0x1234 bytes > send data -Client: "OKAY" success + Client: "OKAY" success -Host: "flash:bootloader" request to flash the data to the bootloader + Host: "flash:bootloader" request to flash the data to the bootloader -Client: "INFOerasing flash" indicate status / progress - "INFOwriting flash" - "OKAY" indicate success + Client: "INFOerasing flash" indicate status / progress + "INFOwriting flash" + "OKAY" indicate success -Host: "powerdown" send a command + Host: "powerdown" send a command -Client: "FAILunknown command" indicate failure + Client: "FAILunknown command" indicate failure Command Reference @@ -105,6 +108,8 @@ Command Reference specification. OEM-specific commands should not begin with a lowercase letter, to prevent incompatibilities with future specs. +.. code-block:: none + "getvar:%s" Read a config/version variable from the bootloader. The variable contents will be returned after the OKAY response. @@ -139,16 +144,14 @@ Command Reference "powerdown" Power off the device. - - Client Variables ---------------- -The "getvar:%s" command is used to read client variables which +The ``getvar:%s`` command is used to read client variables which represent various information about the device and the software on it. -The various currently defined names are: +The various currently defined names are:: version Version of FastBoot protocol supported. It should be "0.3" for this document. diff --git a/doc/android/fastboot.txt b/doc/android/fastboot.rst similarity index 79% rename from doc/android/fastboot.txt rename to doc/android/fastboot.rst index 9de13223f8..de3f6c37d7 100644 --- a/doc/android/fastboot.txt +++ b/doc/android/fastboot.rst @@ -1,12 +1,12 @@ -================ +.. SPDX-License-Identifier: GPL-2.0+ + Android Fastboot ================ Overview -======== +-------- -The protocol that is used over USB and UDP is described in -``doc/android/fastboot-protocol.txt``. +The protocol that is used over USB and UDP is described in [1]_. The current implementation supports the following standard commands: @@ -22,25 +22,23 @@ The current implementation supports the following standard commands: The following OEM commands are supported (if enabled): -- oem format - this executes ``gpt write mmc %x $partitions`` +- ``oem format`` - this executes ``gpt write mmc %x $partitions`` Support for both eMMC and NAND devices is included. Client installation -=================== +------------------- The counterpart to this is the fastboot client which can be found in Android's ``platform/system/core`` repository in the fastboot folder. It runs on Windows, Linux and OSX. The fastboot client is -part of the Android SDK Platform-Tools and can be downloaded from: - -https://developer.android.com/studio/releases/platform-tools +part of the Android SDK Platform-Tools and can be downloaded from [2]_. Board specific -============== +-------------- USB configuration ------------------ +^^^^^^^^^^^^^^^^^ The fastboot gadget relies on the USB download gadget, so the following options must be configured: @@ -57,7 +55,7 @@ supported by the fastboot client. The list of vendor IDs supported can be found in the fastboot client source code. General configuration ---------------------- +^^^^^^^^^^^^^^^^^^^^^ The fastboot protocol requires a large memory buffer for downloads. This buffer should be as large as possible for a @@ -67,46 +65,46 @@ may be overridden on the fastboot command line using ``-l`` and ``-s``. Fastboot environment variables -============================== +------------------------------ Partition aliases ------------------ +^^^^^^^^^^^^^^^^^ Fastboot partition aliases can also be defined for devices where GPT -limitations prevent user-friendly partition names such as "boot", "system" -and "cache". Or, where the actual partition name doesn't match a standard +limitations prevent user-friendly partition names such as ``boot``, ``system`` +and ``cache``. Or, where the actual partition name doesn't match a standard partition name used commonly with fastboot. The current implementation checks aliases when accessing partitions by name (flash_write and erase functions). To define a partition alias -add an environment variable similar to: +add an environment variable similar to:: -``fastboot_partition_alias_<alias partition name>=<actual partition name>`` + fastboot_partition_alias_<alias partition name>=<actual partition name> -for example: +for example:: -``fastboot_partition_alias_boot=LNX`` + fastboot_partition_alias_boot=LNX Variable overrides ------------------- +^^^^^^^^^^^^^^^^^^ Variables retrived through ``getvar`` can be overridden by defining environment variables of the form ``fastboot.<variable>``. These are looked up first so can be used to override values which would otherwise be returned. Using this mechanism you can also return types for NAND filesystems, as the fully parameterised variable is looked -up, e.g. +up, e.g.:: -``fastboot.partition-type:boot=jffs2`` + fastboot.partition-type:boot=jffs2 Boot command ------------- +^^^^^^^^^^^^ -When executing the fastboot ``boot`` command, if ``fastboot_bootcmd`` is set then -that will be executed in place of ``bootm <CONFIG_FASTBOOT_BUF_ADDR>``. +When executing the fastboot ``boot`` command, if ``fastboot_bootcmd`` is set +then that will be executed in place of ``bootm <CONFIG_FASTBOOT_BUF_ADDR>``. Partition Names -=============== +--------------- The Fastboot implementation in U-Boot allows to write images into disk partitions. Target partitions are referred on the host computer by @@ -115,11 +113,11 @@ their names. For GPT/EFI the respective partition name is used. For MBR the partitions are referred by generic names according to the -following schema: +following schema:: - <device type><device index letter><partition index> + <device type><device index letter><partition index> -Example: ``hda3``, ``sdb1``, ``usbda1`` +Example: ``hda3``, ``sdb1``, ``usbda1``. The device type is as follows: @@ -135,7 +133,7 @@ controller, SD/MMC controller) or disk index. The partition index starts from ``1`` and describes the partition number on the particular device. Writing Partition Table -======================= +----------------------- Fastboot also allows to write the partition table to the media. This can be done by writing the respective partition table image to a special target @@ -148,34 +146,26 @@ configuration options: CONFIG_FASTBOOT_MBR_NAME In Action -========= +--------- -Enter into fastboot by executing the fastboot command in U-Boot for either USB: - -:: +Enter into fastboot by executing the fastboot command in U-Boot for either USB:: => fastboot usb 0 -or UDP: - -:: +or UDP:: => fastboot udp link up on port 0, speed 100, full duplex Using ethernet@4a100000 device Listening for fastboot command on 192.168.0.102 -On the client side you can fetch the bootloader version for instance: - -:: +On the client side you can fetch the bootloader version for instance:: $ fastboot getvar version-bootloader version-bootloader: U-Boot 2019.07-rc4-00240-g00c9f2a2ec Finished. Total time: 0.005s -or initiate a reboot: - -:: +or initiate a reboot:: $ fastboot reboot @@ -184,9 +174,7 @@ and once the client comes back, the board should reset. You can also specify a kernel image to boot. You have to either specify the an image in Android format *or* pass a binary kernel and let the fastboot client wrap the Android suite around it. On OMAP for instance you -take zImage kernel and pass it to the fastboot client: - -:: +take zImage kernel and pass it to the fastboot client:: $ fastboot -b 0x80000000 -c "console=ttyO2 earlyprintk root=/dev/ram0 mem=128M" boot zImage creating boot image... @@ -197,9 +185,7 @@ take zImage kernel and pass it to the fastboot client: OKAY [ -0.000s] finished. total time: 2.766s -and on the U-Boot side you should see: - -:: +and on the U-Boot side you should see:: Starting download of 1847296 bytes ........................................................ @@ -212,3 +198,9 @@ and on the U-Boot side you should see: OK Starting kernel ... + +References +---------- + +.. [1] :doc:`fastboot-protocol` +.. [2] https://developer.android.com/studio/releases/platform-tools diff --git a/doc/android/index.rst b/doc/android/index.rst new file mode 100644 index 0000000000..225d6f125a --- /dev/null +++ b/doc/android/index.rst @@ -0,0 +1,14 @@ +.. SPDX-License-Identifier: GPL-2.0+ + +Android-specific doc +==================== + +.. toctree:: + :maxdepth: 2 + + ab + avb2 + bcb + boot-image + fastboot-protocol + fastboot diff --git a/doc/index.rst b/doc/index.rst index 206a04590f..cd98be6cc5 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -86,6 +86,18 @@ organized in a vendor subdirectory. board/index +Android-specific doc +-------------------- + +These books provide information about booting the Android OS from U-Boot, +manipulating Android images from U-Boot shell and discusses other +Android-specific features available in U-Boot. + +.. toctree:: + :maxdepth: 2 + + android/index + Indices and tables ================== diff --git a/test/py/tests/test_android/test_avb.py b/test/py/tests/test_android/test_avb.py index 20ccaf6712..a04a7ff264 100644 --- a/test/py/tests/test_android/test_avb.py +++ b/test/py/tests/test_android/test_avb.py @@ -8,7 +8,7 @@ This tests Android Verified Boot 2.0 support in U-boot: For additional details about how to build proper vbmeta partition -check doc/android/avb2.txt +check doc/android/avb2.rst For configuration verification: - Corrupt boot partition and check for failure -- 2.24.0

3 3

Pull request for UEFI sub-system for efi-2020-04-rc1-2
by Heinrich Schuchardt 15 Jan '20

15 Jan '20

The following changes since commit 88366b96ee0d8640b2af53e4026dbaeed0fab5e0: travis: Switch to QEMU v4.2.0 globally (2020-01-11 08:07:03 -0500) are available in the Git repository at: https://gitlab.denx.de/u-boot/custodians/u-boot-efi.git tags/efi-2020-04-rc1-2 for you to fetch changes up to faadc04180ef05acfd6523b49a2abf37ae61afad: efi_loader: imply VIDEO_ANSI (2020-01-15 00:51:51 +0100) Gitlab CI and Travis CI showed no problems: https://gitlab.denx.de/u-boot/custodians/u-boot-efi/pipelines/1851 https://travis-ci.org/xypron2/u-boot/builds/637171603 Primary key fingerprint: 6DC4 F9C7 1F29 A6FA 06B7 6D33 C481 DBBC 2C05 1AC4 ---------------------------------------------------------------- Pull request for UEFI sub-system for efi-2020-04-rc1-2 Bug fixes for the UEFI sub-system are provided: * imply VIDEO_ANSI for correct cursor positioning and colors * fix issues in the UEFI block device driver * add missing documentation ---------------------------------------------------------------- Heinrich Schuchardt (6): efi_loader: document functions in efi_rng.c efi_loader: describe returning of control efi_selftest: enable CONFIG_CMD_POWEROFF efi_driver: fix efi_uc_stop() efi_driver: debug output efi_uc_start, efi_uc_stop efi_loader: imply VIDEO_ANSI doc/api/efi.rst | 6 +++++ lib/efi_driver/efi_uclass.c | 11 +++++---- lib/efi_loader/Kconfig | 1 + lib/efi_loader/efi_boottime.c | 8 +++---- lib/efi_loader/efi_rng.c | 35 ++++++++++++++++++++++++++++ lib/efi_selftest/Kconfig | 1 + lib/efi_selftest/efi_selftest_block_device.c | 4 ++-- 7 files changed, 55 insertions(+), 11 deletions(-)

2 1

eMMC wipe
by Ismael Rangel 15 Jan '20

15 Jan '20

Hi, Current U-Boot repo supports eMMC erase command with argument 0x00000000 (MMC_ERASE_ARG). https://github.com/u-boot/u-boot/blob/master/drivers/mmc/mmc_write.c#L53 cmd.cmdidx = MMC_CMD_ERASE; cmd.cmdarg = MMC_ERASE_ARG; cmd.resp_type = MMC_RSP_R1b; Argument 0x80000000 (MMC_SECURE_ERASE_ARG) is also defined but is not used in any function. Latest eMMC 5.1 devices support a few more data wipe and reorder features e.g. Trim, Discard and Sanitize. Is there any plan to add these features? Thanks, Ismael.

1 0

[PATCH 0/3] RISC-V SiFive FU540 support SPL
by Pragnesh Patel 15 Jan '20

15 Jan '20

This series add support for SPL to FU540. This series depends on https://patchwork.ozlabs.org/patch/1196703/ (riscv: dts: Add hifive-unleashed-a00 dts from Linux) U-Boot SPL can boot from L2 LIM (0x0800_0000) and jump to OpenSBI(FW_DYNAMIC firmware) and U-Boot proper from MMC devices. How to test this patch: 1) Go to OpenSBI-dir : make PLATFORM=sifive/fu540 O=build_dir I=install_dir FW_DYNAMIC=y install 2) cp install_dir/platform/sifive/fu540/firmware/fw_dynamic.bin <u-boot-dir>/ 3) Change to u-boot-dir 4) make sifive_fu540_spl_defconfig 5) make all 6) SD card partition which contains "fw_payload.bin" previously /dev/sdc1 - SiFive bare-metal (or s ->5202) should be now of /dev/sdc1 - 8300 Linux filesystem. 6) sudo dd if=spl/u-boot-spl.bin of=/dev/sdc4 bs=1M 7) sudo dd if=u-boot.itb of=/dev/sdc1 bs=1M Following are the boot messages on FU540 five cores SMP platform: HiFive-U serial #: 05374581 U-Boot SPL 2020.01-rc5-00007-g4a96c4e4ac-dirty (Dec 23 2019 - 16:49:18 +0530) Trying to boot from MMC1 U-Boot 2020.01-rc5-00007-g4a96c4e4ac-dirty (Dec 23 2019 - 16:49:18 +0530) CPU: rv64imafdc Model: SiFive HiFive Unleashed A00 DRAM: 8 GiB MMC: spi@10050000:mmc@0: 0 In: serial@10010000 Out: serial@10010000 Err: serial@10010000 Net: eth0: ethernet@10090000 Hit any key to stop autoboot: 0 => => setenv serverip 172.16.35.74;setenv ipaddr 172.16.35.40;tftpboot 0x83000000 fit.itb;bootm 0x83000000 ethernet@10090000: PHY present at 0 ethernet@10090000: Starting autonegotiation... ethernet@10090000: Autonegotiation complete ethernet@10090000: link up, 100Mbps full-duplex (lpa: 0x41e1) Using ethernet@10090000 device TFTP from server 172.16.35.74; our IP address is 172.16.35.40 Filename 'fit.itb'. Load address: 0x83000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################### 876 KiB/s done Bytes transferred = 13823823 (d2ef4f hex) ## Loading kernel from FIT Image at 83000000 ... Using 'config-1' configuration Trying 'kernel@1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: uncompressed Data Start: 0x830000d8 Data Size: 9247260 Bytes = 8.8 MiB Architecture: RISC-V OS: Linux Load Address: 0x80200000 Entry Point: 0x80200000 Verifying Hash Integrity ... OK ## Loading ramdisk from FIT Image at 83000000 ... Using 'config-1' configuration Trying 'ramdisk@1' ramdisk subimage Description: ramdisk Type: RAMDisk Image Compression: gzip compressed Data Start: 0x838d3378 Data Size: 4568674 Bytes = 4.4 MiB Architecture: RISC-V OS: Linux Load Address: 0x82000000 Entry Point: unavailable Verifying Hash Integrity ... OK Loading ramdisk from 0x838d3378 to 0x82000000 WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file! ## Loading fdt from FIT Image at 83000000 ... Using 'config-1' configuration Trying 'fdt@1' fdt subimage Description: unavailable Type: Flat Device Tree Compression: uncompressed Data Start: 0x838d1b80 Data Size: 6023 Bytes = 5.9 KiB Architecture: RISC-V Verifying Hash Integrity ... OK Booting using the fdt blob at 0x838d1b80 Loading Kernel Image Using Device Tree in place at 00000000838d1b80, end 00000000838d6306 Starting kernel ... [ 0.000000] OF: fdt: Ignoring memory range 0x80000000 - 0x80200000 [ 0.000000] Linux version 5.3.0-13236-g97f9a3c4eee5 (pragneshp@sachinj2-OptiPlex-7010) (gcc version 8.2.0 (Buildroot 2018.11-rc2-00003-ga0787e9 [ 0.000000] earlycon: sifive0 at MMIO 0x0000000010010000 (options '') [ 0.000000] printk: bootconsole [sifive0] enabled [ 0.000000] Initial ramdisk at: 0x(____ptrval____) (4568674 bytes) [ 0.000000] Zone ranges: [ 0.000000] DMA32 [mem 0x0000000080200000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x000000027fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000080200000-0x000000027fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000080200000-0x000000027fffffff] [ 0.000000] software IO TLB: mapped [mem 0xfbfff000-0xfffff000] (64MB) [ 0.000000] CPU with hartid=0 is not available [ 0.000000] CPU with hartid=0 is not available [ 0.000000] elf_hwcap is 0x112d [ 0.000000] percpu: Embedded 17 pages/cpu s30680 r8192 d30760 u69632 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 2067975 [ 0.000000] Kernel command line: earlycon=sifive,0x10010000 console=ttySIF0,115200 [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Sorting __ex_table... [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] Memory: 8179828K/8386560K available (6081K kernel code, 388K rwdata, 2025K rodata, 209K init, 307K bss, 206732K reserved, 0K cma-r) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 0, nr_irqs: 0, preallocated irqs: 0 [ 0.000000] plic: mapped 53 interrupts with 4 handlers for 9 contexts. [ 0.000000] riscv_timer_init_dt: Registering clocksource cpuid [0] hartid [1] [ 0.000000] clocksource: riscv_clocksource: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns [ 0.000007] sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns [ 0.008475] Console: colour dummy device 80x25 [ 0.012817] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=4000) [ 0.022843] pid_max: default: 32768 minimum: 301 [ 0.027914] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.035329] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.044790] rcu: Hierarchical SRCU implementation. [ 0.049254] smp: Bringing up secondary CPUs ... [ 0.055029] smp: Brought up 1 node, 4 CPUs [ 0.059661] devtmpfs: initialized [ 0.063822] random: get_random_u32 called from bucket_table_alloc.isra.29+0x4e/0x160 with crng_init=0 [ 0.072594] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.082004] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.089515] NET: Registered protocol family 16 [ 0.105942] vgaarb: loaded [ 0.108197] SCSI subsystem initialized [ 0.111980] usbcore: registered new interface driver usbfs [ 0.117135] usbcore: registered new interface driver hub [ 0.122519] usbcore: registered new device driver usb [ 0.128108] clocksource: Switched to clocksource riscv_clocksource [ 0.140305] NET: Registered protocol family 2 [ 0.144473] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) [ 0.152647] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 0.162267] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 0.172183] TCP: Hash tables configured (established 65536 bind 65536) [ 0.178366] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.185164] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 0.192575] NET: Registered protocol family 1 [ 0.196784] RPC: Registered named UNIX socket transport module. [ 0.202175] RPC: Registered udp transport module. [ 0.206857] RPC: Registered tcp transport module. [ 0.211533] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.217963] PCI: CLS 0 bytes, default 64 [ 0.222163] Unpacking initramfs... [ 0.578809] Freeing initrd memory: 4460K [ 0.582984] workingset: timestamp_bits=62 max_order=21 bucket_order=0 [ 0.596653] NFS: Registering the id_resolver key type [ 0.600998] Key type id_resolver registered [ 0.605099] Key type id_legacy registered [ 0.609098] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.615937] 9p: Installing v9fs 9p2000 file system support [ 0.621588] NET: Registered protocol family 38 [ 0.625709] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 0.633058] io scheduler mq-deadline registered [ 0.637568] io scheduler kyber registered [ 0.685647] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 0.692241] 10010000.serial: ttySIF0 at MMIO 0x10010000 (irq = 4, base_baud = 0) is a SiFive UART v0 [ 0.700625] printk: console [ttySIF0] enabled [ 0.700625] printk: console [ttySIF0] enabled [ 0.709285] printk: bootconsole [sifive0] disabled [ 0.709285] printk: bootconsole [sifive0] disabled [ 0.719077] 10011000.serial: ttySIF1 at MMIO 0x10011000 (irq = 1, base_baud = 0) is a SiFive UART v0 [ 0.728423] [drm] radeon kernel modesetting enabled. [ 0.745353] loop: module loaded [ 0.748269] sifive_spi 10040000.spi: mapped; irq=3, cs=1 [ 0.753551] sifive_spi 10050000.spi: mapped; irq=5, cs=1 [ 0.758874] libphy: Fixed MDIO Bus: probed [ 0.762947] macb 10090000.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 0.769704] macb: GEM doesn't support hardware ptp. [ 0.774587] libphy: MACB_mii_bus: probed [ 0.940397] Microsemi VSC8541 SyncE 10090000.ethernet-ffffffff:00: attached PHY driver [Microsemi VSC8541 SyncE] (mii_bus:phy_addr=10090000.et) [ 0.954941] macb 10090000.ethernet eth0: Cadence GEM rev 0x10070109 at 0x10090000 irq 6 (70:b3:d5:b7:f5:81) [ 0.964744] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 0.970464] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 0.976458] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.982880] ehci-pci: EHCI PCI platform driver [ 0.987336] ehci-platform: EHCI generic platform driver [ 0.992593] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.998695] ohci-pci: OHCI PCI platform driver [ 1.003140] ohci-platform: OHCI generic platform driver [ 1.008604] usbcore: registered new interface driver uas [ 1.013666] usbcore: registered new interface driver usb-storage [ 1.019742] mousedev: PS/2 mouse device common for all mice [ 1.050616] mmc_spi spi1.0: SD/MMC host mmc0, no DMA, no WP, no poweroff, cd polling [ 1.057762] usbcore: registered new interface driver usbhid [ 1.063145] usbhid: USB HID core driver [ 1.067858] NET: Registered protocol family 10 [ 1.072475] Segment Routing with IPv6 [ 1.075421] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 1.081800] NET: Registered protocol family 17 [ 1.085918] 9pnet: Installing 9P2000 support [ 1.090013] Key type dns_resolver registered [ 1.096438] Freeing unused kernel memory: 208K [ 1.100122] This architecture does not have kernel memory protection. [ 1.106536] Run /init as init process Starting syslogd: OK Starting klogd: OK Starting mdev... /etc/init.d/S10mdev: line 9: can't create /proc/sys/kernel/hotplug: nonexistent directory [ 1.167972] mmc0: host does not support reading read-only switch, assuming write-enable [ 1.175230] mmc0: new SDHC card on SPI [ 1.180257] mmcblk0: mmc0:0000 SC16G 14.8 GiB [ 1.214677] mmcblk0: p1 p2 p4 modprobe: can't change directory to '/lib/modules': No such file or directory Initializing random number generator... [ 1.666442] random: dd: uninitialized urandom read (512 bytes read) done. Starting network: udhcpc: started, v1.29.3 udhcpc: sending discover [ 3.756777] macb 10090000.ethernet eth0: link up (100/Full) [ 3.761593] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready udhcpc: sending discover udhcpc: sending select for 172.16.35.21 udhcpc: lease of 172.16.35.21 obtained, lease time 28800 deleting routers adding dns 172.16.34.150 adding dns 172.16.24.25 OK Starting dropbear sshd: [ 4.457029] random: dropbear: uninitialized urandom read (32 bytes read) OK Welcome to Buildroot buildroot login: root Password: # Pragnesh Patel (3): riscv: Add place-holder for FU540 clk and gpio riscv: Add FU540 specific includes riscv: sifive: fu540: add SPL configuration arch/riscv/cpu/u-boot-spl.lds | 1 + arch/riscv/dts/fu540-c000-u-boot.dtsi | 65 + .../dts/hifive-unleashed-a00-u-boot.dtsi | 24 + arch/riscv/include/asm/arch-fu540/cache.h | 43 + arch/riscv/include/asm/arch-fu540/clint.h | 20 + arch/riscv/include/asm/arch-fu540/clk.h | 14 + arch/riscv/include/asm/arch-fu540/gpio.h | 42 + arch/riscv/include/asm/arch-fu540/i2c.h | 48 + arch/riscv/include/asm/arch-fu540/otp.h | 80 ++ arch/riscv/include/asm/arch-fu540/spi.h | 86 ++ arch/riscv/include/asm/arch-fu540/uart.h | 35 + arch/riscv/include/asm/arch-generic/gpio.h | 32 +- arch/riscv/include/asm/csr.h | 2 + board/sifive/fu540/Kconfig | 11 + board/sifive/fu540/MAINTAINERS | 1 + board/sifive/fu540/Makefile | 6 + board/sifive/fu540/ememoryotp.c | 143 ++ board/sifive/fu540/fu540.c | 31 +- board/sifive/fu540/include/ccache.h | 47 + board/sifive/fu540/include/clkutils.h | 75 + board/sifive/fu540/include/ddrregs.h | 622 +++++++++ board/sifive/fu540/include/ememoryotp.h | 24 + board/sifive/fu540/include/fu540-memory-map.h | 427 ++++++ board/sifive/fu540/include/i2c.h | 49 + board/sifive/fu540/include/regconfig-ctl.h | 274 ++++ board/sifive/fu540/include/regconfig-phy.h | 1224 +++++++++++++++++ board/sifive/fu540/include/spi.h | 233 ++++ board/sifive/fu540/include/uart.h | 54 + board/sifive/fu540/include/ux00ddr.h | 268 ++++ board/sifive/fu540/include/ux00prci.h | 206 +++ board/sifive/fu540/spl.c | 321 +++++ board/sifive/fu540/uart.c | 64 + configs/sifive_fu540_spl_defconfig | 23 + include/configs/sifive-fu540.h | 17 + lib/Makefile | 1 + 35 files changed, 4583 insertions(+), 30 deletions(-) create mode 100644 arch/riscv/dts/fu540-c000-u-boot.dtsi create mode 100644 arch/riscv/dts/hifive-unleashed-a00-u-boot.dtsi create mode 100644 arch/riscv/include/asm/arch-fu540/cache.h create mode 100644 arch/riscv/include/asm/arch-fu540/clint.h create mode 100644 arch/riscv/include/asm/arch-fu540/clk.h create mode 100644 arch/riscv/include/asm/arch-fu540/gpio.h create mode 100644 arch/riscv/include/asm/arch-fu540/i2c.h create mode 100644 arch/riscv/include/asm/arch-fu540/otp.h create mode 100644 arch/riscv/include/asm/arch-fu540/spi.h create mode 100644 arch/riscv/include/asm/arch-fu540/uart.h create mode 100644 board/sifive/fu540/ememoryotp.c create mode 100644 board/sifive/fu540/include/ccache.h create mode 100644 board/sifive/fu540/include/clkutils.h create mode 100644 board/sifive/fu540/include/ddrregs.h create mode 100644 board/sifive/fu540/include/ememoryotp.h create mode 100644 board/sifive/fu540/include/fu540-memory-map.h create mode 100644 board/sifive/fu540/include/i2c.h create mode 100644 board/sifive/fu540/include/regconfig-ctl.h create mode 100644 board/sifive/fu540/include/regconfig-phy.h create mode 100644 board/sifive/fu540/include/spi.h create mode 100644 board/sifive/fu540/include/uart.h create mode 100644 board/sifive/fu540/include/ux00ddr.h create mode 100644 board/sifive/fu540/include/ux00prci.h create mode 100644 board/sifive/fu540/spl.c create mode 100644 board/sifive/fu540/uart.c create mode 100644 configs/sifive_fu540_spl_defconfig -- 2.17.1

7 18

[GIT PULL] Pull request: u-boot-imx u-boot-imx-20200115
by Stefano Babic 15 Jan '20

15 Jan '20

Hi Tom, please pull from i.MX, thanks ! The following changes since commit 88366b96ee0d8640b2af53e4026dbaeed0fab5e0: travis: Switch to QEMU v4.2.0 globally (2020-01-11 08:07:03 -0500) are available in the Git repository at: https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git tags/u-boot-imx-20200115 for you to fetch changes up to 8d9c0762a8cf0a5027e7cd3c6794693f2d64d007: imx: imxrt1050-evk: Add support for the NXP i.MXRT1050-EVK (2020-01-14 22:54:00 +0100) ---------------------------------------------------------------- ----------------------------------- - imx8: add capricorn giedi deneb boards - imx6: fixed fow wandboard - imx7: DM_ETHER for pico-imx7d - fsl_esdhc_imx: add broken-cd property - New SOC: IMXRT10xx Travis: https://travis-ci.org/sbabic/u-boot-imx/builds/637126531 ---------------------------------------------------------------- Anatolij Gustschin (4): imx: add imx8x capricorn giedi board imx: add imx8x based deneb board clk: imx8qxp: extend to support getting I2C IPG clock imx: dts: imx8dx: add I2C IPG clock for bus 0 and 2 Fabio Estevam (5): imx8qxp_mek: Select CONFIG_NET_RANDOM_ETHADDR wandboard: Do not print error message when PMIC is absent mx6ul_14x14_evk: Fix SPL boot hang mmc: fsl_esdhc_imx: Handle the "broken-cd" property ARM: dts: imx6ul-14x14-evk: Pass the "broken-cd" property Giulio Benetti (21): spl: fix entry_point equal to load_addr armv7m: cache: add mmu_set_region_dcache_behaviour() stub for compatibility clk: imx: pllv3: register PLLV3 GENERIC and USB as 2 different clocks clk: imx: pllv3: set div_mask differently if PLLV3 is GENERIC or USB clk: imx: pllv3: add enable() support clk: imx: pllv3: add disable() support clk: imx: pllv3: add set_rate() support clk: imx: pllv3: add PLLV3_SYS support clk: imx: pllv3: add support for PLLV3_AV type clk: imx: pfd: add set_rate() clk: imx: add i.IMXRT1050 clk driver pinctrl: add i.MXRT driver gpio: mxc_gpio: add support for i.MXRT1050 ARM: dts: imxrt1050: add dtsi file serial_lpuart: add clock enable if CONFIG_CLK is defined serial_lpuart: add support for i.MXRT ram: add SDRAM driver for i.MXRT SoCs mmc: fsl_esdhc: make if(CONFIG_IS_ENABLED(CLK)) an #if statement mmc: fsl_esdhc: add compatible for fsl, imxrt-usdhc imx: Add basic support for the NXP IMXRT10xx SoC family imx: imxrt1050-evk: Add support for the NXP i.MXRT1050-EVK Joris Offouga (2): pico-imx7d: Disable USB_ETHER support for bl33 defconfig pico-imx7d: Convert to DM_ETH Peng Fan (1): imx: imx8qxp_mek: update README arch/arm/Kconfig | 10 ++ arch/arm/Makefile | 4 +- arch/arm/cpu/armv7m/cache.c | 6 + arch/arm/dts/Makefile | 6 +- arch/arm/dts/fsl-imx8dx.dtsi | 10 +- arch/arm/dts/imx6ul-14x14-evk.dtsi | 1 + arch/arm/dts/imx8-deneb.dts | 10 ++ arch/arm/dts/imx8-giedi.dts | 10 ++ arch/arm/dts/imx8qxp-capricorn-u-boot.dtsi | 133 ++++++++++++++++ arch/arm/dts/imx8qxp-capricorn.dtsi | 285 +++++++++++++++++++++++++++++++++++ arch/arm/dts/imxrt1050-evk-u-boot.dtsi | 44 ++++++ arch/arm/dts/imxrt1050-evk.dts | 200 ++++++++++++++++++++++++ arch/arm/dts/imxrt1050.dtsi | 146 ++++++++++++++++++ arch/arm/include/asm/arch-imxrt/clock.h | 10 ++ arch/arm/include/asm/arch-imxrt/gpio.h | 19 +++ arch/arm/include/asm/arch-imxrt/imx-regs.h | 20 +++ arch/arm/include/asm/arch-imxrt/imxrt.h | 11 ++ arch/arm/include/asm/arch-imxrt/sys_proto.h | 11 ++ arch/arm/mach-imx/Makefile | 3 +- arch/arm/mach-imx/imx8/Kconfig | 11 ++ arch/arm/mach-imx/imxrt/Kconfig | 25 +++ arch/arm/mach-imx/imxrt/Makefile | 7 + arch/arm/mach-imx/imxrt/soc.c | 35 +++++ board/freescale/imx8qxp_mek/README | 26 ++-- board/freescale/imxrt1050-evk/Kconfig | 22 +++ board/freescale/imxrt1050-evk/MAINTAINERS | 6 + board/freescale/imxrt1050-evk/Makefile | 6 + board/freescale/imxrt1050-evk/README | 31 ++++ board/freescale/imxrt1050-evk/imximage.cfg | 36 +++++ board/freescale/imxrt1050-evk/imxrt1050-evk.c | 81 ++++++++++ board/freescale/mx6ul_14x14_evk/mx6ul_14x14_evk.c | 175 +++------------------ board/siemens/capricorn/Kconfig | 25 +++ board/siemens/capricorn/MAINTAINERS | 11 ++ board/siemens/capricorn/Makefile | 12 ++ board/siemens/capricorn/board.c | 448 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ board/siemens/capricorn/imximage.cfg | 22 +++ board/siemens/capricorn/spl.c | 47 ++++++ board/siemens/capricorn/uboot-container.cfg | 13 ++ board/siemens/common/factoryset.c | 2 + board/technexion/pico-imx7d/pico-imx7d.c | 46 ------ board/wandboard/wandboard.c | 2 +- common/spl/spl.c | 4 +- configs/deneb_defconfig | 103 +++++++++++++ configs/giedi_defconfig | 103 +++++++++++++ configs/imx8qxp_mek_defconfig | 1 + configs/imxrt1050-evk_defconfig | 69 +++++++++ configs/pico-dwarf-imx7d_defconfig | 5 + configs/pico-hobbit-imx7d_defconfig | 5 + configs/pico-imx7d_bl33_defconfig | 8 +- configs/pico-imx7d_defconfig | 5 + configs/pico-nymph-imx7d_defconfig | 5 + configs/pico-pi-imx7d_defconfig | 5 + drivers/clk/imx/Kconfig | 16 ++ drivers/clk/imx/Makefile | 2 + drivers/clk/imx/clk-imx8qxp.c | 12 ++ drivers/clk/imx/clk-imxrt1050.c | 292 +++++++++++++++++++++++++++++++++++ drivers/clk/imx/clk-pfd.c | 22 +++ drivers/clk/imx/clk-pllv3.c | 218 ++++++++++++++++++++++++++- drivers/gpio/mxc_gpio.c | 7 +- drivers/mmc/Kconfig | 2 +- drivers/mmc/fsl_esdhc_imx.c | 49 +++--- drivers/pinctrl/nxp/Kconfig | 14 ++ drivers/pinctrl/nxp/Makefile | 1 + drivers/pinctrl/nxp/pinctrl-imxrt.c | 40 +++++ drivers/ram/Kconfig | 8 + drivers/ram/Makefile | 2 + drivers/ram/imxrt_sdram.c | 439 +++++++++++++++++++++++++++++++++++++++++++++++++++++ drivers/serial/serial_lpuart.c | 31 +++- include/configs/capricorn-common.h | 185 +++++++++++++++++++++++ include/configs/deneb.h | 19 +++ include/configs/giedi.h | 19 +++ include/configs/imxrt1050-evk.h | 46 ++++++ include/configs/pico-imx7d.h | 11 -- include/configs/siemens-ccp-common.h | 19 +++ include/configs/siemens-env-common.h | 201 +++++++++++++++++++++++++ include/dt-bindings/clock/imxrt1050-clock.h | 65 ++++++++ include/dt-bindings/memory/imxrt-sdram.h | 100 ++++++++++++ include/dt-bindings/pinctrl/pins-imxrt1050.h | 993 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ include/fsl_lpuart.h | 3 +- 79 files changed, 4882 insertions(+), 275 deletions(-) create mode 100644 arch/arm/dts/imx8-deneb.dts create mode 100644 arch/arm/dts/imx8-giedi.dts create mode 100644 arch/arm/dts/imx8qxp-capricorn-u-boot.dtsi create mode 100644 arch/arm/dts/imx8qxp-capricorn.dtsi create mode 100644 arch/arm/dts/imxrt1050-evk-u-boot.dtsi create mode 100644 arch/arm/dts/imxrt1050-evk.dts create mode 100644 arch/arm/dts/imxrt1050.dtsi create mode 100644 arch/arm/include/asm/arch-imxrt/clock.h create mode 100644 arch/arm/include/asm/arch-imxrt/gpio.h create mode 100644 arch/arm/include/asm/arch-imxrt/imx-regs.h create mode 100644 arch/arm/include/asm/arch-imxrt/imxrt.h create mode 100644 arch/arm/include/asm/arch-imxrt/sys_proto.h create mode 100644 arch/arm/mach-imx/imxrt/Kconfig create mode 100644 arch/arm/mach-imx/imxrt/Makefile create mode 100644 arch/arm/mach-imx/imxrt/soc.c create mode 100644 board/freescale/imxrt1050-evk/Kconfig create mode 100644 board/freescale/imxrt1050-evk/MAINTAINERS create mode 100644 board/freescale/imxrt1050-evk/Makefile create mode 100644 board/freescale/imxrt1050-evk/README create mode 100644 board/freescale/imxrt1050-evk/imximage.cfg create mode 100644 board/freescale/imxrt1050-evk/imxrt1050-evk.c create mode 100644 board/siemens/capricorn/Kconfig create mode 100644 board/siemens/capricorn/MAINTAINERS create mode 100644 board/siemens/capricorn/Makefile create mode 100644 board/siemens/capricorn/board.c create mode 100644 board/siemens/capricorn/imximage.cfg create mode 100644 board/siemens/capricorn/spl.c create mode 100644 board/siemens/capricorn/uboot-container.cfg create mode 100644 configs/deneb_defconfig create mode 100644 configs/giedi_defconfig create mode 100644 configs/imxrt1050-evk_defconfig create mode 100644 drivers/clk/imx/clk-imxrt1050.c create mode 100644 drivers/pinctrl/nxp/pinctrl-imxrt.c create mode 100644 drivers/ram/imxrt_sdram.c create mode 100644 include/configs/capricorn-common.h create mode 100644 include/configs/deneb.h create mode 100644 include/configs/giedi.h create mode 100644 include/configs/imxrt1050-evk.h create mode 100644 include/configs/siemens-ccp-common.h create mode 100644 include/configs/siemens-env-common.h create mode 100644 include/dt-bindings/clock/imxrt1050-clock.h create mode 100644 include/dt-bindings/memory/imxrt-sdram.h create mode 100644 include/dt-bindings/pinctrl/pins-imxrt1050.h Best regards, Stefano -- ===================================================================== DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic(a)denx.de =====================================================================

2 1