On 08/06/2014 11:59 PM, Masahiro Yamada wrote:
> Hi York,
>
>
> On Wed, 6 Aug 2014 11:24:27 -0700
> York Sun <york...@freescale.com> wrote:
>
>> On 07/29/2014 10:08 PM, Masahiro Yamada wrote:
>>> This commit adds:
>>> - arch/${ARCH}/Kconfig
>>> provide a menu to select target boards
>>> - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
>>> set CONFIG macros to the appropriate values for each board
>>> - configs/${TARGET_BOARD}_defconfig
>>> default setting of each board
>>>
>>> (This commit was automatically generated by a conversion script
>>> based on boards.cfg)
>>
>> Dear Masahiro,
>>
>> Do you have any plan to sort the entries in each Kconfig, eg
>> arch/arm/Kconfig?
>
>
> Do you mean, just sorting? (if so, in which order)
> or grouping boards with the same platform like this series?
> http://patchwork.ozlabs.org/patch/376860/
>
> So, my answer is yes for ARM Kconfig.
> The first phase of refactoring is on Patchwork now
> (and I have a plan to do a little bit more).
> But I have no idea about the other architecutures.
> Honestly, I am expecting it to the custodian of each architecture.
>
> BTW the entries in Kconfig are already sorted.
> The order is the same as that in boards.cfg
> which originates in tools/reformat.py.
>
> We had sorted the entries with tools/reformat.py quite often, right?
> (I thought it was really painful to resolve merge conflicts in boards.cfg,
> but it looked like everybody had gotten along with it...)
>
> Anyway, please let me know your intention clearer.
> How do you want the entries in Kconfig look like?
>
Dear Masahiro,
When I was playing with the u-boot with Kconfig, I found it was not easy to
select the board I wanted to build if using menuconfig. The reason is the board
names are not sorted. Of course I can easily get around it by using _defconfig.
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
