linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: DCC(JTAG) serial and console emulation support
Date: Wed, 13 Oct 2010 13:00:55 -0700	[thread overview]
Message-ID: <1287000055.28336.19.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010131551390.2764@xanadu.home>

On Wed, 2010-10-13 at 15:55 -0400, Nicolas Pitre wrote:
> > I found it independently actually .. It looks like there's at least two
> > problems. This jtag driver has a status register which flags when RX is
> > available, and TX is possible. I'm not sure this status register fits
> > into the model. The other thing is that we have a ttyJ registered for
> > this driver, and it would be nice to use that over something like ttyHVC
> > (I'm not sure if that name is correct, just a guess).
> 
> Really?  Is there a compelling reason to perpetuate this serial device 
> namespace fragmentation nonsense?  Your initial patch even had a config 
> option to hijack /dev/ttyS0 because of that.

I'm not sure how to interpret what your saying .. Are you saying we
should use /dev/hvcX or shouldn't ? the reason I want to use ttyJ is
because it was assigned specifically for jtags which, to me, makes
things a lot less confusing.

Daniel

-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-10-13 20:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 19:07 [PATCH] serial: DCC(JTAG) serial and console emulation support Daniel Walker
2010-10-06  2:55 ` Nicolas Pitre
2010-10-06 13:48   ` Daniel Walker
2010-10-06 14:22     ` Nicolas Pitre
2010-10-06 14:49       ` Daniel Walker
2010-10-06 15:21         ` Nicolas Pitre
2010-10-06 15:33           ` Daniel Walker
2010-10-06 15:47             ` Nicolas Pitre
2010-10-06 15:54               ` Daniel Walker
2010-10-06 16:22                 ` Nicolas Pitre
2010-10-06 16:40                   ` Daniel Walker
2010-10-06 17:02                     ` Nicolas Pitre
2010-10-06 17:07                       ` Daniel Walker
2010-10-07 21:27 ` Tony Lindgren
2010-10-07 21:58   ` Daniel Walker
2010-10-08  1:28     ` Nicolas Pitre
2010-10-08 20:35       ` Tony Lindgren
2010-10-08 20:59         ` Tony Lindgren
2010-10-08 21:27         ` Nicolas Pitre
2010-10-08 20:36     ` Tony Lindgren
2010-10-08  1:25   ` Nicolas Pitre
2010-10-08 20:32     ` Tony Lindgren
2010-10-08 20:58       ` Tony Lindgren
2010-10-08 21:28         ` Nicolas Pitre
2010-10-08 21:25       ` Nicolas Pitre
2010-10-08 21:49         ` Tony Lindgren
2010-10-09  0:57           ` Nicolas Pitre
2010-10-13 15:21 ` Arnd Bergmann
2010-10-13 16:17   ` Daniel Walker
2010-10-13 17:44     ` Arnd Bergmann
2010-10-13 18:08       ` Daniel Walker
2010-10-13 19:45         ` Arnd Bergmann
2010-10-13 19:52           ` Daniel Walker
2010-10-13 20:10             ` Arnd Bergmann
2010-10-13 20:24               ` Daniel Walker
2010-10-13 20:44                 ` Nicolas Pitre
2010-10-13 20:49                   ` Daniel Walker
2010-10-13 22:51                     ` Nicolas Pitre
2010-10-13 23:26                       ` Russell King - ARM Linux
2010-10-13 23:41                         ` Nicolas Pitre
2010-10-13 19:55         ` Nicolas Pitre
2010-10-13 20:00           ` Daniel Walker [this message]
2010-10-13 20:27             ` Nicolas Pitre
2010-10-13 20:47               ` Daniel Walker
2010-10-13 22:05                 ` Daniel Walker

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=1287000055.28336.19.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).