From: Timur Tabi <timur@freescale.com>
To: Milton Miller <miltonm@bga.com>
Cc: linux-ppc <linuxppc-dev@ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: powerpc: udbg based backend for hvc_console
Date: Fri, 21 Nov 2008 10:13:26 -0600 [thread overview]
Message-ID: <4926DE26.7030607@freescale.com> (raw)
In-Reply-To: <22538ec7f241b37d1dfcb94188d414e8@bga.com>
Milton Miller wrote:
> We want the last console= parameter on the command line to win. So if
> that implys the last call to add_preferred_console wins, then you have
> code overriding the command line.
Hmm, good point. However, how likely is it that we'll have more than one
console driver? Also, without calling add_preferred_console(), the kernel needs
to have a console= on the command line.
In my case, my driver only calls add_preferred_console() if the device tree
contains a specific property that it looks for. In effect, this property
override the console= line. However, the console= line goes to the HVC
subsystem, and not my driver, and I can't use it to send the configuration data
the driver needs.
Unfortunately, my driver hasn't been published yet, so it's hard to explain the
details. I guess I need to think about this more.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-11-21 16:13 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
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 [this message]
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=4926DE26.7030607@freescale.com \
--to=timur@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.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).