From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Default configuration for Ka-Ro TX25 module
Date: Tue, 22 Sep 2015 09:55:23 +0300 [thread overview]
Message-ID: <20150922065523.GD2242@tarshish> (raw)
In-Reply-To: <6bee8e0798ac4666bc051d88f2064b30@IHM-PORT-E13M01.prdhosting.local>
Hi Matthew,
On Mon, Sep 21, 2015 at 11:08:22PM +0000, Matthew Kerr wrote:
> 1) Are you aware of a default configuration which has been created for
> the TX25 module? Or is there something similar that I should start with?
Buildroot has no specific configuration for the TX25 module.
> 2) Is it possible to use the Ka-Ro supplied kernel source (and
> patches/upgrades)? Should I use it or should I just let Buildroot do its
> thing and see what happens?
You can tell Buildroot to build a kernel from vendor supplied source tree.
Just select one of the "Custom" options, or "Local directory" in the "Kernel
version" configuration choice.
Alternatively, you may build the kernel on your own as before, and use
Buildroot just for the rootfs.
In any case Buildroot can't automatically build a kernel for you, since it
lacks the required information.
> 3) Can I do anything with the Ka-Ro supplied rootfs or should I just
> let Buildroot generate this for me?
Buildroot supports helper mechanisms to ease local customization of generated
rootfs, like rootfs overlay, and post build script. See
http://nightly.buildroot.org/manual.html#customize for more details.
Hope this helps,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-09-22 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 23:08 [Buildroot] Default configuration for Ka-Ro TX25 module Matthew Kerr
2015-09-22 6:55 ` Baruch Siach [this message]
2015-09-22 7:49 ` Arnout Vandecappelle
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=20150922065523.GD2242@tarshish \
--to=baruch@tkos.co.il \
--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