mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Teresa Gámez" <t.gamez@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: bareboxenv: console bootargs
Date: Mon, 23 Feb 2015 09:01:02 +0100	[thread overview]
Message-ID: <20150223080102.GL12209@pengutronix.de> (raw)
In-Reply-To: <1424419220.4065.15.camel@lws-gamez.phytec.de>

Hi Teresa,

On Fri, Feb 20, 2015 at 09:00:20AM +0100, Teresa Gámez wrote:
> Hello,
> 
> I have noticed that the console= bootarg parameter in the latest
> enviroment is set in the /env/nv/linux.bootargs.base variable. But it is
> also set over common/console.c in the variable linux.bootargs.console
> which results here in two console= parameter:
> 
> commandline: console=ttyO0,115200n8 console=ttyO0,115200
> root=/dev/mmcblk0p2 rootfstype=ext4 rw rootwait
> 
> Wouldn't it be the right way to set the linux.bootargs.console instead
> of the linux.bootargs.base in the enviroment. If it needs to be
> overwritten at all...

Indeed, linux.bootargs.console would be a better variable for the
console bootargs. The OMAP and i.MX boards don't need this setting
because they set it in common/console.c using the linux_console_name
variable. I just sent a patch to fix that.

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:[~2015-02-23  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  8:00 Teresa Gámez
2015-02-23  8:01 ` Sascha Hauer [this message]

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=20150223080102.GL12209@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=t.gamez@phytec.de \
    /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