diff options
| author |   jsg <jsg@openbsd.org> | 2017-01-24 05:29:22 +0000 |
|---|---|---|
| committer | jsg <jsg@openbsd.org> | 2017-01-24 05:29:22 +0000 |
| commit | d9e0385638bef18ac4720124282e80f73b1f261f (patch) | |
| tree | 1c7c87b34fe1bd7f5582e8e099c8aebaba66beda /sys/lib/libkern/memcpy.c | |
| parent | Display the thread ID (TID) rather than the process group ID (PGRP) (diff) | |
| download | wireguard-openbsd-d9e0385638bef18ac4720124282e80f73b1f261f.tar.xz wireguard-openbsd-d9e0385638bef18ac4720124282e80f73b1f261f.zip | |
There are two u-boot targets which should work with the sabre lite
boards. mx6qsabrelite (which sets fdt_addr) and nitrogen6q
(which sets fdtaddr). The difference seems to be the mx6qsabrelite
target uses a small loader in SPI connected flash which will load
the rest of u-boot from an SD card. The nitrogen6q target normally
loads all of u-boot from an image in flash and then searches for a
6x_bootscript file with u-boot commands on MMC and SATA.
While neither of them supports "Generic Distro Configuration" which
would automatically search for an EFI image, if they did fdt_addr
is intended to be used for a DTB in ROM, while fdt_addr_r is intended
to be used for a DTB in RAM.
Change the 6x_bootscript u-boot commands to load the DTB to
fdtaddr instead of fdt_addr as matthieu@ reported fdt_addr was not
present in the u-boot environment on his system.
Diffstat (limited to 'sys/lib/libkern/memcpy.c')
0 files changed, 0 insertions, 0 deletions