[meta-freescale] [meta-fsl-arm-extra PATCH] linux-toradex (3.14.28): Restrict recipe parsing for compatible machines
otavio.salvador at ossystems.com.br
Tue Jan 19 07:20:01 PST 2016
On Tue, Jan 19, 2016 at 1:15 PM, Max Krummenacher <max.oss.09 at gmail.com> wrote:
> 2016-01-19 15:15 GMT+01:00 Otavio Salvador <otavio.salvador at ossystems.com.br>:
>> On Mon, Jan 18, 2016 at 9:52 PM, Max Krummenacher <max.oss.09 at gmail.com> wrote:
>>> Am Montag, den 18.01.2016, 15:51 -0200 schrieb Otavio Salvador:
>>>> While it is good, as design, allow for easier reuse of the recipe by
>>>> custom designs (specially SoM-based ones) it requires that we provide
>>>> common 'defconfig' files.
>>> Wouldn't it then be better to provide such a common defconfig
>>> If yes I could prepare an alternative patch which adds
>>> instead of restricting compatible machine.
>>> I would probably take the current linux-fslc one to cover a greater
>>> range of drivers and options than what we use for our machines.
>> This is indeed an option and I would appreciate it. One even better
>> one, in my POV, would be if both machines could use a single
>> defconfig. Would this be possible?
> Yes this is possible, one is a subset of the other.
> I'm still not happy though about size etc. as I outlined in the
> discussion for the initial commit:
> If you have strong feelings towards the 'one size fits all' solution I
> might get persuaded (or pressed)
> to go for it.
Personally I expect anyone using Toradex SoM will make their custom
defconfig so the default one is just a reference. The size difference
is minimal specially if you use kernel modules which will not be
loaded if the peripheral is not used/enabled.
It is your call but I don't see a big gain in two different defconfig
files for such small difference.
Otavio Salvador O.S. Systems
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
More information about the meta-freescale