mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Differences between kernel config in ptxdist directory and the real kernel source directory
Date: Fri, 13 Jun 2014 16:13:16 +0200	[thread overview]
Message-ID: <20140613141316.GC5199@pengutronix.de> (raw)
In-Reply-To: <539AC04A.2050108@optimeas.de>

Hi,

On Fri, Jun 13, 2014 at 11:11:38AM +0200, Matthias Klein wrote:
> 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?

During kernel.prepare the config is copied from the BSP to the kernel
source tree.
At the end of 'ptxdist menuconfig kernel' or 'ptxdist oldconfig kernel' it
is copied back, so you need to explicitly do this after changing the
kernel code.

Regards
Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-06-13 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  9:11 Matthias Klein
2014-06-13 14:13 ` Michael Olbrich [this message]
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=20140613141316.GC5199@pengutronix.de \
    --to=m.olbrich@pengutronix.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