From: Timur Tabi <timur@freescale.com>
To: Yoder Stuart <stuart.yoder@freescale.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
paulus@samba.org, miltonm@bga.com,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function
Date: Thu, 07 Aug 2008 13:11:49 -0500 [thread overview]
Message-ID: <489B3AE5.109@freescale.com> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA3043BC7D7@az33exm25.fsl.freescale.net>
Yoder Stuart wrote:
> The second was the idea that we may need a /aliases/stdin as well.
> You could conceptually have stdout be a monitor and a stdin
> be a keyboard.
I don't think the hypervisor console subsystem supports this. I don't see any
way of registering separate clients for input vs. output.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-08-07 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080806055214.30717.86092.stgit@trillian.secretlab.ca>
[not found] ` <20080806060239.30717.79273.stgit@trillian.secretlab.ca>
[not found] ` <20080805.233205.201125898.davem@davemloft.net>
[not found] ` <18585.31504.836857.829592@cargo.ozlabs.ibm.com>
2008-08-06 13:31 ` [RFC/PATCH 2/3] of: add of_lookup_stdout() utility function Grant Likely
2008-08-06 16:25 ` Segher Boessenkool
2008-08-06 17:09 ` Mitch Bradley
2008-08-07 0:40 ` David Gibson
2008-08-07 22:35 ` Benjamin Herrenschmidt
[not found] ` <ed82fe3e0808060946v39992095pfb6b85726b7d307d@mail.gmail.com>
[not found] ` <20080807061254.GB12571@yookeroo.seuss>
2008-08-07 17:28 ` Yoder Stuart
2008-08-07 18:11 ` Timur Tabi [this message]
2008-08-07 19:20 Milton Miller
2008-08-07 19:22 ` Timur Tabi
[not found] ` <489B4B89.1010507-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-08-07 19:38 ` Scott Wood
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=489B3AE5.109@freescale.com \
--to=timur@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=paulus@samba.org \
--cc=stuart.yoder@freescale.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