From: Kyle McMartin <kyle@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Kyle McMartin <kyle@infradead.org>,
linux-kernel@vger.kernel.org, karthik.manamcheri@gmail.com,
torvalds@linuxfoundation.org
Subject: Re: Revert "serial: 8250: Make SERIAL_8250_RUNTIME_UARTS work correctly"
Date: Mon, 3 Jun 2013 13:03:22 -0400 [thread overview]
Message-ID: <20130603170322.GF8270@merlin.infradead.org> (raw)
In-Reply-To: <20130603165531.GA20412@kroah.com>
On Mon, Jun 03, 2013 at 09:55:31AM -0700, Greg KH wrote:
> On Mon, Jun 03, 2013 at 09:38:26AM -0400, Kyle McMartin wrote:
> > This reverts commit cfcec52e9781f08948c6eb98198d65c45be75a70.
> >
> > This regresses a longstanding behaviour on X86 systems, which end up with
> > PCI serial ports moving between ttyS4 and ttyS0 when you bisect to opposite
> > sides of this commit, resulting in the need to constantly modify the console
> > setting in order to bisect across it.
> >
> > Please revert, we can work on solving this for ARM platforms in a less
> > disruptive way.
>
> Ugh, how did this break x86 systems? Karthik, you said this wouldn't
> affect anyone else, what did you test it on?
>
> > Signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
>
> I'll go queue this up for the next -rc release, thanks Kyle.
>
No worries, I undertand what Karthik is talking about, so I'll try to
figure this out.
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
is what was set in my .config, resulting in:
[3.9.y]
0: uart:16550A port:00001030 irq:16 tx:16522 rx:0 RTS|CTS|DTR|CD
1: uart:unknown port:000002F8 irq:3
2: uart:unknown port:000003E8 irq:4
3: uart:unknown port:000002E8 irq:3
[3.10-rc2]
0: uart:unknown port:000003F8 irq:4
1: uart:unknown port:000002F8 irq:3
2: uart:unknown port:000003E8 irq:4
3: uart:unknown port:000002E8 irq:3
4: uart:16550A port:00001030 irq:16 tx:16226 rx:0 RTS|CTS|DTR|CD
There's undeniably something wrong if RUNTIME_UARTS=0 doesn't result
in his serial ports showing up, I'll try to help debug that, but I
think the 3.9 behaviour is desireable if no "legacy" uarts are found.
regards, Kyle
next prev parent reply other threads:[~2013-06-03 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 13:38 Kyle McMartin
2013-06-03 16:55 ` Greg KH
2013-06-03 17:03 ` Kyle McMartin [this message]
2013-06-03 17:09 ` Greg KH
[not found] ` <CAES2cWxYsxgjWzgNuhrWDoC7t2XrZQdeTe47ftWaCdg-2QoHUg@mail.gmail.com>
2013-06-03 20:32 ` Greg KH
[not found] ` <CAES2cWwPSpsqYdBHH51gVsCFdh_YVnADwzU+SKXqgzQwZMUVEA@mail.gmail.com>
2013-06-03 21:37 ` Greg KH
2013-06-03 20:05 Karthik Manamcheri
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=20130603170322.GF8270@merlin.infradead.org \
--to=kyle@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=karthik.manamcheri@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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
all inboxes | Powered by JetHome®