On 09/04/2019 17.37, Stephen Checkoway wrote:
>
>
> On Apr 9, 2019, at 02:13, Thomas Huth wrote:
>
>> We'd like to get rid of global_qtest in the long run (since it is
>> causing trouble for tests that run multiple instances of QEMU in
>> parallel, e.g. migration tests)... so if it is feasible,
On Apr 9, 2019, at 02:13, Thomas Huth wrote:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multiple instances of QEMU in
> parallel, e.g. migration tests)... so if it is feasible, please don't
> use it in new code anymore. Try to use a
Thomas Huth writes:
> On 09/04/2019 10.35, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> On 09/04/2019 09.45, Markus Armbruster wrote:
Thomas Huth writes:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multipl
On 09/04/2019 10.35, Markus Armbruster wrote:
> Thomas Huth writes:
>
>> On 09/04/2019 09.45, Markus Armbruster wrote:
>>> Thomas Huth writes:
>>>
We'd like to get rid of global_qtest in the long run (since it is
causing trouble for tests that run multiple instances of QEMU in
par
Thomas Huth writes:
> On 09/04/2019 09.45, Markus Armbruster wrote:
>> Thomas Huth writes:
>>
>>> We'd like to get rid of global_qtest in the long run (since it is
>>> causing trouble for tests that run multiple instances of QEMU in
>>> parallel, e.g. migration tests)... so if it is feasible, p
On 09/04/2019 09.45, Markus Armbruster wrote:
> Thomas Huth writes:
>
>> We'd like to get rid of global_qtest in the long run (since it is
>> causing trouble for tests that run multiple instances of QEMU in
>> parallel, e.g. migration tests)... so if it is feasible, please don't
>> use it in new
Thomas Huth writes:
> We'd like to get rid of global_qtest in the long run (since it is
> causing trouble for tests that run multiple instances of QEMU in
> parallel, e.g. migration tests)... so if it is feasible, please don't
> use it in new code anymore. Try to use a local variable in the funct
On 08/04/2019 22.55, Stephen Checkoway wrote:
> From: Stephen Checkoway
>
> Test the AMD command set for parallel flash chips. This test uses an
> ARM musicpal board with a pflash drive to test the following list of
> currently-supported commands.
> - Autoselect
> - CFI
> - Sector erase
> - Chip
From: Stephen Checkoway
Test the AMD command set for parallel flash chips. This test uses an
ARM musicpal board with a pflash drive to test the following list of
currently-supported commands.
- Autoselect
- CFI
- Sector erase
- Chip erase
- Program
- Unlock bypass
- Reset
Signed-off-by: Stephen
