All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Tue, 2 Jul 2013 09:34:15 +0200	[thread overview]
Message-ID: <20130702093415.5db13282@skate> (raw)
In-Reply-To: <51D26E29.6030805@mind.be>

Dear Arnout Vandecappelle,

On Tue, 02 Jul 2013 08:07:37 +0200, Arnout Vandecappelle wrote:

>   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?

If you look at
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8/patches,
you'll see that patches are organized in a set of sub-directories, and
the patch order is defined in a shell script,
https://github.com/RobertCNelson/linux-dev/blob/am33x-v3.8/patch.sh,
that has to be executed over a Git kernel tree.

To handle such a bizarre stuff, I don't see any other option that
adding a new kconfig option to specify a shell script to be executed at
"patch" time of the kernel, so that one can do whatever funky things
(s)he wants. That's ugly, but I don't see a nice and generic way of
handling such a bizarre distribution of kernel code.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-02  7:34 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
2013-07-02  7:34               ` Thomas Petazzoni [this message]
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=20130702093415.5db13282@skate \
    --to=thomas.petazzoni@free-electrons.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 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.