From: Chris LaRocque <clarocq@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] updating the beaglebone black defconfig
Date: Wed, 30 Dec 2015 13:34:35 -0500 [thread overview]
Message-ID: <n6183t$ket$1@ger.gmane.org> (raw)
Hello
I'm working to update the beaglebone defconfig to kernel 4.1.13 ti 36 branch
(github.com/beagleboard/linux).
The build works but I want to incorporate a patched version of DTC
(github.com/pantoniou/dtc/tree/dt-overlays5) to support the cape manager and
device tree overlay changes. At this pont I'd appreciate some guidance.
My first thought was to simply patch the buildroot dtc package files to pull
from the new location. This looks to be the most direct, probably only
requiring that place the file in board/beaglebone/patches/dtc?
Second, try to dynamically create a patch for the mainline dtc to the bb.org
fork. Haven't thought this through yet. A pointer or two would be
appreciated. I thought to use 'git diff'?
Regards
Chris
next reply other threads:[~2015-12-30 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 18:34 Chris LaRocque [this message]
2015-12-30 20:01 ` [Buildroot] updating the beaglebone black defconfig Craig Swank
2015-12-31 23:51 ` Chris LaRocque
2016-01-01 18:42 ` Craig Swank
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='n6183t$ket$1@ger.gmane.org' \
--to=clarocq@gmail.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 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.