Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Tue, 02 Jul 2013 08:07:37 +0200	[thread overview]
Message-ID: <51D26E29.6030805@mind.be> (raw)
In-Reply-To: <51D155A0.3010205@gmail.com>

On 07/01/13 12:10, Zoltan Gyarmati wrote:
> checked the linked config from fhunleth, it seems in the used kernel
> tree (
> http://files.troodon-software.com/br/beagleboard-kernel-b37928553c8de3598d8a259d7ce5c4be713c2908.tar.xz
> ), the usb and the ethernet support is broken (or, as it always
> possible, i failed something).
>   So to get a working kernel, i used the patchset from
> https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8  ,
> ( which patches are extracted from the Angstrom build tree ), applied
> them manually on the mainline tree, created a tarball, and used that to
> build with Buildroot.
> So far everything works well (UART,USB host/gadget, ethernet, GPIO
> tested). I wondering, would it be possible to apply those subdir-style (
> https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8/patches  )
> patches automatically in Buildroot on an elegant way? Or better to
> create a git tree with applied patches somewhere online and use that in
> Buildroot?

  I guess you can download the patches as a tarball, right? Then you 
should just be able to use the tarball's URL in BR2_LINUX_KERNEL_PATCH 
and buildroot will extract them from the tarball and apply them all in 
directory order (or according to the series file, if present). Or does 
that not work for some reason?

  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

  parent reply	other threads:[~2013-07-02  6:07 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
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 [this message]
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=51D26E29.6030805@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