From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Need help with "CONFIG_CMDLINE" or setting up serial console.
Date: Thu, 24 Aug 2017 19:24:06 +0200 [thread overview]
Message-ID: <20170824192406.785ce955@windsurf> (raw)
In-Reply-To: <CANK3ZEdib88=wt7YLnhBj2XwNJA8E3eZdecN3F_SgCO8Tbv=xw@mail.gmail.com>
Hello,
On Thu, 24 Aug 2017 07:13:55 +0530, Aseem Sharma wrote:
> I have created rootfs and zImage for "arm926t" using the long term support
> release of buildroot. However I am having trouble knowing if it is working
> as I do not see any messages on the screen.
>
> How do I setup serial console on my device? I am not able to find the usual
> "CONFIG_CMDLINE" option in menuconfig to be able to set kernel command line.
CONFIG_CMDLINE is a Linux kernel option, not a Buildroot option.
In Buildroot, "make menuconfig" shows you the Buildroot options (which
architecture to use, which packages to build, which filesystem image to
generate, which kernel version and configuration to use, etc.)
If you want to access the Linux kernel configuration in the context of
Buildroot, you need to do "make linux-menuconfig". This is all
explained in the Buildroot manual, so please have a look at it.
However, using CONFIG_CMDLINE is by far not the easiest way of changing
the kernel command line. Instead, if you're using a decent bootloader,
it for sure provides a way to specify the kernel command line. Under
U-Boot for example, the bootargs variable is used for the kernel
command line value.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-24 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANK3ZEcnN1bK_LkiN-WGBcOqeRJhyPWwFjdDvAUQMefRp5QDew@mail.gmail.com>
[not found] ` <CANK3ZEeshYV1gRVEdJwFv-qJ7FW3bBS3p0Uv64EGgtiqBu=+DQ@mail.gmail.com>
[not found] ` <CANK3ZEcxuKgGCJeMxPQG6DytubWuojBieb+ApJiaW3rOrMbWzw@mail.gmail.com>
[not found] ` <CANK3ZEfboeXLiyTZs0nR_CnmOp_VOsKdZxfo_0ocUbumEr_kkA@mail.gmail.com>
[not found] ` <CANK3ZEdDRfwMSXKHHxKSHbzzxzfr1Z4dgL8eTKZSYHdKgGdjCA@mail.gmail.com>
[not found] ` <CANK3ZEcNN4dS1mhsWCPQmc1RaUrVacErJ0eeVG_rEYcoMWER+g@mail.gmail.com>
[not found] ` <CANK3ZEe8-g11nW4xsjnO8f1YX7sxOaEiVrvcTNdg3uCudgOQbw@mail.gmail.com>
[not found] ` <CANK3ZEfgerodJDfKZr0QOfo1SuSeMFGR+fqthi=u4urN-T7sPQ@mail.gmail.com>
[not found] ` <CANK3ZEeRTwNokPC8WS1VXiViQqmt6=Dpo3f_-_metsKQM3AjFg@mail.gmail.com>
2017-08-24 1:43 ` [Buildroot] Need help with "CONFIG_CMDLINE" or setting up serial console Aseem Sharma
2017-08-24 17:24 ` Thomas Petazzoni [this message]
2017-08-25 6:50 ` Aseem Sharma
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=20170824192406.785ce955@windsurf \
--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