[Buildroot] Kernel patches in Buildroot

[Buildroot] Kernel patches in Buildroot

[Joao Pinto]

Hi,
We are designing the procedure to release our software stack based on buildroot.
Could you please tell what is the advised method for including a kernel patch
set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?

Thanks for your help!

Joao

[Buildroot] Kernel patches in Buildroot

[Arnout Vandecappelle]

On 11-11-15 12:35, Joao Pinto wrote:
> Hi,
> We are designing the procedure to release our software stack based on buildroot.
> Could you please tell what is the advised method for including a kernel patch
> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?

 I personally prefer to use a git repository that includes the patches. During
development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
release, I point to the repository (often on gitlab) and specify a tag.

 BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
can specify a directory with the latter as well.


 Regards,
 Arnout

> 
> Thanks for your help!
> 
> Joao
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 


-- 
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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Kernel patches in Buildroot

[Yegor Yefremov]

On Wed, Nov 11, 2015 at 1:04 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 11-11-15 12:35, Joao Pinto wrote:
>> Hi,
>> We are designing the procedure to release our software stack based on buildroot.
>> Could you please tell what is the advised method for including a kernel patch
>> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
>> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?
>
>  I personally prefer to use a git repository that includes the patches. During
> development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
> release, I point to the repository (often on gitlab) and specify a tag.
>
>  BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
> can specify a directory with the latter as well.

You can also create a BSP repository containing patches, configs and
so on and just instruct customers to use BR2_EXTERNAL feature
(http://nightly.buildroot.org/manual.html#outside-br-custom).

Yegor

[Buildroot] Kernel patches in Buildroot

[Joao Pinto]

Thanks for your help!

On 11/11/2015 12:04 PM, Arnout Vandecappelle wrote:
> On 11-11-15 12:35, Joao Pinto wrote:
>> Hi,
>> We are designing the procedure to release our software stack based on buildroot.
>> Could you please tell what is the advised method for including a kernel patch
>> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
>> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?
> 
>  I personally prefer to use a git repository that includes the patches. During
> development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
> release, I point to the repository (often on gitlab) and specify a tag.
> 
>  BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
> can specify a directory with the latter as well.
> 
> 
>  Regards,
>  Arnout
> 
>>
>> Thanks for your help!
>>
>> Joao
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
> 
> 

[Buildroot] Kernel patches in Buildroot

[Joao Pinto]

Hi!
I am trying to use BR2_GLOBAL_PATCH_DIR to indicate the global patch directory,
which has the following value:

BR2_GLOBAL_PATCH_DIR="snps-custom/packages"

I have a "snps-custom" folder which has a "packages" folder inside. Inside the
"packages" folder we have a folder for each package we need to patch, in this
example mplayer and the linux kernel.

--snps-custom
  --packages
    --linux-arc-axs101-20141021-3.13
	0001-XXXX.patch
	0002-YYYY.patch
    --mplayer
	0001-mplayer.patch
    --<packagename>
	000x-xxxxx.patch

The linux kernel patching system does not recognizes the
packages/linux-arc-axs101-20141021-3.13 patch folder. Could you give me a help
on this?

Thanks!

BR,
Joao Pinto



On 11/17/2015 11:13 AM, Joao Pinto wrote:
> Thanks for your help!
> 
> On 11/11/2015 12:04 PM, Arnout Vandecappelle wrote:
>> On 11-11-15 12:35, Joao Pinto wrote:
>>> Hi,
>>> We are designing the procedure to release our software stack based on buildroot.
>>> Could you please tell what is the advised method for including a kernel patch
>>> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
>>> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?
>>
>>  I personally prefer to use a git repository that includes the patches. During
>> development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
>> release, I point to the repository (often on gitlab) and specify a tag.
>>
>>  BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
>> can specify a directory with the latter as well.
>>
>>
>>  Regards,
>>  Arnout
>>
>>>
>>> Thanks for your help!
>>>
>>> Joao
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>
>>
>>
> 

[Buildroot] Kernel patches in Buildroot

[David Van Arnem]

On 11/17/2015 10:13 AM, Joao Pinto wrote:
>
> Hi!
> I am trying to use BR2_GLOBAL_PATCH_DIR to indicate the global patch directory,
> which has the following value:
>
> BR2_GLOBAL_PATCH_DIR="snps-custom/packages"
>
> I have a "snps-custom" folder which has a "packages" folder inside. Inside the
> "packages" folder we have a folder for each package we need to patch, in this
> example mplayer and the linux kernel.
>
> --snps-custom
>    --packages
>      --linux-arc-axs101-20141021-3.13
> 	0001-XXXX.patch
> 	0002-YYYY.patch
>      --mplayer
> 	0001-mplayer.patch
>      --<packagename>
> 	000x-xxxxx.patch
>
> The linux kernel patching system does not recognizes the
> packages/linux-arc-axs101-20141021-3.13 patch folder. Could you give me a help
> on this?

I haven't done this myself, so I'm not completely sure if this is 
correct, but there's an option to add custom kernel patches under 
menuconfig -> Kernel -> Custom kernel patches.  I think to patch the 
kernel you would need to set that value to the 
snps-custom/packages/linux-arc-axs... path.

David

>
> Thanks!
>
> BR,
> Joao Pinto
>
>
>
> On 11/17/2015 11:13 AM, Joao Pinto wrote:
>> Thanks for your help!
>>
>> On 11/11/2015 12:04 PM, Arnout Vandecappelle wrote:
>>> On 11-11-15 12:35, Joao Pinto wrote:
>>>> Hi,
>>>> We are designing the procedure to release our software stack based on buildroot.
>>>> Could you please tell what is the advised method for including a kernel patch
>>>> set in buildroot? I typically use BR2_LINUX_KERNEL_PATCH where I indicate each
>>>> patch file. Is there a easier way like using BR2_GLOBAL_PATCH_DIR for example?
>>>
>>>   I personally prefer to use a git repository that includes the patches. During
>>> development, I make a local checkout specified with LINUX_OVERRIDE_SRCDIR; for
>>> release, I point to the repository (often on gitlab) and specify a tag.
>>>
>>>   BR2_GLOBAL_PATCH_DIR and BR2_LINUX_KERNEL_PATCH are basically equivalent, you
>>> can specify a directory with the latter as well.
>>>
>>>
>>>   Regards,
>>>   Arnout
>>>
>>>>
>>>> Thanks for your help!
>>>>
>>>> Joao
>>>> _______________________________________________
>>>> buildroot mailing list
>>>> buildroot at busybox.net
>>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>>
>>>
>>>
>>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
Thanks,
David

[Buildroot] Kernel patches in Buildroot

[Thomas Petazzoni]

Dear Joao Pinto,

On Tue, 17 Nov 2015 17:13:31 +0000, Joao Pinto wrote:

> BR2_GLOBAL_PATCH_DIR="snps-custom/packages"
> 
> I have a "snps-custom" folder which has a "packages" folder inside. Inside the
> "packages" folder we have a folder for each package we need to patch, in this
> example mplayer and the linux kernel.
> 
> --snps-custom
>   --packages
>     --linux-arc-axs101-20141021-3.13

Call this folder just "linux". The folder must be named after the
package name, and not contains some additional version information. If
you want to store patches for several versions of the same package, you
must use the same organization as in Buildroot itself:

  <package-name>/<package-version>/*.patch

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Kernel patches in Buildroot

[Thomas Petazzoni]

Dear David Van Arnem,

On Tue, 17 Nov 2015 11:30:13 -0700, David Van Arnem wrote:
> On 11/17/2015 10:13 AM, Joao Pinto wrote:

> > The linux kernel patching system does not recognizes the
> > packages/linux-arc-axs101-20141021-3.13 patch folder. Could you give me a help
> > on this?
> 
> I haven't done this myself, so I'm not completely sure if this is 
> correct, but there's an option to add custom kernel patches under 
> menuconfig -> Kernel -> Custom kernel patches.  I think to patch the 
> kernel you would need to set that value to the 
> snps-custom/packages/linux-arc-axs... path.

This is indeed another solution. But Joao was trying to use the
BR2_GLOBAL_PATCH_DIR mechanism, which allows to provide custom patches
for *any* package, and not only specifically for the Linux kernel.

Essentially, the "Custom kernel patches" mechanism you points to
predates the BR2_GLOBAL_PATCH_DIR mechanism. We keep it for
compatibility reasons, but generally consider BR2_GLOBAL_PATCH_DIR to
be the "better way".

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] Kernel patches in Buildroot

[David Van Arnem]

On 11/17/2015 01:09 PM, Thomas Petazzoni wrote:
> Dear David Van Arnem,
>
> On Tue, 17 Nov 2015 11:30:13 -0700, David Van Arnem wrote:
>> On 11/17/2015 10:13 AM, Joao Pinto wrote:
>
>>> The linux kernel patching system does not recognizes the
>>> packages/linux-arc-axs101-20141021-3.13 patch folder. Could you give me a help
>>> on this?
>>
>> I haven't done this myself, so I'm not completely sure if this is
>> correct, but there's an option to add custom kernel patches under
>> menuconfig -> Kernel -> Custom kernel patches.  I think to patch the
>> kernel you would need to set that value to the
>> snps-custom/packages/linux-arc-axs... path.
>
> This is indeed another solution. But Joao was trying to use the
> BR2_GLOBAL_PATCH_DIR mechanism, which allows to provide custom patches
> for *any* package, and not only specifically for the Linux kernel.
>
> Essentially, the "Custom kernel patches" mechanism you points to
> predates the BR2_GLOBAL_PATCH_DIR mechanism. We keep it for
> compatibility reasons, but generally consider BR2_GLOBAL_PATCH_DIR to
> be the "better way".

Good to know, thank you!

David
>
> Best regards,
>
> Thomas
>


-- 
Thanks,
David

[Buildroot] Kernel patches in Buildroot

[Joao Pinto]

Dear Thomas,
Thanks, worked fine!

BR
Joao Pinto

On 11/17/2015 8:08 PM, Thomas Petazzoni wrote:
> Dear Joao Pinto,
> 
> On Tue, 17 Nov 2015 17:13:31 +0000, Joao Pinto wrote:
> 
>> BR2_GLOBAL_PATCH_DIR="snps-custom/packages"
>>
>> I have a "snps-custom" folder which has a "packages" folder inside. Inside the
>> "packages" folder we have a folder for each package we need to patch, in this
>> example mplayer and the linux kernel.
>>
>> --snps-custom
>>   --packages
>>     --linux-arc-axs101-20141021-3.13
> 
> Call this folder just "linux". The folder must be named after the
> package name, and not contains some additional version information. If
> you want to store patches for several versions of the same package, you
> must use the same organization as in Buildroot itself:
> 
>   <package-name>/<package-version>/*.patch
> 
> Best regards,
> 
> Thomas
>