On Wed, Dec 18, 2013 at 11:48 PM, Alexander Graf wrote:
>
> On 11.11.2013, at 09:16, peter.crosthwa...@xilinx.com wrote:
>
>> From: Peter Crosthwaite
>>
>> There are a mix of usages of the qemu_fdt_* API calls, some which
>> wish to assert and abort QEMU on failure and some of which wish to do
>>
On 11.11.2013, at 09:16, peter.crosthwa...@xilinx.com wrote:
> From: Peter Crosthwaite
>
> There are a mix of usages of the qemu_fdt_* API calls, some which
> wish to assert and abort QEMU on failure and some of which wish to do
> their own error handling. The latter in more correct, but the fo
From: Peter Crosthwaite
There are a mix of usages of the qemu_fdt_* API calls, some which
wish to assert and abort QEMU on failure and some of which wish to do
their own error handling. The latter in more correct, but the former
is in the majority and more pragmatic. However the asserting clients
