On 13 April 2015 at 16:34, Simon Glass sjg@chromium.org wrote:
Hi Joe,
On 13 April 2015 at 16:28, Joe Hershberger joe.hershberger@gmail.com wrote:
Hi Sjoerd,
On Mon, Apr 13, 2015 at 5:07 PM, Simon Glass sjg@chromium.org wrote:
Hi Sjoerd,
On 13 April 2015 at 14:54, Sjoerd Simons sjoerd.simons@collabora.co.uk wrote:
Make the sandbox setup more generic/examplary by including config_distro_defaults.h and config_distro_bootcmd.h.
Among other things this makes it easy to test whether images will boot though with the standard distro bootcmds by running e.g: u-boot -c 'host bind 0 myimage.img ; boot'
By default there are 2 target host devices to emulate device with multiple storage devices (e.g. internal ("host 0") and external ("host 1") and verify that the prioritization and fallbacks do work correctly.
Signed-off-by: Sjoerd Simons sjoerd.simons@collabora.co.uk Reviewed by: Simon Glass sjg@chromium.org Acked-by: Simon Glass sjg@chromium.org
Thanks for the updated patch. Please see my question below.
Changes in v4:
- Adapt to sandbox networking support
Changes in v3: None Changes in v2: None
include/configs/sandbox.h | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-)
Applied to u-boot-x86/sandbox, thanks!
[snip]