25 Jun, 2014
1 commit
24 Jun, 2014
1 commit
-
Commit 95fac6ab4589 "sandbox: Use os functions to read host device tree"
removed the ability for get_device_and_partition() to handle the "host"
device type, and redirect accesses to it to the host filesystem. This
broke some unit tests that use this feature. So, revert that change. The
code added back by this patch is slightly different to pacify checkpatch.However, we're then left with "host" being both:
- A pseudo device that accesses the hosts real filesystem.
- An emulated block device, which accesses "sectors" inside a file stored
on the host.In order to resolve this discrepancy, rename the pseudo device from host
to hostfs, and adjust the unit-tests for this change.The "help sb" output is modified to reflect this rename, and state where
the host and hostfs devices should be used.Signed-off-by: Stephen Warren
Tested-by: Josh Wu
Acked-by: Simon Glass
Tested-by: Simon Glass
22 Jun, 2014
1 commit
-
Make both dm enumeration commands support showing whether a driver is active
or not, and use a consistent indicator (an asterisk).Signed-off-by: Simon Glass
Acked-by: Marek Vasut
21 Jun, 2014
3 commits
-
The values here are int, but the map_to_sysmem() call can return a long.
Add a cast to deal with this.Signed-off-by: Simon Glass
-
The GPIO tests require the sandbox GPIO driver, so cannot be run on other
platforms. Similarly for the 'dm test' command.Signed-off-by: Simon Glass
-
It is best to avoid having any occurence of 'struct device' in driver
model, so rename to achieve this.Signed-off-by: Simon Glass
19 Jun, 2014
1 commit
-
vboot_test.sh uses Bashisms. Explicitly use #!/bin/bash so the script
doesn't fail if /bin/sh isn't Bash.Signed-off-by: Stephen Warren
Acked-by: Simon Glass
06 Jun, 2014
1 commit
-
run_command_list() is supposed to return a return code of 0 for success
and 1 for failure. Add a few simple tests that confirm this. These tests
work both with the built-in parser and hush.Signed-off-by: Simon Glass
27 May, 2014
1 commit
-
using UBI and DM together leads in compiler error, as
both define a "struct device", so rename "struct device"
in include/dm/device.h to "struct udevice", as we use
linux code (MTD/UBI/UBIFS some USB code,...) and cannot
change the linux "struct device"Signed-off-by: Heiko Schocher
Cc: Simon Glass
Cc: Marek Vasut
22 Mar, 2014
2 commits
-
add host tool "fit_check_sign" which verifies, if a fit image is
signed correct.Signed-off-by: Heiko Schocher
Cc: Simon Glass -
based on patch from andreas@oetken.name:
http://patchwork.ozlabs.org/patch/294318/
commit message:
I currently need support for rsa-sha256 signatures in u-boot and found out that
the code for signatures is not very generic. Thus adding of different
hash-algorithms for rsa-signatures is not easy to do without copy-pasting the
rsa-code. I attached a patch for how I think it could be better and included
support for rsa-sha256. This is a fast first shot.aditionally work:
- removed checkpatch warnings
- removed compiler warnings
- rebased against current headSigned-off-by: Heiko Schocher
Cc: andreas@oetken.name
Cc: Simon Glass
07 Mar, 2014
3 commits
-
The unit-test for hush's "test -e" currently relies upon being run in
the U-Boot build directory, because it tests for the existence of a file
that exists in that directory.Fix this by explicitly creating the file we use for the existence test,
and deleting it afterwards so that multiple successive unit-test
invocations succeed. This required adding an os.c function to erase
files.Reported-by: Simon Glass
Signed-off-by: Stephen Warren -
The following shell command fails:
if test -z "$x"; then echo "zero"; else echo "non-zero"; fi
(assuming $x does not exist, it prints "non-zero" rather than "zero").
... since "$x" expands to nothing, and the argument is completely
dropped, causing too few to be passed to -z, causing cmd_test() to
error out early.This is because when variable expansions are processed by make_string(),
the expanded results are concatenated back into a new string. However,
no quoting is applied when doing so, so any empty variables simply don't
generate any parameter when the combined string is parsed again.Fix this by explicitly replacing quoting any argument that was originally
quoted when re-generating a string from the already-parsed argument list.This also fixes loss of whitespace in commands such as:
setenv space " "
setenv var " 1${space}${space} 2 "
echo ">>${var}<
Acked-by: Simon Glass
Signed-off-by: Stephen Warren -
Delete the temporary variables that are used to save unit-test results
from the environment after running the test. This prevents polluting
the environment, or growing it too much.Signed-off-by: Stephen Warren
Acked-by: Simon Glass
05 Mar, 2014
3 commits
-
Add driver model support for GPIOs. Since existing GPIO drivers do not use
driver model, this feature must be enabled by CONFIG_DM_GPIO. After all
GPO drivers are converted over we can perhaps remove this config.Tests are provided for the sandbox implementation, and are a sufficient
sanity check for basic operation.The GPIO uclass understands the concept of named banks of GPIOs, with each
GPIO device providing a single bank. Within each bank the GPIOs are numbered
using an offset from 0 to n-1. For example a bank named 'b' with 20
offsets will provide GPIOs named b0 to b19.Anonymous GPIO banks are also supported, and are just numbered without any
prefix.Each time a GPIO driver is added to the uclass, the GPIOs are renumbered
accordinging, so there is always a global GPIO numbering order.Signed-off-by: Simon Glass
Signed-off-by: Marek Vasut
Signed-off-by: Pavel Herrmann
Signed-off-by: Viktor Křivák
Signed-off-by: Tomas Hlavacek -
This command is not required for driver model operation, but can be useful
for testing. It provides simple dumps of internal data structures.Signed-off-by: Simon Glass
Signed-off-by: Marek Vasut
Signed-off-by: Pavel Herrmann
Signed-off-by: Viktor Křivák
Signed-off-by: Tomas Hlavacek -
Add some tests of driver model functionality. Coverage includes:
- basic init
- binding of drivers to devices using platform_data
- automatic probing of devices when referenced
- availability of platform data to devices
- lifecycle from bind to probe to remove to unbind
- renumbering within a uclass when devices are probed/removed
- calling driver-defined operations
- deactivation of drivers when removed
- memory leak across creation and destruction of drivers/uclasses
- uclass init/destroy methods
- automatic probe/remove of children/parents when neededThis function is enabled for sandbox, using CONFIG_DM_TEST.
Signed-off-by: Simon Glass
19 Feb, 2014
2 commits
-
I recently re-wrote cmd_test() to add new features. Add a bunch of unit-
tests to make sure I didn't break anything.Suggested-by: Simon Glass
Signed-off-by: Stephen Warren -
"env default -f" doesn't work any more; replace it with
"env default -f -a". This avoids the following when running the ut
command:do_ut_cmd: Testing commands
env - environment handling commandsUsage:
env default [-f] -a - [forcibly] reset default environment
...Signed-off-by: Stephen Warren
13 Dec, 2013
1 commit
-
Add a test for dumpimage.
Signed-off-by: Guilherme Maciel Ferreira
Signed-off-by: Simon Glass
01 Nov, 2013
1 commit
-
Signed-off-by: Masahiro Yamada
15 Oct, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Drop changes for PEP 4 following python tools]
Signed-off-by: Tom Rini
04 Sep, 2013
1 commit
-
This adds the "test_compression" command when building the sandbox. This
tests the existing compression and decompression routines for simple
sanity and for buffer overflow conditions.Signed-off-by: Kees Cook
Acked-by: Simon Glass
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
26 Jun, 2013
3 commits
-
Add a description of how to implement verified boot using signed FIT images,
and a simple test which verifies operation on sandbox.The test signs a FIT image and verifies it, then signs a FIT configuration
and verifies it. Then it corrupts the signature to check that this is
detected.Signed-off-by: Simon Glass
-
It is difficult to automatically test tracing on most architectures, but
with sandbox it is easy enough to do a simple sanity check.Signed-off-by: Simon Glass
-
When this test fails it is useful to see the output from U-Boot. Add
printing of this information on failure.Signed-off-by: Simon Glass
05 Jun, 2013
1 commit
-
The image code is fairly complex with various different options. It would
be useful to have comprehensive tests for this.As a start, create a script which tries out loading a kernel/ramdisk/fdt
from a FIT and checks that the images appear in the right place in memory.This uses sandbox which now supports bootm and related features.
Signed-off-by: Simon Glass
10 Aug, 2012
1 commit
-
Since run_command() and run_command_list() are important and a little
confusing, add some basic tests to check that the behaviour is correct.Note: I am not sure that this should be committed, nor where it should go
in the source tree. Comments welcome.To run the unit tests use the ut_cmd command available in sandbox:
make sandbox_config
make
./u-boot -c ut_cmd(To test both hush and built-in parsers, you need to manually change
CONFIG_SYS_HUSH_PARSER in include/configs/sandbox.h and build/run again)Signed-off-by: Simon Glass