mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: How to disable console late?
Date: Thu, 26 Jun 2014 07:52:09 +0200	[thread overview]
Message-ID: <20140626055209.GU15686@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mEx4SW8gCjmxB8kTFypgAbm8GbfaMk9UcZRj5jF3y4uvg@mail.gmail.com>

On Wed, Jun 25, 2014 at 06:22:04PM +0200, Holger Schurig wrote:
> On my i.MX6 I have CONFIG_CONSOLE_FULL and CONSOLE_ACTIVATE_NONE
> defined. But still my serial is automatically activated as a console.
> 
> barebox:/ devinfo cs0
> Bus: platform
> Parameters:
>   baudrate: 115200
>   active: ioe
> 
> I'd rather active the serial port as a console only if a key is
> pressed during power on. Based on the help text of
> CONFIG_ACTIVATE_NONE, I actually thought that this would happen.
> 
> Any hints?
> 
> 
> I could remove chosen/stdout-path from my DTS and put it in
> on-the-fly? This sounds a bit ugly ...

Indeed you have to remove the stdout-path property from DTS. You don't
have to add it back, 'cs0.active=ioe' should do it. Note we currently
don't have persistent names for the console devices which means that
cs0 is whatever is probed first.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-06-26  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 16:22 Holger Schurig
2014-06-26  5:52 ` Sascha Hauer [this message]
2014-07-04  7:51 ` Jean-Christophe PLAGNIOL-VILLARD

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=20140626055209.GU15686@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=holgerschurig@gmail.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