From: Martin Peevski <martin@ronetix.at>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Re: Basic questions about using BuildRoot
Date: Thu, 20 Sep 2012 09:19:56 +0300 [thread overview]
Message-ID: <505AB58C.3030805@ronetix.at> (raw)
In-Reply-To: <5058F058.1020806@mind.be>
On 19/09/12 01:06, Arnout Vandecappelle wrote:
> On 09/17/12 12:43, Thomas De Schampheleire wrote:
>> If you're only interested in the rootfs, you could use the original,
>> working u-boot and use the rootfs from buildroot. Have you tried that?
>>
>>> >
>>> > One question beyond the theme: is it possible to build only Root FS
>>> > compatible with some external Kernel without any tool and if so
>>> how to do
>>> > that?
>
> Indeed, it is entirely possible to use buildroot to build a rootfs and
> combine it with a pre-built kernel. There is usually no dependency
> of an executable on a specific kernel version, because the kernel
> ABI is backward-compatible. When you build an internal or
> crosstool-NG toolchain in buildroot, however, do make sure that
> you use kernel headers with a sufficiently low version (smaller than
> or equal to the pre-built kernel you use).
>
> If you do want to build a custom kernel later on, you need two
> things: the source and the config. Whoever gave you the kernel
> binary is also obliged to give you the source (GPL), so that should
> be doable. The config you can usually get from the running kernel,
> in /proc/config.gz.
>
>
> Good luck!
>
> Regards,
> Arnout
>
Hi again! Thank you for the help. All my attempts to build Linux
with external version of U-boot and Kernel and the rootfs from buildroot
was unsuccessfull. However I get older directory tree and programs and
make rootfs with the Linux command mkfs.jffs2. To that moment it works,
thank for you time and help!
next prev parent reply other threads:[~2012-09-20 6:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 17:29 [Buildroot] Basic questions about using BuildRoot Martin Peevski
2012-09-15 17:50 ` Thomas De Schampheleire
[not found] ` <5054C649.6000006@ronetix.at>
2012-09-15 18:26 ` Thomas De Schampheleire
[not found] ` <5055A940.7070802@ronetix.at>
2012-09-16 11:12 ` [Buildroot] Fwd: " Thomas De Schampheleire
[not found] ` <5055C935.3050108@ronetix.at>
2012-09-17 10:43 ` Thomas De Schampheleire
2012-09-18 22:06 ` Arnout Vandecappelle
2012-09-20 6:19 ` Martin Peevski [this message]
2012-09-27 8:55 ` Martin Peevski
2012-09-27 9:53 ` Thomas Petazzoni
2012-09-27 10:42 ` Arnout Vandecappelle
2012-09-27 11:57 ` Martin Peevski
2012-09-27 12:21 ` Thomas Petazzoni
2012-09-28 14:02 ` Martin Peevski
2012-09-29 13:17 ` Martin Peevski
2012-09-29 13:57 ` Stephan Hoffmann
2012-09-29 14:09 ` Martin Peevski
2012-09-29 14:14 ` Stephan Hoffmann
2012-10-01 8:14 ` Martin Peevski
2012-10-01 8:29 ` Stephan Hoffmann
2012-10-01 8:40 ` Samuel Martin
2012-10-01 9:06 ` Martin Peevski
2012-10-01 9:11 ` Samuel Martin
2012-10-01 9:17 ` Martin Peevski
2012-10-01 12:51 ` Martin Peevski
2012-10-03 15:05 ` Martin Peevski
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=505AB58C.3030805@ronetix.at \
--to=martin@ronetix.at \
--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