From: John Stile <john@stilen.com>
To: buildroot@busybox.net
Subject: [Buildroot] configure buildroot to patch at91bootstrap
Date: Tue, 29 Jan 2013 15:33:05 -0800 [thread overview]
Message-ID: <1359502385.7974.197.camel@genx> (raw)
In-Reply-To: <20130129214230.699afd2e@skate>
On Tue, 2013-01-29 at 21:42 +0100, Thomas Petazzoni wrote:
> Dear John Stile,
>
> On Tue, 29 Jan 2013 12:29:51 -0800, John Stile wrote:
> > I have modified output/build/at91bootstrap-1.16, and now I would like
> > to save the patch set and have it applied when I rebuild
> > at91bootstrap-1.16 from scratch.
> >
> > To my buildroot .conf file, I added:
> > BR2_TARGET_AT91BOOTSTRAP_PATCH="$(TOPDIR)/board/atmel/at91sam9g20ek/at91bootstrap-patch"
> > but it is erased from .config after running make.
>
> Never edit your .config file manually. There is no way it can work
> properly, unless you know precisely what you're doing.
>
> The reason why a BR2_TARGET_AT91BOOTSTRAP_PATCH line gets removed is
> because this option simply doesn't exist.
>
> Simply go in:
>
> Bootloaders
> -> at91bootstrap
> -> custom patch dir
>
> And set your patch directory here.
There in lines the problem.
I do not have:
Bootloaders
-> at91bootstrap
-> custom patch dir
My buildroot 2011.11 has:
Bootloaders --->
[*] AT91 Bootstrap
(at91sam9g20ek) Bootstrap board
Boot Memory (NAND Flash) --->
[ ] AT91 DataFlashBoot
Is is possible to back-port the ability to patch at91bootstrap in
2011.11?
What release added it?
next prev parent reply other threads:[~2013-01-29 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 20:29 [Buildroot] configure buildroot to patch at91bootstrap John Stile
2013-01-29 20:37 ` John Stile
2013-01-29 20:42 ` Thomas Petazzoni
2013-01-29 23:33 ` John Stile [this message]
2013-01-30 7:58 ` Thomas Petazzoni
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=1359502385.7974.197.camel@genx \
--to=john@stilen.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.