From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linux-omap@vger.kernel.org
Subject: Re: 3.8 -> 3.9-rc1 upgrade: old configs broken
Date: Mon, 4 Mar 2013 16:35:28 -0800 [thread overview]
Message-ID: <20130305003527.GK1622@atomide.com> (raw)
In-Reply-To: <20130304232252.GA14552@blackmetal.musicnaut.iki.fi>
* Aaro Koskinen <aaro.koskinen@iki.fi> [130304 15:26]:
> Hi,
>
> How should I upgrade my .config files when upgrading to 3.9-rc1?
>
> So far I have been doing it like this:
>
> cp <old config from previous kernel release> .config
> make ARCH=arm oldnoconfig
> <compile>
>
> But now I see that none of my boards boot up... Except OMAP1 (well, after
> fixing the build issues). I believe this is because ARCH_MULTIPLATFORM
> changes. I can always redo my configs with menuconfig, it's a PITA job...
>
> So I guess .config files are not supposed to be upwards compatible?
Well in this case you need to update your config files by adding
the following manually to your .config:
CONFIG_ARCH_MULTIPLATFORM=y
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_OMAP2PLUS=y
And maybe also:
CONFIG_ARCH_MULTI_V6=y
That's because after the multiplatform Kconfig changes we cannot
select omap2+ automatically as that would not be nice for the
other arm architectures.
Then if using uImage, you need to define LOADADDR in the
environment when building. Or run mkimage manually.
Regards,
Tony
next prev parent reply other threads:[~2013-03-05 0:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 23:22 3.8 -> 3.9-rc1 upgrade: old configs broken Aaro Koskinen
2013-03-05 0:35 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-06 16:26 Piotr Haber
2013-03-06 20:33 ` Tony Lindgren
2013-03-08 4:12 ` Rajendra Nayak
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=20130305003527.GK1622@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-omap@vger.kernel.org \
/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