From: barhoumi mohtadi <mohtadi_barhoumi@hotmail.fr>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Loading kernel configuration from an existing platform ( where is the file ??? :D )
Date: Wed, 2 May 2012 12:58:55 +0100 [thread overview]
Message-ID: <SNT145-W54D185C9F25D76782E97BF902E0@phx.gbl> (raw)
In-Reply-To: <159404761dca398eb1e588865c442c08@idefix.lespocky.dyndns.org>
[-- Attachment #1.1: Type: text/plain, Size: 2049 bytes --]
Great ! it worked, ( but in fact i thought that he old config is saved in old.config and that we don't require to save the configuration to .config )!!
thanks again :)
Regards,
Mohtadi Barhoumi
> Date: Wed, 2 May 2012 13:52:24 +0200
> From: post@lespocky.de
> To: ptxdist@pengutronix.de
> Subject: Re: [ptxdist] Loading kernel configuration from an existing platform ( where is the file ??? :D )
>
> Hei hei,
>
> Am 2012-05-02 09:53, schrieb barhoumi mohtadi:
> > I've tried to load that file , i can see that options are checked, i
> > save my configuration, but when running kernelconfig another time,
> > it's like i've done nothing!! the confiugration has not been loaded
> > properly i guess...
>
> This sounds like a problem one has with upgrading kernels too. In our
> BSP there's this:
>
> PTXCONF_KERNEL_CONFIG="kernelconfig-${PTXCONF_KERNEL_VERSION}"
>
> So there's one config for each kernel version. When upgrading I do the
> following:
>
> * `ptxdist kernelconfig`
> * "Load an Alternate Configuration File" – Here load your old config,
> the in background called 'make menuconfig' for the kernelconfig handles
> new options.
> * Do your settings or check your old ones.
> * "Save an Alternate Configuration File" – Enter '.config' here.
>
> ptxdist handles copying .config to
> kernelconfig-${PTXCONF_KERNEL_VERSION} in both directions, at least this
> is what I guessed from the behaviour.
>
> So you do not only need to load your old config but save it to .config
> (without path before). You can now call `ptxdist kernelconfig` again and
> your config should still be there.
>
> HTH & Greets
> Alex
>
> --
> »With the first link, the chain is forged. The first speech censured,
> the first thought forbidden, the first freedom denied, chains us all
> irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
> *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
[-- Attachment #1.2: Type: text/html, Size: 2582 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-05-02 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 14:40 barhoumi mohtadi
2012-04-29 20:27 ` Dave Festing
2012-05-02 7:53 ` barhoumi mohtadi
2012-05-02 11:52 ` Alexander Dahl
2012-05-02 11:58 ` barhoumi mohtadi [this message]
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=SNT145-W54D185C9F25D76782E97BF902E0@phx.gbl \
--to=mohtadi_barhoumi@hotmail.fr \
--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