From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 2 Jul 2013 09:34:15 +0200 Subject: [Buildroot] Beaglebone Black support In-Reply-To: <51D26E29.6030805@mind.be> References: <20130623161357.136be827bdb312f43bda51a6@lavabit.com> <20130623214133.6249f43e6e2d8bda20aa971a@lavabit.com> <20130624124933.e7983d6a3730922581985bf4@lavabit.com> <51D155A0.3010205@gmail.com> <51D26E29.6030805@mind.be> Message-ID: <20130702093415.5db13282@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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