From: Mike Frysinger <vapier@gentoo.org>
To: RONETIX - Asen Dimov <dimov@ronetix.at>
Cc: Daniel Walker <dwalker@codeaurora.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>,
Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@fluxnic.net>,
Tony Lindgren <tony@atomide.com>,
linux-arm-msm@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] drivers: char: hvc: add arm JTAG DCC console support
Date: Thu, 7 Apr 2011 14:57:51 -0400 [thread overview]
Message-ID: <BANLkTinTWwLB0gi0qKQfCYQ8x6PTuL9-uA@mail.gmail.com> (raw)
In-Reply-To: <4D9E04F0.5010004@ronetix.at>
On Thu, Apr 7, 2011 at 14:39, RONETIX - Asen Dimov wrote:
> On 11/30/2010 09:25 PM, Daniel Walker wrote:
>> This driver adds a basic console that uses the arm JTAG
>> DCC to transfer data back and forth. It has support for
>> ARMv6 and ARMv7.
>>
>> This console is created under the HVC driver, and should be named
>> /dev/hvcX (or /dev/hvc0 for example).
>>
>> drivers/char/Kconfig | 9 +++
>> drivers/char/Makefile | 1 +
>> drivers/char/hvc_dcc.c | 133
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>
> ...
>
> this DCC driver implements "one channel", but what about implementing
> "multiple channels". For example reserve few(3) bits for channel number,
> and two bits for carried data, then fill the rest bytes with with some data
> and send the word(32 bits) over DCC. On the Linux side writing on /dev/hvcX
> puts the number X as channel number, and on the other side the CPU
> emulator gets the data and redistribute it to TCP/IP socket.
>
> I have started write some code implementing this. Are there any one
> interested
> in this multiple channels, and are there any one started to work on it?
this sort of multiplexing of the data stream sounds like the job for
userspace ? or maybe a line discipline ? inserting structured data
into the kernel driver doesnt sound right to me ...
-mike
prev parent reply other threads:[~2011-04-07 18:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 19:25 [PATCH] drivers: char: hvc: add arm JTAG DCC console support Daniel Walker
2010-11-30 19:57 ` Nicolas Pitre
2010-11-30 21:17 ` Arnd Bergmann
2010-12-01 5:30 ` Stephen Boyd
2010-12-01 18:54 ` Daniel Walker
2010-12-01 19:28 ` Greg KH
2010-12-18 5:16 ` [PATCH] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-20 17:51 ` Daniel Walker
2010-12-20 18:39 ` Stephen Boyd
2010-12-20 18:46 ` Nicolas Pitre
2010-12-20 20:08 ` [PATCH 0/3] hvc_dcc cleanups and fixes Stephen Boyd
2010-12-20 20:08 ` [PATCH 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile Stephen Boyd
2010-12-20 21:39 ` Nicolas Pitre
2011-01-02 9:00 ` Pavel Machek
2011-01-02 18:49 ` David Brown
2011-01-03 5:50 ` Pavel Machek
2011-01-04 18:49 ` Tony Lindgren
2010-12-20 21:49 ` Arnaud Lacombe
2010-12-20 21:52 ` Stephen Boyd
2010-12-20 22:10 ` Nicolas Pitre
2010-12-20 20:08 ` [PATCH 2/3] hvc_dcc: Simplify put_chars()/get_chars() loops Stephen Boyd
2010-12-20 20:08 ` [PATCH 3/3] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-20 21:44 ` Nicolas Pitre
2011-01-04 18:52 ` Tony Lindgren
2011-01-06 1:49 ` [PATCH 0/3] hvc_dcc cleanups and fixes Stephen Boyd
2011-01-06 3:20 ` Greg KH
2011-02-03 22:17 ` Greg KH
2011-02-03 23:19 ` Stephen Boyd
2011-02-03 23:30 ` Greg KH
2011-02-03 23:48 ` [PATCHv2 " Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 2/3] hvc_dcc: Simplify put_chars()/get_chars() loops Stephen Boyd
2011-02-03 23:48 ` [PATCHv2 3/3] hvc_dcc: Simplify assembly for v6 and v7 ARM Stephen Boyd
2010-12-01 20:20 ` [PATCH] drivers: char: hvc: add arm JTAG DCC console support Stephen Boyd
2010-12-07 19:10 ` Stephen Boyd
2011-01-14 19:19 ` Tony Lindgren
2011-01-14 23:49 ` Stephen Boyd
2011-04-07 18:39 ` RONETIX - Asen Dimov
2011-04-07 18:57 ` Mike Frysinger [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=BANLkTinTWwLB0gi0qKQfCYQ8x6PTuL9-uA@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=dimov@ronetix.at \
--cc=dwalker@codeaurora.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nico@fluxnic.net \
--cc=randy.dunlap@oracle.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;
as well as URLs for NNTP newsgroup(s).