27 Jul, 2018
16 commits
-
nfs was only printing basic info about the transfer in the case of a
DEBUG build. Print the same level of detail as tftp always.Signed-off-by: Joe Hershberger
-
The check for sending to the gateway was not using the correct variable
for comparison, so it was reporting that packets are sent to the gateway
when they were not.Signed-off-by: Joe Hershberger
-
Reported-by: Coverity (CID: 152888)
Signed-off-by: Joe Hershberger -
Ask the OS for each of its interfaces and for each one, bind a U-Boot
device and then probe it. This will allocate the priv data structure
that is then populated.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
We don't necessarily know how many MAC addresses we'll need, so implement
a ROM read so we always have something valid.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
With systemd stable interface names, eth0 will almost never exist.
Instead of using that name in the sandbox.dts, use an index.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
Instead of doing a simple string compare against "lo", look for the flag
that indicates a localhost interface.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
Use the dev_ functions to access DT properties.
Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
If we let descriptors equal 0, we can end up closing STDIN. Make sure
they start out as -1.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
With driver model, we were not checking if the state of the device was
marked as active before calling the halt function. Check that the device
is probed and also marked as active. This avoids the case where we were
calling halt on the first device in net_init() and the driver would
operate on bogus data structures causing problems. In this case, the
priv was all 0, so halt() would close STDIN.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
test.dts specified the fake MAC address as a u32 array. Instead it
should be a u8 array.Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
In open, the socket is correctly checked to be -1 in the error case.
In send and recv, we checked for 0, but that is a valid socket number.Correct this by checking for -1 as a bad socket everywhere.
Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
such as aborting a command that is timing out without completely
terminating the sandbox executable.In [1], Simon disabled this. His reason for it was that it interferes
with piping test scripts. Piping should be done in cooked mode, so this
change should still not interfere.[1] commit 8969ea3e9f2db04a6b3675 ("sandbox: Disable Ctrl-C")
Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass -
We don't necessarily want to re-enable ctrl-c if it was already disabled
when calling tstc().Signed-off-by: Joe Hershberger
Reviewed-by: Simon Glass
26 Jul, 2018
1 commit
-
Now that we have removed the DocBook files we need to not try and clean
that directory.Reported-by: ericywl
Reported-by: Jagan Teki
Fixes: 78a88f7930be ("doc: Replace DocBook with sphinx-based docs")
Signed-off-by: Tom Rini
25 Jul, 2018
10 commits
-
Switch to the distro boot for UniPhier platform.
- Remove the environment vairalbes used to load images from raw
block devices.- Keep the command to download images via tftp. This will be
useful to boot the kernel when no valid kernel image is ready
yet in the file system.- Use root.cpio.gz instead of root.cpio.uboot because we always know
the file size of the init ramdisk; it is loaded via either a file
system or network.- Rename fit_addr_r to kernel_addr_r, which the distro command
checks to get the load address of FIT image.Signed-off-by: Masahiro Yamada
-
Enable "mtdparts" and "ubi" commands for uniphier_v8_defconfig to
use UBI on NAND devices.Enable only "mtdparts" for uniphier_{v7,ld4_sld8}_defconfig because
enabling UBI would increase 170KB, which would be memory footprint
problem.Signed-off-by: Masahiro Yamada
-
Propagate the "mtdparts" environment variable to the DT passed
in to OS.Signed-off-by: Masahiro Yamada
-
Prepare to add more fdt fixup code.
Signed-off-by: Masahiro Yamada
-
The 'bd' is passed in ft_board_setup() as the second argument.
Replace 'gd->bd' with 'bd'.Signed-off-by: Masahiro Yamada
-
Add 'const' (also 'static' in some places) to struct node_info
arrays to save memory footprint.Signed-off-by: Masahiro Yamada
-
The second argument of fdt_fixup_mtdparts() is an opaque pointer,
'void *node_info', hence callers can pass any pointer.Obviously, fdt_fixup_mtdparts() expects 'struct node_info *'
otherwise, it crashes run-time.Change the prototype so that it is compile-time checked.
Also, add 'const' qualifier to it so that callers can constify
the struct node_info arrays.Signed-off-by: Masahiro Yamada
Reviewed-by: Simon Glass -
The NAND framework makes sure to pass in the buffer with at least
chip->buf_align alignment. Currently, the Denali NAND driver only
requests 16 byte alignment. This causes unaligned cache operations
for the DMA transfer.[Error Example]
=> nand read 81000010 0 1000
NAND read: device 0 offset 0x0, size 0x1000
CACHE: Misaligned operation at range [81000010, 81001010]
CACHE: Misaligned operation at range [81000010, 81001010]
CACHE: Misaligned operation at range [81000010, 81001010]
CACHE: Misaligned operation at range [81000010, 81001010]
4096 bytes read: OKReported-by: Marek Vasut
Signed-off-by: Masahiro Yamada -
cherry-pick kernel commit 2ae89c7 (2018-06-05)
to avoid warnings when compiling with GCC 8.1In file included from scripts/kconfig/zconf.tab.c:2486:
scripts/kconfig/confdata.c: In function ‘conf_write’:
scripts/kconfig/confdata.c:771:22: warning: ‘%s’ directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
sprintf(newname, "%s%s", dirname, basename);
^~
scripts/kconfig/confdata.c:771:19: note: assuming directive output of 7 bytes
sprintf(newname, "%s%s", dirname, basename);
^~~~~~
scripts/kconfig/confdata.c:771:2: note: ‘sprintf’ output 1 or more bytes (assuming 4104) into a destination of size 4097
sprintf(newname, "%s%s", dirname, basename);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
scripts/kconfig/confdata.c:774:23: warning: ‘.tmpconfig.’ directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
^~~~~~~~~~~
scripts/kconfig/confdata.c:774:3: note: ‘sprintf’ output between 13 and 4119 bytes into a destination of size 4097
sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Signed-off-by: Luis Araneda
Signed-off-by: Masahiro Yamada
24 Jul, 2018
13 commits
-
The patch
"tools/mkimage: Fix DTC run command to handle file names with space"
(sha1: a6e9810495bc929b6beafb88f557cdaadf87fc83) contains comma in name
which is confusing patman. Fix it by defining Mirza's email in mailmap.Signed-off-by: Michal Simek
-
The NAND offsets for the kernel and U-Boot were missing.
This patch sets up the offsets so the AM3517-EVM can boot from NAND
when DIP switches S7:1 and S7:4 are to the OFF positionSigned-off-by: Adam Ford
-
The previous e-mail pointing to Vaibhav Hiremath
is bouncing and has for some time. This updates it to myself and I
work for Logic PD the manufacturer of the AM3517-SOM and EVMSigned-off-by: Adam Ford
-
Symbol CONFIG_SPL_RELOC_STACK_SIZE is not used anywhere. So remove it.
Signed-off-by: Heinrich Schuchardt
-
Currently the U-Boot project contains 2 documentation directories:
- doc/
- Documentation/The Documentation directory only contains device tree bindings related
content, so move the 3 files to doc/device-tree-bindings/.Signed-off-by: Breno Lima
-
There is no reason not to use macros which are already defined.
It is also much easier for grepping.Signed-off-by: Michal Simek
Reviewed-by: Simon Glass -
commit d233ccb1d84b901f7e23e6d9b4f2c6a57198b23b
ARM: omap3: beagle: Enable DM_SERIAL, update distro usage and NAND layoutSigned-off-by: Guillaume GARDET
Cc: Derald D. Woods
Cc: Tom Rini -
Header file "asm/utils.h" is not required to compile "spl_ymodem.c".
So, removing this dependency allows other architectures to use this
booting device as "asm/utils.h" is only present in "arm" architecture.Signed-off-by: Paulo Zaneti
-
The length returned by hexport_r has a few redundant characters.
This appears as NULL characters at the end so seems harmless.Remove the surplus counts in two places
totlen += strlen(ep->key) + 2;
I'm guessing the +2 here is for = and sep char. But there is another
totlen += 2; line that does that.size = totletn + 1;
Doesn't make sense and isn't justified with any comment.Signed-off-by: Zubair Lutfullah Kakakhel
-
Use blk_dread()/blk_dwrite() in mmc_read()/mmc_write() AVB operation
implementations. This fixes compilation issues when CONFIG_BLK is
enabled.Signed-off-by: Igor Opaniuk
Tested-by: Eugeniu Rosca -
1. Since libavb library alone is highly portable, introduce dedicated
Kconfig symbol for AVB bootloader-dependent operations, so it's possible
to build libavb separately. AVB bootloader-dependent operations include:
* Helpers to process strings in order to build OS bootargs.
* Helpers to access MMC, similar to drivers/fastboot/fb_mmc.c.
* Helpers to alloc/init/free avb ops.
2. Add CONFIG_FASTBOOT dependency, as fastboot buffer is
re-used in partition verification operations.Reported-by: Eugeniu Rosca
Signed-off-by: Igor Opaniuk
Reviewed-by: Eugeniu Rosca
Tested-by: Eugeniu Rosca -
In the case that there was no name defined for a partition the
code assumes that name_len is 22 and therefore allocates exactly
that space for a dummy name. But the function sprintf() first
resolves "0x%08llx@0x%08llx" to a string that is longer than 22
bytes. This leads to a buffer overflow. The replacement function
snprintf() limits the copied bytes to name_len and therefore
avoids the buffer overflow.Signed-off-by: Kay Potthoff
-
With recent kernel v4.18-rcx, uImage becomes bigger than 8MB.
Set SYS_BOOTM_LEN to 16MB, this fix the following error message:
"Fix Loading Kernel Image ... Image too large: increase
CONFIG_SYS_BOOTM_LEN"Signed-off-by: Patrice Chotard