From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55454) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WI5eA-0004lx-SZ for qemu-devel@nongnu.org; Mon, 24 Feb 2014 19:13:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WI5e4-0003ru-QB for qemu-devel@nongnu.org; Mon, 24 Feb 2014 19:13:18 -0500 Received: from omzsmtpe04.verizonbusiness.com ([199.249.25.207]:57144) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WI5e4-0003po-M5 for qemu-devel@nongnu.org; Mon, 24 Feb 2014 19:13:12 -0500 From: Don Slutz Message-ID: <530BE015.70109@terremark.com> Date: Mon, 24 Feb 2014 19:13:09 -0500 MIME-Version: 1.0 References: <1392834640-15488-1-git-send-email-dslutz@verizon.com> In-Reply-To: <1392834640-15488-1-git-send-email-dslutz@verizon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] char/serial: Fix emptyness handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Don Slutz , qemu-devel@nongnu.org Cc: Peter Crosthwaite On 02/19/14 13:30, Don Slutz wrote: > The commit 88c1ee73d3231c74ff90bcfc084a7589670ec244 > char/serial: Fix emptyness check > > Still causes extra NULL byte(s) to be sent. > > So if the fifo is empty, do not send an extra NULL byte. > > Signed-off-by: Don Slutz > --- > hw/char/serial.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/hw/char/serial.c b/hw/char/serial.c > index 6d3b5af..6df5a53 100644 > --- a/hw/char/serial.c > +++ b/hw/char/serial.c > @@ -225,8 +225,9 @@ static gboolean serial_xmit(GIOChannel *chan, GIOCondition cond, void *opaque) > > if (s->tsr_retry <= 0) { > if (s->fcr & UART_FCR_FE) { > - s->tsr = fifo8_is_empty(&s->xmit_fifo) ? > - 0 : fifo8_pop(&s->xmit_fifo); > + if (fifo8_is_empty(&s->xmit_fifo)) > + return FALSE; > + s->tsr = fifo8_pop(&s->xmit_fifo); > if (!s->xmit_fifo.num) { > s->lsr |= UART_LSR_THRE; > } Since I sent this out, I have wondered if: s->lsr |= UART_LSR_THRE Also needs to be done. -Don Slutz