Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: kernel 5.19.8: "Oxford Semiconductor Ltd OXPCIe952 Dual Native 950 UART" gets wrong baudrate (PCI ID 1415:c158)
Date: Tue, 4 Oct 2022 21:14:28 -0000 (UTC)	[thread overview]
Message-ID: <thi7nk$tpq$1@ciao.gmane.io> (raw)
In-Reply-To: thi5m6$j7r$1@ciao.gmane.io

On 2022-10-04, Grant Edwards <grant.b.edwards@gmail.com> wrote:

> I just ran into what I think is the same problem when upgrading from
> 5.10.76 to 5.15.68 (sorry I don't have any intermediate kernel
> versions to test with). This is an oxford quad 950 board that has
> worked flawlessly for many years. Now the baud rates are all wrong.
>
> [...]

After reading through the thread a third time, I tried enabling
CONFIG_SERIAL_8250_16550A_VARIANTS in my 6.15.69 kernel, and my	quad
Oxford board works again.

The first two times I read through the thread I misunderstood the statement

    Can you please confirm that you have the
    CONFIG_SERIAL_8250_16550A_VARIANTS option disabled (default to
    "off" for x86 only)?

as meaning that you should disable that option as a prerequisite to
making it work. So I checked to make sure it was disabled (it
was). Yes, it's obvious now what was meant was that having it disabled
explains the previous observations.

--
Grant









  reply	other threads:[~2022-10-04 21:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 19:59 kernel 5.19.8: "Oxford Semiconductor Ltd OXPCIe952 Dual Native 950 UART" gets wrong baudrate (PCI ID 1415:c158) Anders Blomdell
2022-09-13  8:21 ` Greg Kroah-Hartman
2022-09-13 12:16   ` Anders Blomdell
2022-09-13 12:30     ` Greg Kroah-Hartman
2022-09-13 12:43       ` Anders Blomdell
2022-09-13 14:01         ` Greg Kroah-Hartman
2022-09-13 15:34           ` Anders Blomdell
2022-09-13 16:19             ` Maciej W. Rozycki
2022-09-13 17:17               ` Anders Blomdell
2022-09-16 21:50                 ` Maciej W. Rozycki
2022-09-13 18:59               ` Anders Blomdell
2022-09-13 21:07               ` Anders Blomdell
2022-09-14  0:00                 ` Maciej W. Rozycki
2022-09-14 11:01                   ` Anders Blomdell
2022-09-14 11:41                     ` Maciej W. Rozycki
2022-09-14 14:15                       ` Maciej W. Rozycki
2022-09-14 14:22                         ` Anders Blomdell
2022-09-16 21:03                           ` Maciej W. Rozycki
2022-09-19  6:50                             ` Anders Blomdell
2022-09-14 14:57                         ` Greg Kroah-Hartman
2022-09-15 10:09                           ` Anders Blomdell
2022-09-16 21:03                             ` Maciej W. Rozycki
2022-10-04 20:39     ` Grant Edwards
2022-10-04 21:14       ` Grant Edwards [this message]
2022-10-05 10:02       ` Ilpo Järvinen

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='thi7nk$tpq$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=linux-serial@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