Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] config choices in building for beaglebone black (BBB)?
Date: Mon, 20 Apr 2015 23:36:24 +0200	[thread overview]
Message-ID: <87wq16trc7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55302A4C.5050109@mind.be> (Arnout Vandecappelle's message of "Thu, 16 Apr 2015 23:31:56 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

>> also, for bleeding edge, can anyone verify whether i'm safe pushing
 >> the versions of everything right to the latest? you know:
 >> 
 >> * kernel 4.0.x
 >> * glibc 2.21
 >> * binutils 2.25
 >> * gcc 4.9.x

 >  For binutils and gcc and uClibc we typically stick to the buildroot default
 > versions (even though we don't actually test all defconfigs when we change the
 > default version for one of those...).

We don't do runtime testing (very time consuming and we don't have
access to all boards), but the defconfigs do get build tested.

 >  In case of BBB, I'm not 100% sure if all the graphics stuff from the TI kernel
 > has been fully upstreamed, so switching to a mainline kernel is not necessarily
 > acceptable. Even though the buildroot defconfig doesn't include graphics
 > support, we do want to offer a kernel that supports everything that the board has.

Indeed. That and the cape handling. It really depends on what you need
to do with the hw.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2015-04-20 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 13:03 [Buildroot] config choices in building for beaglebone black (BBB)? Robert P. J. Day
2015-04-16 21:31 ` Arnout Vandecappelle
2015-04-20 21:36   ` Peter Korsgaard [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=87wq16trc7.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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