All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Default configuration for Ka-Ro TX25 module
Date: Tue, 22 Sep 2015 09:49:07 +0200	[thread overview]
Message-ID: <560107F3.80500@mind.be> (raw)
In-Reply-To: <20150922065523.GD2242@tarshish>

On 22-09-15 08:55, Baruch Siach wrote:
> Hi Matthew,
> 
> On Mon, Sep 21, 2015 at 11:08:22PM +0000, Matthew Kerr wrote:
[snip]
>> 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.

 Note that the binaries in the Ka-Ro supplied rootfs will most likely not work,
unless you also reuse their toolchain.

 Reusing their toolchain is BTW pretty easy as well: copy the toolchain out of
the VM and install it in the same location on your host, and in buildroot select
'External toolchain', 'custom toolchain', 'pre-installed toolchain', and point
'toolchain path' to where the toolchain resided (excluding the bin/ part). Then
you'll have to specify the toolchain properties: which standard C library is
used (most likely glibc), the gcc version, and the kernel headers version. If
you make a mistake there, buildroot will tell you what is wrong.

 One possible issue you may run into is that they also have custom versions for
some of the user-space programs, e.g. for bluetooth or wifi support. If that is
the case, it is probably easiest (to start with) to use the vendor-supplied
toolchain as I described above and just copy those binaries from the
vendor-supplied rootfs.


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2015-09-22  7:49 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
2015-09-22  7:49   ` Arnout Vandecappelle [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=560107F3.80500@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.