Am 15.07.2013 12:45, schrieb Peter Crosthwaite:
> Hi Andreas,
>
> On Mon, Jul 15, 2013 at 7:55 PM, Andreas Färber wrote:
>> Hi Peter,
>>
>> Am 15.07.2013 06:02, schrieb Peter Crosthwaite:
>>> A while ago, TYPE_CPU was refactored to by a child of TYPE_DEVICE. As
>>> something of a hangover though,
Hi Andreas,
On Mon, Jul 15, 2013 at 7:55 PM, Andreas Färber wrote:
> Hi Peter,
>
> Am 15.07.2013 06:02, schrieb Peter Crosthwaite:
>> A while ago, TYPE_CPU was refactored to by a child of TYPE_DEVICE. As
>> something of a hangover though, CPU has a separate reset fn to device.
>> This means
>>
>>
Hi Peter,
Am 15.07.2013 06:02, schrieb Peter Crosthwaite:
> A while ago, TYPE_CPU was refactored to by a child of TYPE_DEVICE. As
> something of a hangover though, CPU has a separate reset fn to device.
> This means
>
> device_reset(DEVICE(my_cpu));
>
> doesn't actually work as a reset. Should w
Hi Andreas, Anthony,
A while ago, TYPE_CPU was refactored to by a child of TYPE_DEVICE. As
something of a hangover though, CPU has a separate reset fn to device.
This means
device_reset(DEVICE(my_cpu));
doesn't actually work as a reset. Should we fix this by getting rif of
cpu_reset and just usi