[Buildroot] [PATCH 3/4] arch: do not distinguish revisions of ARM1136JF-S

Benoît Thébaudeau benoit.thebaudeau.dev at gmail.com
Mon Sep 15 22:37:51 UTC 2014


Dear Yann E. MORIN,

On Tue, Sep 16, 2014 at 12:02 AM, Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
> Benoît, Thomas, All,
>
> On 2014-09-15 23:44 +0200, Benoît Thébaudeau spake thusly:
>> On Mon, Sep 15, 2014 at 11:39 PM, Thomas Petazzoni
>> <thomas.petazzoni at free-electrons.com> wrote:
>> > Dear Yann E. MORIN,
>> >
>> > On Mon, 15 Sep 2014 23:33:39 +0200, Yann E. MORIN wrote:
>> >
>> >> > Note that the removal of the two options should not break existing
>> >> > full .config, since the hidden option BR2_arm1136jf_s becomes again a
>> >> > visible option to select the CPU.
>> >>
>> >> But it would break a defconfig.
>> >
>> > Right. But I believe that when we change the default value of an
>> > option, we also break a defconfig, and we don't include that as part of
>> > the Config.in.legacy handling (but also because it's obviously more
>> > complicated).
>> >
>> >> As suggested on IRC, move the BR2_arm1136jf_s_r1 to Config.legacy, and
>> >> have it select BR2_arm1136jf_s, so the user can re-use a defconfig.
>> >
>> > Hum, why just BR2_arm1136jf_s_r1 and not BR2_arm1136jf_s_r0 ?
>>
>> This issue disappears if -march and -mtune are kept and -mcpu removed
>> as I suggested.
>
> So, maybe we need something like this:
>
>     https://gist.github.com/aeruder/341565b759822b352dd9

Exactly.

Regards,
Benoît


More information about the buildroot mailing list