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 15:17:57 -0600 [thread overview]
Message-ID: <1121116677.28557.104.camel@tdi> (raw)
In-Reply-To: <20050711211706.E1540@flint.arm.linux.org.uk>
On Mon, 2005-07-11 at 21:17 +0100, Russell King wrote:
> On Mon, Jul 11, 2005 at 02:00:57PM -0600, Alex Williamson wrote:
> > On Mon, 2005-07-11 at 20:46 +0100, Russell King wrote:
> > > 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,
>
> The fix for this went in on 21st May 2005, so obviously it's not
> actually fixed.
No, I think this is a problem with the broken A2 UARTs getting
confused in serial8250_set_sleep(). If I remove either UART_CAP_SLEEP
or UART_CAP_EFR from the capabilities list for this UART, it behaves
normally. Also, just commenting out the UART_CAP_EFR chunks of
set_sleep make it behave. I'll ping Exar for more data. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2005-07-11 21:19 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
2005-07-11 20:17 ` Russell King
2005-07-11 21:17 ` Alex Williamson [this message]
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=1121116677.28557.104.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.