From: Daniel Walker <dwalker@codeaurora.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org,
"Hyok S. Choi" <hyok.choi@samsung.com>,
Tony Lindgren <tony@atomide.com>,
Jeff Ohlstein <johlstei@quicinc.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Ben Dooks <ben-linux@fluff.org>, Alan Cox <alan@linux.intel.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Feng Tang <feng.tang@intel.com>,
Tobias Klauser <tklauser@distanz.ch>,
Jason Wessel <jason.wessel@windriver.com>,
Philippe Langlais <philippe.langlais@stericsson.com>
Subject: Re: [PATCH] serial: DCC(JTAG) serial and console emulation support
Date: Thu, 07 Oct 2010 12:58:52 -0700 [thread overview]
Message-ID: <1286481532.23836.27.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <AANLkTi=8Et=Z6zrzbZa3L0MO=cBjjh7L=XU2=PDEbzWW@mail.gmail.com>
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 ..
Daniel
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-10-07 19:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 18:36 Daniel Walker
2010-10-07 19:25 ` Mike Frysinger
2010-10-07 19:39 ` Daniel Walker
2010-10-07 19:48 ` Mike Frysinger
2010-10-07 19:58 ` Daniel Walker [this message]
2010-10-07 20:02 ` Mike Frysinger
2010-10-07 20:06 ` Daniel Walker
2010-10-07 20:47 ` Mike Frysinger
2010-10-07 20:59 ` Daniel Walker
2010-10-07 21:05 ` Mike Frysinger
2010-10-07 21:17 ` Daniel Walker
2010-10-07 21:32 ` Mike Frysinger
2010-10-07 21:50 ` Daniel Walker
2010-10-07 20:52 ` Alan Cox
2010-10-07 20:37 ` Daniel Walker
2010-10-07 21:08 ` Alan Cox
2010-10-07 20:50 ` Alan Cox
2010-10-07 20:36 ` Daniel Walker
2010-10-07 21:05 ` Alan Cox
2010-10-07 20:51 ` Daniel Walker
2010-10-07 21:03 ` Mike Frysinger
2010-10-07 21:14 ` Daniel Walker
2010-10-08 8:13 ` Alan Cox
2010-10-08 15:23 ` Daniel Walker
2010-10-08 15:40 ` Greg KH
2010-10-08 16:11 ` Daniel Walker
2010-10-08 16:56 ` Alan Cox
2010-10-08 16:45 ` Daniel Walker
2010-10-08 18:38 ` Mike Frysinger
2010-10-08 19:01 ` Daniel Walker
2010-10-08 19:20 ` Mike Frysinger
2010-10-08 19:50 ` Daniel Walker
2010-10-08 22:02 ` Mike Frysinger
2010-10-08 22:22 ` Daniel Walker
2010-10-09 5:38 ` Mike Frysinger
2010-10-07 21:15 ` Greg KH
2010-10-07 21:47 ` Daniel Walker
2010-10-07 21:52 ` Greg KH
2010-10-07 22:11 ` Daniel Walker
2010-10-08 2:04 ` Mike Frysinger
2010-10-07 21:38 ` Alan Cox
2010-10-07 21:41 ` Daniel Walker
2010-10-08 8:18 ` Alan Cox
2010-10-08 15:16 ` Daniel Walker
2010-10-08 4:59 Daniel Walker
2010-10-08 6:05 ` Mike Frysinger
2010-10-08 19:34 matthieu castet
2010-10-08 19:52 ` Daniel Walker
2010-10-08 19:55 ` Daniel Walker
2010-10-08 20:40 ` matthieu castet
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=1286481532.23836.27.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=alan@linux.intel.com \
--cc=ben-linux@fluff.org \
--cc=feng.tang@intel.com \
--cc=gregkh@suse.de \
--cc=hyok.choi@samsung.com \
--cc=jason.wessel@windriver.com \
--cc=johlstei@quicinc.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.langlais@stericsson.com \
--cc=tklauser@distanz.ch \
--cc=tony@atomide.com \
--cc=vapier@gentoo.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
Powered by JetHome