[meta-freescale] [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe
Otavio Salvador
otavio at ossystems.com.br
Tue Apr 28 10:44:02 PDT 2015
On Tue, Apr 28, 2015 at 2:38 PM, Otavio Salvador
<otavio at ossystems.com.br> wrote:
> On Tue, Apr 28, 2015 at 2:24 PM, Nikolay Dimitrov <picmaster at mail.bg> wrote:
>> On 04/28/2015 08:12 PM, Otavio Salvador wrote:
>>> On Tue, Apr 28, 2015 at 2:10 PM, Nikolay Dimitrov <picmaster at mail.bg>
>>> wrote:
>>>>
>>>> On 04/28/2015 07:42 PM, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> On Tue, Apr 28, 2015 at 12:39 PM, Fabio Estevam <festevam at gmail.com>
>>>>> wrote:
>>>>> ...
>>>>>>
>>>>>>
>>>>>> Applying it on top of 4.0 linux-fslc makes the SD card detection
>>>>>> problem go away.
>>>>>
>>>>>
>>>>> ...
>>>>>
>>>>> I have applied this to linux-fslc tree and applied this to master and
>>>>> fido branches. It should work out of box now.
>>>>
>>>>
>>>>
>>>> Mainline code worked out of the box in the first place. I'm now
>>>> wondering what's the best way to go forward, as we did a lot of work
>>>> just to return to the starting point.
>>>
>>>
>>> This was a regression when enabling support for BT/WIFI reset handling
>>> which Fabio did to support WaRP. The beauty here we support in a
>>> single kernel a huge set of boards and already using the mainline mode
>>> for them.
>>
>>
>> I just feel uncomfortable that we loaded Fabio with additional work,
>> because the boards share a common tree and I didn't have any choice to
>> switch the kernel recipe to a working commit, that's all.
>
> In fact Fabio and I checke
(pressed too fast)
In fact Fabio and I checked what could eventually fix the root cause
and this seems to be a better long term commitment.
I understand your view and while it seems to be very appealing to have
"full control" it also ends with a lot of work duplication. The
sharing of a single mainline Linux kernel and U-Boot repositories is
the best way to:
- avoid work duplication
- reduce maintenance burden and work in mid term
- easy custom board development
- maximize BSP robustness
Of course, the price for this is when a regression is found it affects
different boards but a fix also fixes the issue in several boards. It
seems to be the best long-term compromise.
--
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
More information about the meta-freescale
mailing list