From: Alex Williamson <alex.williamson@hp.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: David Vrabel <dvrabel@arcom.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial: 8250 fails to detect Exar XR16L2551 correctly
Date: Mon, 11 Jul 2005 14:00:57 -0600 [thread overview]
Message-ID: <1121112057.28557.91.camel@tdi> (raw)
In-Reply-To: <20050711204646.D1540@flint.arm.linux.org.uk>
On Mon, 2005-07-11 at 20:46 +0100, Russell King wrote:
> On Mon, Jul 11, 2005 at 01:00:08PM -0600, Alex Williamson wrote:
> > On Thu, 2005-07-07 at 14:20 +0100, David Vrabel wrote:
> >
> > > I've redid the patch and added a check for this. Alex, could you test
> > > this version, please.
> >
> > This detects the A2 ST16C255x as an XR16550, so apparently the sleep
> > check doesn't work. I contacted Exar about these two seemingly
> > identical UARTs, and they say that the A2 ST16C255x should be compatible
> > with the XR16550 so perhaps we don't need to special case the A2 UART at
> > all. Unfortunately, when I use the UART for a console, I get garbled
> > output from the time the UART is detected until we hit userspace.
>
> There was a bug in this area - does it happen with latest and greatest
> kernels?
Yes, I'm using a git pull from ~5hrs ago. How recent was the bug
fix? It worked fine before I applied David's patch, the A2 UART was
detected as a 16550A. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-07-11 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 14:19 serial: 8250 fails to detect Exar XR16L2551 correctly David Vrabel
2005-07-06 18:57 ` Russell King
2005-07-06 20:20 ` Alex Williamson
2005-07-07 13:20 ` David Vrabel
2005-07-11 19:00 ` Alex Williamson
2005-07-11 19:46 ` Russell King
2005-07-11 20:00 ` Alex Williamson [this message]
2005-07-11 20:17 ` Russell King
2005-07-11 21:17 ` Alex Williamson
2005-07-13 17:04 ` Alex Williamson
2005-07-13 18:03 ` Alex Williamson
2005-07-14 14:40 ` David Vrabel
2005-07-14 13:46 ` Russell King
2005-07-15 20:39 ` Alex Williamson
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=1121112057.28557.91.camel@tdi \
--to=alex.williamson@hp.com \
--cc=dvrabel@arcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.