From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: DCC(JTAG) serial and console emulation support
Date: Fri, 8 Oct 2010 13:35:28 -0700 [thread overview]
Message-ID: <20101008203528.GN7558@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010072125440.3107@xanadu.home>
* Nicolas Pitre <nico@fluxnic.net> [101007 18:19]:
> On Thu, 7 Oct 2010, Daniel Walker wrote:
>
> > On Thu, 2010-10-07 at 14:27 -0700, Tony Lindgren wrote:
> >
> > > Can you please pass the read and write functions to the driver
> > > in platform_data? We are already booting kernels with both
> > > ARMv6 and 7 compiled in.
> >
> > What kind of situation did you want to use it in ? I was thinking about
> > how arm could have these functions in a header file, that way we
> > wouldn't duplicate in multiple places.
> >
> > > Also, as it's a driver, other architectures may want to use it too.
> >
> > I'm not sure if this model fits other architectures tho. They may not
> > have the same read/write/status sorts of stuff. Atleast I don't know
> > enough about other architectures jtags .
>
> This is ARM specific, and even not all ARM implementations have it.
Are you sure? I thought DCC is JTAG specific standard?
Tony
next prev parent reply other threads:[~2010-10-08 20:35 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 [this message]
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
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=20101008203528.GN7558@atomide.com \
--to=tony@atomide.com \
--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).