From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building a Linux from scratch and new target architecture
Date: Tue, 19 Jan 2016 16:37:28 +0100 [thread overview]
Message-ID: <20160119163728.3dc4953c@free-electrons.com> (raw)
In-Reply-To: <1453201429564-122990.post@n4.nabble.com>
Hello,
On Tue, 19 Jan 2016 03:03:49 -0800 (PST), ronyboss wrote:
> Recently I have been working with buildroot system and openwrt system. I
First of all, make sure to not confuse Buildroot and OpenWRT. They are
completely different projects, and internally they work completely
differently.
The OpenWRT documentation improperly calls the project "OpenWRT
Buildroot" because OpenWRT was 10+ years ago a fork of Buildroot. But
nowadays, the projects have nothing in common.
> have successfully build the linux for raspberry pi and other different
> routers with my own modifications. Now I want to learn how to add custom
> Target architecture, how to add kernel for them and how to tweek rootfs, and
> how to tweek file system and others.
>
> So it would be helpful for me if anyone can provide me some information
> about these things.
If you're really talking about Buildroot (http://buildroot.org), then
please read the documentation at
https://buildroot.org/downloads/manual/manual.html. It gives all the
details about customizing the rootfs, adding more packages, configuring
the kernel, and more.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-19 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:03 [Buildroot] Building a Linux from scratch and new target architecture ronyboss
2016-01-19 15:37 ` Thomas Petazzoni [this message]
2016-01-20 16:12 ` rony
2016-01-20 19:21 ` Thomas De Schampheleire
2016-01-21 3:34 ` rony
2016-01-20 14:18 ` Thomas De Schampheleire
2016-01-20 16:14 ` rony
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=20160119163728.3dc4953c@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