diff options
| author | Markus Armbruster <armbru@redhat.com> | 2009-10-07 01:15:58 +0200 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2009-10-07 08:54:54 -0500 |
| commit | e23a1b33b53d25510320b26d9f154e19c6c99725 (patch) | |
| tree | 2c0c5b9ac463c9e9ed745d1ea1837892cac139f3 /hw/etraxfs.c | |
| parent | 33e66b86d89040f0a9e99aa53deb74ce8936a649 (diff) | |
New qdev_init_nofail()
Like qdev_init(), but terminate program via hw_error() instead of
returning an error value.
Use it instead of qdev_init() where terminating the program on failure
is okay, either because it's during machine construction, or because
we know that failure can't happen.
Because relying in the latter is somewhat unclean, and the former is
not always obvious, it would be nice to go back to qdev_init() in the
not-so-obvious cases, only with proper error handling. I'm leaving
that for another day, because it involves making sure that error
values are properly checked by all callers.
Patchworks-ID: 35168
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/etraxfs.c')
| -rw-r--r-- | hw/etraxfs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/etraxfs.c b/hw/etraxfs.c index 4f451c54c9..7937e48ef4 100644 --- a/hw/etraxfs.c +++ b/hw/etraxfs.c @@ -92,7 +92,7 @@ void bareetraxfs_init (ram_addr_t ram_size, dev = qdev_create(NULL, "etraxfs,pic"); /* FIXME: Is there a proper way to signal vectors to the CPU core? */ qdev_prop_set_ptr(dev, "interrupt_vector", &env->interrupt_vector); - qdev_init(dev); + qdev_init_nofail(dev); s = sysbus_from_qdev(dev); sysbus_mmio_map(s, 0, 0x3001c000); sysbus_connect_irq(s, 0, cpu_irq[0]); |