If I had to guess, I'd say that the network dependency issue ARM is talking about is the fact that we install an image over the wire, and that they probably want to do bare metal testing on systems that may not even have network support at all. I know that they've mentioned such things in the past, and the response has basically been that we chose this method of deployment based on the boards we care about testing. If they need to deploy things in a different way (usb, jtag, carrier pigeons...) a different deployment handler would need to be written to cover that.
On Wed, Jun 20, 2012 at 2:12 PM, Andy Doan <[email protected]> wrote: > On 06/20/2012 01:59 PM, Scott Bambrough wrote: > >> Agreed, it is a little too ambitious. Might be better to add it as a >> second mode of operation LAVA supports, and indicate the mode in the job >> JSON. >> > > I probably wasn't clear about one thing: This would definitely be a new > mode for LAVA that people would have to opt-in for when defining their jobs. > > > ______________________________**_________________ > linaro-validation mailing list > linaro-validation@lists.**linaro.org <[email protected]> > http://lists.linaro.org/**mailman/listinfo/linaro-**validation<http://lists.linaro.org/mailman/listinfo/linaro-validation> >
_______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
