Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: buildrootcharles <charles.s@mercury-security.com>
To: buildroot@busybox.net
Subject: [Buildroot] Custom kernal patch not being run
Date: Thu, 28 Aug 2014 11:00:55 -0700 (PDT)	[thread overview]
Message-ID: <1409248855849-78152.post@n4.nabble.com> (raw)

I am trying to figure out how to create and have buildroot deploy a custom
kernel patch (on my system only). I currently have my buildroot configured
to  build a custom kernel from a tarball I have saved locally on my machine
(filename Linux-3.10.4-July302014.tar.gz), I have created a patch file
(named Linux-patch.patch) with the following content:

*** /home/MSC/SVN_BuildRoot/output/build/linux-custom/net/ipv4/ipconfig.c
2014-07-22 14:45:55.000000000 -0700
--- /home/MSC/SVN_BuildRoot/board/ep4502/linux-patches/ipconfig.c	2014-08-28
10:00:33.824586558 -0700
***************
*** 89,96 ****
  
  /* Define the friendly delay before and after opening net devices */
  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502VBB
! #define CONF_CARRIER_TIMEOUT	12000	/* Wait for carrier timeout */
  #else
  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
  #endif
--- 89,96 ----
  
  /* Define the friendly delay before and after opening net devices */
  #define CONF_POST_OPEN		10	/* After opening: 10 msecs */
! #ifdef CONFIG_MACH_AT91SAM9G45_EP4502MSC
! #define CONF_CARRIER_TIMEOUT	30000	/* Wait for carrier timeout */
  #else
  #define CONF_CARRIER_TIMEOUT	120000	/* Wait for carrier timeout */
  #endif

I have specified the directory where the patch resides in the
BR2_LINUX_KERNEL_PATCH="/home/patchdirectory/"
whenever I run make Linux-rebuild it never seems to find my patch, do I have
it named wrong?  can anyone help, I've been stuck on this for nearly 2 days?
thanks.



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Custom-kernal-patch-not-being-run-tp78152.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

             reply	other threads:[~2014-08-28 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 18:00 buildrootcharles [this message]
2014-08-28 18:35 ` [Buildroot] Custom kernal patch not being run Thomas De Schampheleire
2014-08-28 18:44   ` buildrootcharles
2014-08-28 19:51     ` Thomas De Schampheleire
2014-08-28 20:43       ` buildrootcharles
2014-08-29 18:07         ` Thomas De Schampheleire
2014-08-29 18:22           ` buildrootcharles
2014-08-29 19:31             ` Thomas De Schampheleire
2014-09-02 21:32               ` buildrootcharles
2014-09-03  6:42                 ` Thomas De Schampheleire

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=1409248855849-78152.post@n4.nabble.com \
    --to=charles.s@mercury-security.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox