Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/rpi-firmware: add configurable kernel cmdline option
Date: Mon, 10 Aug 2015 16:00:22 +0200	[thread overview]
Message-ID: <20150810160022.663a2fb7@free-electrons.com> (raw)
In-Reply-To: <1466242774.5054496.1439194348268.JavaMail.root@openwide.fr>

Dear Jeremy Rosen,

On Mon, 10 Aug 2015 10:12:28 +0200 (CEST), Jeremy Rosen wrote:

> > solution, that could be used for all bootloaders. I.e. an entry in
> > the
> > kernel menu.
> > 
> > But I'm not really a fan of this; post-build scripts have been
> > introduced just for this kind of local customisation. Others may
> > disagree, though...
> > 
> 
> I kinda disagree here...
> 
> The problem is that the kernel commandline is partly built purely by
> buildroot (for instance console=)

Not at all. Buildroot does not define console= anywhere. It uses the
kernel console as the default tty for getty, but does not anything else
beyond that: it's still up to the user to pass console= on the kernel
command line.

> and partly by the user (depending
> on the architecture, the boot partition can be manually specified)
> so having a generic way to specify "add this strin at the end of
> the kernel command line when you save the commandline wherever
> this particular architecture needs it" would be handy
> 
> Of course it can always be done with with post-build script, but
> it can sometime be tricky when what you need is to modify a string
> in a variable place that is half-generated by buildroot.

Except that there is clearly not generic way to specify the kernel
command line. Depending on the bootloader being used, the mechanism is
completely different. Even with the same bootloader (e. U-Boot), there
is typically a specific environment for each board/platform that builds
the kernel command line at runtime from various other bootloader
environment variables.

So just like Yann said: defining the kernel command line is way too
hardware/project specific to be solved by Buildroot, and it is not
something for which Buildroot would provide a lot of useful help anyway.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-10 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 15:47 [Buildroot] [PATCH 1/1] package/rpi-firmware: add configurable kernel cmdline option Ivo Slanina
2015-08-09 16:22 ` Yann E. MORIN
2015-08-10  8:12   ` Jeremy Rosen
2015-08-10 14:00     ` Thomas Petazzoni [this message]
2015-08-10 13:57   ` Thomas Petazzoni

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=20150810160022.663a2fb7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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