On Monday, October 03, 2011 20:13:03 Simon Glass wrote: > On Mon, Oct 3, 2011 at 12:37 PM, Mike Frysinger wrote: > > On Monday, September 26, 2011 20:10:45 Simon Glass wrote: > >> This is not useful on the sandbox architecture since we can simply link > >> all our code with U-Boot. Also, loading native code doesn't make a lot > >> of sense. > > > > the standalone code would be useful tests i think ... after all, you're > > given an exported API from u-boot which are high level functions like > > I/O. > > > > but getting them to work in the sandbox environment probably will be > > tricky to say the least ... perhaps add a note in the README.sandbox ? > > Yes I will add a note. But it's hard to see why it wouldn't be better > just to link against U-Boot. Or are you thinking of lashing a file > system stress tester to U-Boot somehow?
i would like to see automatic testing of the exported API in the same way that standalone applications work. so u-boot runs, loads an arbitrary blob into its external memory, and then jumps into it. if we have tun/tap networking, this should be easy to get arbitrary files into its memory space ... after that, it's a "simple" matter of jumping into the middle of its code :). -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot