On 10.02.2017 13:48, Peter Maydell wrote:
> On 9 February 2017 at 23:15, David Gibson wrote:
>> On Thu, Feb 09, 2017 at 02:37:26PM +, Peter Maydell wrote:
>>> On 9 February 2017 at 14:13, Thomas Huth wrote:
Peter Maydell recently ran into time-out problems with the
prom-env test on
On 9 February 2017 at 23:15, David Gibson wrote:
> On Thu, Feb 09, 2017 at 02:37:26PM +, Peter Maydell wrote:
>> On 9 February 2017 at 14:13, Thomas Huth wrote:
>> > Peter Maydell recently ran into time-out problems with the
>> > prom-env test on a rather slow ARM board. To tackle this issue,
On Thu, Feb 09, 2017 at 02:37:26PM +, Peter Maydell wrote:
> On 9 February 2017 at 14:13, Thomas Huth wrote:
> > Peter Maydell recently ran into time-out problems with the
> > prom-env test on a rather slow ARM board. To tackle this issue,
> > we can speed up the test by running QEMU with "-no
On 9 February 2017 at 14:13, Thomas Huth wrote:
> Peter Maydell recently ran into time-out problems with the
> prom-env test on a rather slow ARM board. To tackle this issue,
> we can speed up the test by running QEMU with "-nodefaults" here,
> so that SLOF has less devices to scan during boot, an
Peter Maydell recently ran into time-out problems with the
prom-env test on a rather slow ARM board. To tackle this issue,
we can speed up the test by running QEMU with "-nodefaults" here,
so that SLOF has less devices to scan during boot, and by using
the "nvramrc" environment variable instead of
