From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Tossing coins on Beaglebone Black kernel version
Date: Thu, 02 Jun 2016 21:47:19 +0200 [thread overview]
Message-ID: <87wpm7s794.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAAEAJfAnjZzOo2hZG4h=-_2mpZmqb3BUf=fkNLc08zdR9ePVWA@mail.gmail.com> (Ezequiel Garcia's message of "Thu, 2 Jun 2016 12:54:26 -0300")
>>>>> "Ezequiel" == Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> writes:
> As mentioned on IRC, beaglebone_defconfig U-Boot build is currently broken.
> I don't think the error matters much, given the selected U-Boot version
> is really old.
Yeah, our beaglebone defconfig could really use some love. It looks like
I will be getting a beaglebone green wireless so I was planning on
looking into it as well, but thanks for working on it!
> We are currently using git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
> while TI kernel release [1] notes are pointing at
> git://git.ti.com/processor-sdk/processor-sdk-linux.git.
> Now, I'm not all that sure which kernel we want to use by default and that's
> why I'm asking here, to hear what the rest thinks.
What are the beaglebone people using for their official images? Can't we
use the same?
> FWIW, I commercially support a AM335x product and we've switched to
> linux mainline,
> long, long time ago, because the SDK was incredibly crappy at that time.
Yeah, that would be my choice as well for a product. For getting started
on a beaglebone I'm less sure as mainline doesn't have any support for
the various capes.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-06-02 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:54 [Buildroot] Tossing coins on Beaglebone Black kernel version Ezequiel Garcia
2016-06-02 19:47 ` Peter Korsgaard [this message]
2016-06-02 20:49 ` Ezequiel Garcia
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=87wpm7s794.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