[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=j2n-X+-zkas8HdL1awo7Lcyxwofts6FjU8vj6@mail.gmail.com>
Date: Thu, 7 Oct 2010 16:02:30 -0400
From: Mike Frysinger <vapier@...too.org>
To: Daniel Walker <dwalker@...eaurora.org>
Cc: linux-kernel@...r.kernel.org,
"Hyok S. Choi" <hyok.choi@...sung.com>,
Tony Lindgren <tony@...mide.com>,
Jeff Ohlstein <johlstei@...cinc.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Ben Dooks <ben-linux@...ff.org>,
Alan Cox <alan@...ux.intel.com>,
Kukjin Kim <kgene.kim@...sung.com>,
Feng Tang <feng.tang@...el.com>,
Tobias Klauser <tklauser@...tanz.ch>,
Jason Wessel <jason.wessel@...driver.com>,
Philippe Langlais <philippe.langlais@...ricsson.com>
Subject: Re: [PATCH] serial: DCC(JTAG) serial and console emulation support
On Thu, Oct 7, 2010 at 15:58, Daniel Walker wrote:
> On Thu, 2010-10-07 at 15:48 -0400, Mike Frysinger wrote:
>> i dont think hijacking the "ttyS" namespace is acceptable, even if
>> it's behind a Kconfig. other people have tried in the past (myself
>> included) and been shot down. sounds like a shim for crappy userspace
>> apps that blindly assume /dev/ttyS*. is that really an issue anymore
>> though now that things like /dev/ttyUSB* are so common and people are
>> used to picking between multiple serial sources ?
>
> It also creates a ttyJ* which uses the same interfaces as the code for
> ttyS* .. I don't think allowing a Kconfig option to shim this in as a
> ttyS* is all that bad .. This driver is only going to be used in rare
> cases for debugging , having a ttyS* is just a level of flexibility ..
how is that any different from:
ln -s ttyJ0 /dev/ttyS0
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists