From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] First rootfile system build using buildroot
Date: Tue, 1 Sep 2015 08:58:41 +0200 [thread overview]
Message-ID: <20150901085841.3b90dd93@free-electrons.com> (raw)
In-Reply-To: <CAKpDV8stME3N6uU8n_DVUYp=sgLGr9RDk_563FCy8XQqRQSL5Q@mail.gmail.com>
Dear Dinesh Guleria,
On Tue, 1 Sep 2015 06:39:34 +0530, Dinesh Guleria wrote:
> One more question from my side if i use " Sourcery
> CodeBench 2014.05" toolchain then buildroot will download it for me or i
> have to download it manually ?
Buildroot will download it for you.
> Also if buildroot will download it then in
> this case will it be a one time process or if i make a new build for my
> rootfile system, then every time tool chain will be downloaded ?
It is a one time process. Buildroot keeps a cache of the downloaded
files into the dl/ sub-directory (which can be customized using the
BR2_DL_DIR configuration option, which is also an environment variable).
> What exactly the diffrence between using external tool chain like Sourcery
> CodeBench 2014.05" & building toolchain using crosstool-ng ?
> http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/
Sourcery CodeBench 2014.05 is a pre-built toolchain, used by a lot of
people. It's already there and available, hopefully quite well tested.
However, since it's pre-built, you cannot customize it.
Using crosstool-ng to build your toolchain allows to generate a
completely custom toolchain, tailored for your platform.
> >> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly.
>
> Will uboot be able to understand that my rootfilesystem is inside my zimage
> ? Or i have to tell uboot explicitly ?
If you're using an initramfs bundled inside the zImage, then U-Boot
does not even need to know about it. Just load the zImage in U-Boot,
start the kernel, and that's it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-01 6:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 14:37 [Buildroot] First rootfile system build using buildroot Dinesh Guleria
2015-08-31 15:18 ` Dinesh Guleria
2015-08-31 15:53 ` Lee, Tommy
2015-08-31 17:17 ` Dinesh Guleria
2015-08-31 20:58 ` Lee, Tommy
2015-09-01 1:09 ` Dinesh Guleria
2015-09-01 6:58 ` Thomas Petazzoni [this message]
2015-09-01 11:25 ` Dinesh Guleria
2015-09-01 12:02 ` Dinesh Guleria
2015-09-01 12:14 ` Vicente Olivert Riera
2015-09-01 13:23 ` Dinesh Guleria
2015-09-01 15:54 ` Lee, Tommy
2015-09-01 15:57 ` Lee, Tommy
[not found] ` <CAKpDV8uny8GAJrEkEBmMdcboOrGuVQ4G09KRtL9yuvgH1XKE=Q@mail.gmail.com>
2015-09-01 17:45 ` Lee, Tommy
2015-09-02 0:29 ` Dinesh Guleria
2015-09-02 3:38 ` Baruch Siach
2015-09-02 11:06 ` Dinesh Guleria
2015-09-02 11:47 ` Baruch Siach
2015-09-02 13:54 ` Dinesh Guleria
2015-09-02 13:59 ` Vicente Olivert Riera
2015-09-02 14:51 ` Dinesh Guleria
2015-09-02 14:55 ` Vicente Olivert Riera
2015-09-02 16:57 ` Dinesh Guleria
2015-09-02 17:16 ` Baruch Siach
2015-09-02 17:58 ` Dinesh Guleria
2015-09-02 18:13 ` Dinesh Guleria
2015-09-02 18:24 ` Samuel Martin
2015-09-01 6:56 ` Thomas Petazzoni
2015-08-31 20:45 ` 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=20150901085841.3b90dd93@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