u-boot.git/test, branch v2015.01-rc2

sandbox: script for testing sandbox/ext4/fat/fs commands

2014-11-23T11:49:05+00:00

Test size/read/write commands in a sandbox environment.

Signed-off-by: Suriyan Ramasami 

Acked-by: Simon Glass

hush: make run_command() return an error on parsing failure

2014-11-07T21:27:06+00:00

run_command() returns success even if the command had a syntax error;
correct this behaviour.

Signed-off-by: Rabin Vincent 
Acked-by: Simon Glass

hush: return consistent codes from run_command()

2014-11-07T21:27:06+00:00

Attempting to run:
 - an empty string
 - a string with just spaces

returns different error codes, 1 for the empty string and 0
for the string with just spaces.  Make both of them return
0 for consistency.

Signed-off-by: Rabin Vincent 
Acked-by: Simon Glass

test: Add a simple test to detected warnings with uint64_t, uintptr_t

2014-10-27T15:04:01+00:00

These types are problematic because they are typically declared in a
non-standard way in U-Boot. For example, U-Boot uses 'long long' for
int64_t even on a 64-bit machine whereas stdint.h uses 'long'.
Similarly, U-Boot always uses 'long' for intptr_t whereas stdint.h mostly
uses 'int'.

This simple test script runs a few toolchains on a few archs to check for
warnings.

Signed-off-by: Simon Glass

cli: hush: Adjust 'run' command to run each line of the env var

2014-10-27T15:03:33+00:00

The run command treats each argument an an environment variable. It gets the
value of each variable and executes it as a command. If an environment
variable contains a newline and the hush cli is used, it is supposed to
execute each line one after the other.

Normally a newline signals to hush to exit - this is used in normal command
line entry - after a command is entered we want to return to allow the user
to enter the next one. But environment variables obviously need to execute
to completion.

Add a special case for the execution of environment variables which
continues when a newline is seen, and add a few tests to check this
behaviour.

Note: it's not impossible that this may cause regressions in other areas.
I can't think of a case but with any change of behaviour with limited test
coverage there is always a risk. From what I can tell this behaviour has
been around since at least U-Boot 2011.03, although this pre-dates sandbox
and I have not tested it on real hardware.

Reported-by: Wolfgang Denk 
Signed-off-by: Simon Glass

test: dm: Add additional GPIO tests

2014-10-24T01:29:53+00:00

Add tests for gpio_requestf() and for memory leaks.

Signed-off-by: Simon Glass

test: dm: Support memory leak checking as a core feature

2014-10-24T01:29:53+00:00

Check the state of the malloc() heap before each test is run, so that tests
can verify that all is well at the end. Provide helper functions to mark
the heap and to check that it returns to its initial state.

Signed-off-by: Simon Glass

dm: gpio: Add gpio_requestf() helper for printf() strings

2014-10-24T01:29:52+00:00

Add a helper which permits a printf()-style format string for the requester
string.

Signed-off-by: Simon Glass

test: dm: Update GPIO tests for new gpio_request() method

2014-10-24T01:29:52+00:00

Now that gpio_request() is handled by the uclass, updates the tests
accordingly.

Signed-off-by: Simon Glass

dm: sf: Add tests for SPI flash

2014-10-22T16:36:52+00:00

Add a simple test for SPI that uses SPI flash. It operates by creating a
SPI flash file and using the 'sf test' command to test that all
operations work correctly.

Signed-off-by: Simon Glass 
Acked-by: Jagannadha Sutradharudu Teki