From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Nishanth Menon <nm@ti.com>,
Peter Hurley <peter@hurleysoftware.com>,
Sekhar Nori <nsekhar@ti.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [RFC PATCH] ARM: omap2plus_defconfig: Switch over to using 8250 driver
Date: Mon, 13 Apr 2015 09:43:05 +0200 [thread overview]
Message-ID: <552B7389.5000505@linutronix.de> (raw)
In-Reply-To: <5529BAE7.4080808@ti.com>
On 04/12/2015 02:23 AM, Nishanth Menon wrote:
>> I think for the moment we should just freeze omap-serial and let
>> most of userspace catch up first; a lot of the official and
>> unofficial vender support is still stuck in 3.14. By the time,
>> 3.19+ is de rigueur we'll hopefully have figured out the ttyS
>> sharing and how to migrate without breaking userspace.
>>
>
> How about the folks stuck on older distros like Maemo N900?
By the time I was thinking about this, I ended up with this:
a) replace ttyOx with ttySx for the kernel console we it does not end
up dark and add a warning. This works right now however the warning
might been longer but then if one does not read it it might not
matter at all.
b) add symlink udev rule so ttySx nodes becomes ttyOx one, too
a) was mainly for people not aware of the defconfig change who end up
with the new driver without any knowledge.
b) was mainly for people for people using some kind of "pre-created"
image where you are not sure which kernel they have. They still could
use the old driver or they might have switched to the new one. This
udev rule should make sure there at least a getty on serial after the
complete boot.
Sebastian
prev parent reply other threads:[~2015-04-13 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 18:18 [RFC PATCH] ARM: omap2plus_defconfig: Switch over to using 8250 driver Nishanth Menon
2015-04-10 19:40 ` Peter Hurley
2015-04-11 18:27 ` Nishanth Menon
2015-04-11 19:40 ` Peter Hurley
2015-04-12 0:23 ` Nishanth Menon
2015-04-13 7:43 ` Sebastian Andrzej Siewior [this message]
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=552B7389.5000505@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter@hurleysoftware.com \
--cc=tony@atomide.com \
/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).