All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] xen: more robust serial port driver
Date: Tue, 28 Jul 2009 16:47:36 +0200	[thread overview]
Message-ID: <200907281647.36341.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C694C69E.10CA2%keir.fraser@eu.citrix.com>

On Tuesday 28 July 2009 16:15:42 Keir Fraser wrote:
> On 28/07/2009 15:07, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > Attached patch adds a check if the fifo is usable before we
> > actually use it.
>
> I count that at least the first two chunks and the initialisation of
> tx_fifo_size are unnecessary.

First hunk:

    It looks suspicious returning a value of type void.

Second hunk and initialization of tx_fifo_size:

    If you are sure these initializations are duplicates, then they are
    unnecessary.

> Might this be the case for the udelay(100) as 
> well?

No. This ensures, that the write takes effect before the read happens.

> And what kinds of systems have these broken UARTs that half-advertise 
> a broken/non-existent FIFO?

The original ns16550 has a broken FIFO. The ns16450 has no FIFO.
There are simulators which simulate those old things instead of a ns16550a.

Christoph

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2009-07-28 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 14:07 [PATCH] xen: more robust serial port driver Christoph Egger
2009-07-28 14:15 ` Keir Fraser
2009-07-28 14:47   ` Christoph Egger [this message]
2009-07-28 14:58     ` Keir Fraser
2009-07-28 15:03       ` Christoph Egger

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=200907281647.36341.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.