From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6366] serial: open a null device if the CharDriverState argument is null
Date: Sun, 18 Jan 2009 14:28:11 +0000 [thread overview]
Message-ID: <E1LOYdH-0001Wk-0x@cvs.savannah.gnu.org> (raw)
Revision: 6366
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6366
Author: aurel32
Date: 2009-01-18 14:28:10 +0000 (Sun, 18 Jan 2009)
Log Message:
-----------
serial: open a null device if the CharDriverState argument is null
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Modified Paths:
--------------
trunk/hw/serial.c
Modified: trunk/hw/serial.c
===================================================================
--- trunk/hw/serial.c 2009-01-18 14:08:04 UTC (rev 6365)
+++ trunk/hw/serial.c 2009-01-18 14:28:10 UTC (rev 6366)
@@ -711,7 +711,7 @@
{
s->irq = irq;
s->baudbase = baudbase;
- s->chr = chr;
+ s->chr = chr ?: qemu_chr_open("null", "null", NULL);
s->modem_status_poll = qemu_new_timer(vm_clock, (QEMUTimerCB *) serial_update_msl, s);
@@ -721,6 +721,8 @@
qemu_register_reset(serial_reset, s);
serial_reset(s);
+ qemu_chr_add_handlers(s->chr, serial_can_receive1, serial_receive1,
+ serial_event, s);
}
/* If fd is zero, it means that the serial device uses the console */
@@ -739,8 +741,6 @@
register_ioport_write(base, 8, 1, serial_ioport_write, s);
register_ioport_read(base, 8, 1, serial_ioport_read, s);
- qemu_chr_add_handlers(chr, serial_can_receive1, serial_receive1,
- serial_event, s);
return s;
}
@@ -837,8 +837,6 @@
serial_mm_write, s);
cpu_register_physical_memory(base, 8 << it_shift, s_io_memory);
}
- qemu_chr_add_handlers(chr, serial_can_receive1, serial_receive1,
- serial_event, s);
serial_update_msl(s);
return s;
}
reply other threads:[~2009-01-18 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LOYdH-0001Wk-0x@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).