Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Generating a defconfig
Date: Mon, 21 Sep 2015 22:54:37 +0200	[thread overview]
Message-ID: <20150921205437.GE3570@free.fr> (raw)
In-Reply-To: <20150921190806.5b845258@free-electrons.com>

Joao, Thomas, All,

On 2015-09-21 19:08 +0200, Thomas Petazzoni spake thusly:
> On Mon, 21 Sep 2015 17:12:19 +0100, Joao Pinto wrote:
> > I am about to generate a buildroot' defconfig for ARM Juno r1 board, and I would
> > like to know what is the std procedure to make this on buildroot.
> 
> Just create your Buildroot configuration, and then run:
> 
> 	make savedefconfig
> 
> It will create a file named 'defconfig', which you can simply move to
> configs/<foo>_defconfig.
> 
> You can also do it in one step like this:
> 
> 	make BR2_DEFCONFIG=configs/<foo>_defconfig savedefconfig
> 
> Note that for the board defconfig, we have a few rules in Buildroot:
> 
>  * The version of the kernel headers and kernel must be fixed (you
>    should not use the "latest version" option)
> 
>  * The configuration should be minimal, i.e nothing but the default
>    userspace package (just Busybox).

To complement what Thomas said:

    ... and just the minimal set of packages that make the board boot
    (e.g. the bootloader, a hardware blob and such low-level stuff).

For example, the raspberrypi defconfig files also enable the
rpi-firmware package, because it contains the bootloader blob.

Otherwise, as Thomas said: nothing fancy. The strictly minimum to get
the board up to a shell.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-09-21 20:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 16:12 [Buildroot] Generating a defconfig Joao Pinto
2015-09-21 17:01 ` Lee, Tommy
2015-09-21 17:03   ` Joao Pinto
2015-09-21 17:07     ` Lee, Tommy
2015-09-21 17:07       ` Joao Pinto
2015-09-21 17:06   ` Thomas Petazzoni
2015-09-21 17:08 ` Thomas Petazzoni
2015-09-21 20:54   ` Yann E. MORIN [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=20150921205437.GE3570@free.fr \
    --to=yann.morin.1998@free.fr \
    --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