From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Mon, 24 Jun 2013 07:28:24 +0300 Subject: [Buildroot] Beaglebone Black support In-Reply-To: References: <20130623161357.136be827bdb312f43bda51a6@lavabit.com> Message-ID: <20130624042824.GQ4824@tarshish> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 wrote: > > On Sun, 23 Jun 2013 15:21:04 -0400 > > Frank Hunleth > > 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 -