From: Timur Tabi <timur@freescale.com>
To: Timur Tabi <timur@freescale.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: powerpc: udbg based backend for hvc_console
Date: Tue, 18 Nov 2008 09:06:17 -0600 [thread overview]
Message-ID: <4922D9E9.5020204@freescale.com> (raw)
In-Reply-To: <20081118051408.GM26336@yookeroo.seuss>
David Gibson wrote:
> Given the variety of strange I/O configurations in prototype and
> embedded platforms, I can't imagine this was a unique situation. So
> I've pushed my patch out, so anyone else in a similar situation can
> immediately turn their little udbg methods for whatever strange I/O
> they have into a fully-functional console. Maybe it's not something
> you'd want to go to release with, but it certainly simplifies life
> during bringup.
Ok, I understand now. However, I would like to see two changes:
1) Re-arrange the Makefile as I pointed out in another post.
2) Update the Kconfig help file to be very clear that this feature is only
meaningful if the platform has a udbg back-end but no other console or TTY driver.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-11-18 15:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 3:54 powerpc: udbg based backend for hvc_console David Gibson
2008-11-05 4:53 ` Paul Mackerras
2008-11-06 0:20 ` David Gibson
2008-11-17 19:41 ` Timur Tabi
2008-11-18 0:28 ` David Gibson
2008-11-17 20:04 ` Timur Tabi
2008-11-18 0:40 ` David Gibson
2008-11-18 4:42 ` Timur Tabi
2008-11-18 5:14 ` David Gibson
2008-11-18 15:06 ` Timur Tabi [this message]
2008-11-19 0:42 ` David Gibson
2008-11-19 15:20 ` Timur Tabi
2008-11-20 19:07 ` Milton Miller
2008-11-20 19:16 ` Timur Tabi
2008-11-21 0:23 ` David Gibson
2008-11-21 15:57 ` Milton Miller
2008-11-21 16:13 ` Timur Tabi
2008-11-21 19:09 ` Milton Miller
2008-11-21 0:35 ` David Gibson
2008-11-21 19:29 ` Milton Miller
2008-11-17 20:18 ` Timur Tabi
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=4922D9E9.5020204@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).