On 14/01/16 16:51, John Snow wrote:
> We can revisit this once the solution for the CPU interrupt status is
> nailed down :)
Sure :)
> Broadly, you are right that this board has been pretty broken for a long
> time, but it appears to be at least semi-functional in 2.5, so it might
> be time to s
On 01/11/2016 06:41 PM, Mark Cave-Ayland wrote:
> On 08/01/16 20:55, John Snow wrote:
>
>> On 01/06/2016 04:17 PM, Mark Cave-Ayland wrote:
>>> On 06/01/16 20:57, John Snow wrote:
>>>
On 01/06/2016 03:37 PM, Mark Cave-Ayland wrote:
> Make sure that we include the value of dma_active in t
On 08/01/16 20:55, John Snow wrote:
> On 01/06/2016 04:17 PM, Mark Cave-Ayland wrote:
>> On 06/01/16 20:57, John Snow wrote:
>>
>>> On 01/06/2016 03:37 PM, Mark Cave-Ayland wrote:
Make sure that we include the value of dma_active in the migration stream.
Signed-off-by: Mark Cave-Ayl
On 01/06/2016 04:17 PM, Mark Cave-Ayland wrote:
> On 06/01/16 20:57, John Snow wrote:
>
>> On 01/06/2016 03:37 PM, Mark Cave-Ayland wrote:
>>> Make sure that we include the value of dma_active in the migration stream.
>>>
>>> Signed-off-by: Mark Cave-Ayland
>>> ---
>>> hw/ide/macio.c |3 ++
On 06/01/16 20:57, John Snow wrote:
> On 01/06/2016 03:37 PM, Mark Cave-Ayland wrote:
>> Make sure that we include the value of dma_active in the migration stream.
>>
>> Signed-off-by: Mark Cave-Ayland
>> ---
>> hw/ide/macio.c |3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> d
On 01/06/2016 03:37 PM, Mark Cave-Ayland wrote:
> Make sure that we include the value of dma_active in the migration stream.
>
> Signed-off-by: Mark Cave-Ayland
> ---
> hw/ide/macio.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/hw/ide/macio.c b/hw/ide/macio.c
Make sure that we include the value of dma_active in the migration stream.
Signed-off-by: Mark Cave-Ayland
---
hw/ide/macio.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/ide/macio.c b/hw/ide/macio.c
index 560c071..695d4d2 100644
--- a/hw/ide/macio.c
+++ b/hw/ide/m
