[meta-freescale] [PATCH v2 2/5] ls-debug: add recipe

Daiane Angolini daiane.list at gmail.com
Wed Aug 19 05:45:39 PDT 2015

On Wed, Aug 19, 2015 at 7:13 AM, Luo Zhenhua <zhenhua.luo at freescale.com> wrote:
>> -----Original Message-----
>> From: Otavio Salvador [mailto:otavio.salvador at ossystems.com.br]
>> Sent: Wednesday, August 19, 2015 5:56 PM
>> To: Luo Zhenhua-B19537 <zhenhua.luo at freescale.com>
>> Cc: meta-freescale at yoctoproject.org; Weng White-B18292
>> <White.Weng at freescale.com>; Schmitt Richard-B43082
>> <richard.schmitt at freescale.com>; Post Lauren-RAA013
>> <Lauren.Post at freescale.com>; Angolini Daiane-B19406
>> <Daiane.Angolini at freescale.com>
>> Subject: Re: [meta-freescale] [PATCH v2 2/5] ls-debug: add recipe
>> On Wed, Aug 19, 2015 at 6:46 AM, Luo Zhenhua <zhenhua.luo at freescale.com>
>> wrote:
>> >> From: Otavio Salvador [mailto:otavio.salvador at ossystems.com.br]
>> >> I disagree. It should be ls1021a SoCs not the TWR board only.
>> > [Luo Zhenhua-B19537] ls1021a family only has one supported
>> board(ls1021atwr) currently, it is identical to use ls1021a SOCs and ls1021atwr at
>> this time. We can change to ls1021a SOCs when multiple boards of ls1021a are
>> supported by this package.
>> That is a very serious misconception on the BSP design. We do the layer
>> development for custom board to be easier to be supported and Freescale
>> having one board does not mean others cannot reuse the components for
>> their boards development.  Every BSP component should be designed with
>> reusability in mind and this is reduces the time to market development and
>> speeds the development being critical for customers.
> [Luo Zhenhua-B19537] I agree with your point on components reusability.
>         We can't guarantee that this package can work well on 3rd party's boards of same SOC, so it is better to add the new board in the COMPATIBLE_MACHINE after verification.

Imagine that there is someone out there, and you have no idea s/he
exists, and s/he is using your BSP. S/he has complete control to what
s/he is doing, including which ls_debug's features works for her/is
board and which doesn't. S/he tested it already!

S/he is not going to sent a patch upstream to get her/is board
working, because it's a production product. And you will never know
how it's being used.

If you don't let ls_debug be SoC specific (instead of board specific),
s/he is going to need to fork meta-freescale, and you are doubling
her/is work.

And maybe, this is the reason why there is no 3rd party board for
qoriq appearing for us right now.

> Best Regards,
> Zhenhua
>> --
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

More information about the meta-freescale mailing list