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: Wed, 06 Jul 2005 14:20:31 -0600 [thread overview]
Message-ID: <1120681231.14959.3.camel@tdi> (raw)
In-Reply-To: <20050706195740.A28758@flint.arm.linux.org.uk>
On Wed, 2005-07-06 at 19:57 +0100, Russell King wrote:
> On Tue, Jul 05, 2005 at 03:19:40PM +0100, David Vrabel wrote:
> > The 8250 serial driver detects the Exar XR16L2551 as a 16550A. The
> > XR16L2551 has an EFR register and sleep capabilities (UART_CAP_FIFO |
> > UART_CAP_EFR | UART_CAP_SLEEP). However, broken_efr() thinks it's a
> > buggy Exar ST16C255x.
>
> Grumble!
Double grumble...
> > Perhaps it's okay for the ST16C255x to be detected as something with
> > UART_CAP_EFR | UART_CAP_SLEEP even if it doesn't work? i.e., by removing
> > broken_efr().
>
> I don't know - maybe Alex Williamson can try your patch out.
I can, but not till next week when I can get into the office and dig
up the box with the broken A2 rev UARTs. Let me know if you need an
answer before then. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-07-06 20:28 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 [this message]
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
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=1120681231.14959.3.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 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).