From: Chris LaRocque <clarocq@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] updating the beaglebone black defconfig
Date: Thu, 31 Dec 2015 18:51:12 -0500 [thread overview]
Message-ID: <n64f1h$ecf$1@ger.gmane.org> (raw)
In-Reply-To: 1451505684.3162125.479430882.4C107C58@webmail.messagingengine.com
Craig Swank wrote:
> Hi Chris,
> Have you been able to confirm overlays (and the device-tree) work with
> buildroot and beagleboard/linux?
>
> When 'echo BB-W1-P9.12 > /sys/devices/platform/bone_capemgr/slots' the
> w1-gpio module should get loaded and it doesn't. My overlay works as
> expected on a Robert Nelson debian beagle bone, so the overlay is not
> the problem. He also confirmed that his overlay works with
> beagleboard/linux, so the kernel isn't the problem either.
>
> I'm just curious if you've tried a custom overlay yourself and had
> success.
>
> Craig
>
>
> On Wed, Dec 30, 2015, at 10:34 AM, Chris LaRocque wrote:
>> 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
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
Hi Craig
Yes, I've built overlays and they work. I've not tried having the driver
auto load though. I always ensured the driver I needed was loaded before I
pushed the overlay to cape manager. FYI You need a patched version of DTC
for the 4.1 kernel. I've got the patch ready for buildroot review and I
should be able to push it up in an hour or so.
C
next prev parent reply other threads:[~2015-12-31 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 18:34 [Buildroot] updating the beaglebone black defconfig Chris LaRocque
2015-12-30 20:01 ` Craig Swank
2015-12-31 23:51 ` Chris LaRocque [this message]
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='n64f1h$ecf$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox