From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Mon, 24 Jun 2013 07:28:24 +0300 [thread overview]
Message-ID: <20130624042824.GQ4824@tarshish> (raw)
In-Reply-To: <CA+-urNTKwwCtPZkWaxisFbLWiYCRJA1-5COK-rT8NW3QU+kyZw@mail.gmail.com>
Hi Frank,
On Sun, Jun 23, 2013 at 11:30:12PM -0400, Frank Hunleth wrote:
> On Sun, Jun 23, 2013 at 7:13 PM, rh <richard_hubbe11@lavabit.com> wrote:
> > On Sun, 23 Jun 2013 15:21:04 -0400
> > Frank Hunleth
> > <fhunleth@troodon-software.com> wrote:
> >
> > --8<--
> >
> >> However, copying the patches over to buildroot seems wrong and painful
> >> to maintain, but as far as I can tell, there's no official/maintained
> >> git repo with the beaglebone.org kernel patches.
> >
> > This seems official to me but not sure what you mean by official.
> > Do you mean kernel.org-official? TI-official? Circuitco?
>
> I'd just like to point to a kernel that is maintained and has the
> features that I need. The one at github.com/beagleboard/kernel is the
> obvious choice since that's what's shipped on the Beaglebone Black.
>
> The point of my email is just that the github.com/beagleboard/kernel
> repository is not in a form that nicely integrates with buildroot due
> to it just containing patches for a Linux kernel. I'm just looking for
> pointers on how best to handle this.
git integrates quite nicely with Buildroot, and a lot of packages fetch their
sources from git repos. See the 'LIBFOO_SITE_METHOD' description in the
Buildroot manual (http://buildroot.net/downloads/manual/manual.html). Also
look for a github specific tip under 'Tips and tricks'.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-06-24 4:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 19:21 [Buildroot] Beaglebone Black support Frank Hunleth
2013-06-23 20:02 ` Stefan Peter
[not found] ` <20130623161357.136be827bdb312f43bda51a6@lavabit.com>
2013-06-23 23:23 ` Charles Krinke
2013-06-24 3:30 ` Frank Hunleth
2013-06-24 4:28 ` Baruch Siach [this message]
2013-06-24 12:07 ` Frank Hunleth
[not found] ` <20130623214133.6249f43e6e2d8bda20aa971a@lavabit.com>
2013-06-24 12:22 ` Frank Hunleth
[not found] ` <20130624124933.e7983d6a3730922581985bf4@lavabit.com>
2013-07-01 10:10 ` Zoltan Gyarmati
2013-07-01 13:21 ` Frank Hunleth
2013-07-02 6:07 ` Arnout Vandecappelle
2013-07-02 7:34 ` Thomas Petazzoni
2013-07-02 16:46 ` Arnout Vandecappelle
[not found] ` <20130702071112.d2bed52344e1786c14494b36@lavabit.com>
2013-07-02 21:43 ` Peter Korsgaard
2013-07-03 11:54 ` Frank Hunleth
2013-07-03 13:45 ` Peter Korsgaard
2013-07-04 8:16 ` Zoltan Gyarmati
2013-07-07 1:07 ` Frank Hunleth
2013-06-24 16:54 ` Arnout Vandecappelle
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=20130624042824.GQ4824@tarshish \
--to=baruch@tkos.co.il \
--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.