From: Matthias Klein <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Differences between kernel config in ptxdist directory and the real kernel source directory
Date: Fri, 13 Jun 2014 11:11:38 +0200 [thread overview]
Message-ID: <539AC04A.2050108@optimeas.de> (raw)
Hello,
our kernelconfig stays in the bsp directory at
configs/platform-xxx/kernelconfig-version.
We have an out of bsp git tree for the kernel sources which is linked to
local_src/kernel.xxx.
Under which conditions get the config file transferd from bsp dir to
kernel dir, and from kernel dir to bsp dir?
I had a big problem where I had in the bsp a 3.12.15 config with preempt
rt enabled, but an 3.12.19 config without preempt rt in
the kernel directory, and I don't understand how this can happen ...
(The kernel version is 3.12.19)
I was thinking that ptxdist copy the config, calls "make oldconfig", and
copy the result back into the bsp.
Does it makes a difference for the kernel config handling that is is an
git tree instead of xz archive in the bsp?
Thanks a lot for some tips!
Best regards,
Matthias
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-06-13 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:11 Matthias Klein [this message]
2014-06-13 14:13 ` Michael Olbrich
2014-06-13 14:38 ` Matthias Klein
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=539AC04A.2050108@optimeas.de \
--to=matthias.klein@optimeas.de \
--cc=ptxdist@pengutronix.de \
/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