Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Van Arnem <dvanarnem@cmlab.biz>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel patches in Buildroot
Date: Tue, 17 Nov 2015 11:30:13 -0700	[thread overview]
Message-ID: <564B7235.20209@cmlab.biz> (raw)
In-Reply-To: <564B603B.5010907@synopsys.com>

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

  reply	other threads:[~2015-11-17 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 11:35 [Buildroot] Kernel patches in Buildroot Joao Pinto
2015-11-11 12:04 ` Arnout Vandecappelle
2015-11-11 13:13   ` Yegor Yefremov
2015-11-17 11:13   ` Joao Pinto
2015-11-17 17:13     ` Joao Pinto
2015-11-17 18:30       ` David Van Arnem [this message]
2015-11-17 20:09         ` Thomas Petazzoni
2015-11-17 20:18           ` David Van Arnem
2015-11-17 20:08       ` Thomas Petazzoni
2015-11-18  9:30         ` Joao Pinto

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=564B7235.20209@cmlab.biz \
    --to=dvanarnem@cmlab.biz \
    --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