public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] serial: DCC(JTAG) serial and console emulation support
Date: Wed, 13 Oct 2010 22:10:16 +0200	[thread overview]
Message-ID: <201010132210.17061.arnd@arndb.de> (raw)
In-Reply-To: <1286999522.28336.15.camel@c-dwalke-linux.qualcomm.com>

On Wednesday 13 October 2010 21:52:02 Daniel Walker wrote:
> > Seriously, I don't think you need it, but if you really do, we can probably
> > find a way to work around this by changing the base hvc driver.
> 
> I think we would have to add something that allows different major/minor
> numbers, because something that includes the name "Hypervisor" shouldn't
> be used for something general.. /dev/hvcX is also registered for "IBM
> iSeries/pSeries virtual console" (according to www.lanana.org) which is
> confusing ..

That only means we need to update the lanana entry now that the hvc driver
is used on nine different platforms (not including yours) instead of ust
pSeries. Feel free to come up with a backronym for HVC if you're
uncomfortable with the old "hypervisor console" name.

	Arnd

  reply	other threads:[~2010-10-13 20:10 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 [this message]
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=201010132210.17061.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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