public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Ramsay <jim.ramsay@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in 8520.c - port.type not set for serial console
Date: Mon, 6 Jun 2005 09:03:50 -0600	[thread overview]
Message-ID: <4789af9e0506060803161a8382@mail.gmail.com> (raw)
In-Reply-To: <200505311625.46084.bjorn.helgaas@hp.com>

On 5/31/05, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Monday 30 May 2005 4:38 pm, Jim Ramsay wrote:
> > I am attempting to get the 8520.c driver's serial console working with
> > a 16550A UART implementation, and have run into what I consider to be
> > a bug:  In short, the proper 'port.type' for this serial port is not
> > set until the module init (serial8250_init) is called, so the FCR is
> > set incorrectly during serial8250_console_init for any port type which
> > is different than UNKNOWN.
> >
> > The exact problem is that the FCR is being set to '0x0' for a port
> > type of 'UNKNOWN', when for my specific 16550A, it should be set to
> > '0xC1' - and this makes my screen fill with empty characters instead
> > of the printk output I need.
> 
> Shouldn't a 16550A UART work correctly with FCR==0x0, i.e., with FIFOs
> disabled?  Is your UART broken?

That's a good question.  I'll me looking into this in the near future.

> Serial console output is always polled, one character at a time, so
> you shouldn't need FIFOs until later.

True, as long as it works that way... so far I haven't seen it
actually function properly yet with FCR set to 0.

-- 
Jim Ramsay
"Me fail English?  That's unpossible!"

  reply	other threads:[~2005-06-06 15:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 22:38 Bug in 8520.c - port.type not set for serial console Jim Ramsay
2005-05-31 22:25 ` Bjorn Helgaas
2005-06-06 15:03   ` Jim Ramsay [this message]
2005-06-06 15:55     ` Bjorn Helgaas

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=4789af9e0506060803161a8382@mail.gmail.com \
    --to=jim.ramsay@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.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