From: Greg KH <gregkh@linuxfoundation.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Robert Nelson <robertcnelson@gmail.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
linux-serial@vger.kernel.org, Alan Cox <alan@linux.intel.com>
Subject: Re: [RFC] possible removal of omap-serial
Date: Fri, 21 Mar 2014 10:44:48 -0700 [thread overview]
Message-ID: <20140321174448.GA4716@kroah.com> (raw)
In-Reply-To: <20140321173653.GP12310@saruman.home>
On Fri, Mar 21, 2014 at 12:36:53PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Fri, Mar 21, 2014 at 10:10:30AM -0700, Tony Lindgren wrote:
> > > > On the support side, I'm not looking forward to this for beagle/panda
> > > > users. We've already converted them once from ttySx -> ttyOx back in
> > > > 2.6.33/2.6.34? days. That was an irc/email/u-boot/kernel nightmare...
> > >
> > > that's exactly why we're talking about ways to maintain backwards
> > > compatibility here. But I'm more interested in finding a way to switch
> > > over to ttyS and have a symlink to ttyO, that way a simple debootstrap
> > > (or any other ARM distro minimal rootfs) would work out of the box,
> > > without any changes, just like in "normal" systems.
> >
> > Yeah let's not break things. The symlink solution won't work for kernel
>
> again. Let's not break things again.
>
> > console output so it needs to be dealt with some other way.
>
> it would if kernel itself would create the symlink, but that might not
> be doable in a clean way.
The kernel isn't going to create the symlink, sorry, no.
prev parent reply other threads:[~2014-03-21 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 23:52 [RFC] possible removal of omap-serial Felipe Balbi
2014-03-21 0:04 ` Alan Cox
2014-03-21 0:12 ` Greg KH
2014-03-21 1:35 ` Felipe Balbi
2014-03-21 1:37 ` Felipe Balbi
2014-03-21 2:36 ` Greg KH
2014-03-21 2:45 ` Robert Nelson
2014-03-21 2:52 ` Felipe Balbi
2014-03-21 17:10 ` Tony Lindgren
2014-03-21 17:36 ` Felipe Balbi
2014-03-21 17:44 ` Greg KH [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=20140321174448.GA4716@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robertcnelson@gmail.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