From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Intel Edison support
Date: Fri, 17 Apr 2015 09:22:02 +0200 [thread overview]
Message-ID: <5530B49A.4000206@mind.be> (raw)
In-Reply-To: <CA+-urNReEwGqR=FgyWsm9nAO=QkiTcbtfcxBaF3__eCciASM1g@mail.gmail.com>
On 17/04/15 00:50, Frank Hunleth wrote:
> On Thu, Apr 16, 2015 at 5:19 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
>>
>> On 16/04/15 14:33, Frank Hunleth wrote:
>>> Hi all,
>>>
>>> I have support for the Intel Edison working in Buildroot. It took a while to
>>> figure out everything that Intel's Yocto distribution was doing, but after you
>>> simplify it down, it doesn't seem so bad. I'd send the patch up for review, but
>>> it is dwarfed by two massive patch files on u-boot and the kernel that I had to
>>> copy from Intel's Yocto distro [1]. It seems better if BR could download the
>>> Yocto distro, extract the patch files, and use them when needed. It also doesn't
>>> seem right for BR to have to carry around a couple mega-patches. Is this
>>> possible and is there an example somewhere?
>>>
>>> If you would like to see my current patches for Edison support, they are
>>> available here: https://github.com/fhunleth/buildroot-edison.
>>
>> There is a github upload of the official Edison yocto layer at [2]. You could
>> download the relevant patches from there with BR2_LINUX_KERNEL_PATCH. When you
>> do that, please make sure that the sha is included in the URL, so [3] and not [4].
>
> Thanks. I'll try that for the kernel.
>
> At the moment, u-boot only supports patch directories, so I can't
> download the mega-patch for it. I was going to copy/paste the patch
> support from the kernel, but the kernel's patch support looks more
> involved than I expected. I'm not missing a generic patch macro
> somewhere, am I?
The complexity for linux is simply because historically it also supports
directories of patches. If you exclude that feature, it's simply:
UBOOT_PATCH += $(call qstrip,$(BR2_TARGET_UBOOT_PATCHES))
If you do that, we should probably also deprecate the current special handling
of BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR.
Actually, perhaps we should consider extending the BR2_GLOBAL_PATCH_DIR to
support some kind of URL-encoded patches. E.g. *.urlpatch, or dead symlinks to
URLs, or something. Sounds like something for Yann to work on :-)
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-17 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 12:33 [Buildroot] Intel Edison support Frank Hunleth
2015-04-16 21:19 ` Arnout Vandecappelle
2015-04-16 22:50 ` Frank Hunleth
2015-04-17 7:22 ` Arnout Vandecappelle [this message]
2015-04-17 20:29 ` Frank Hunleth
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=5530B49A.4000206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox