From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Gary Thomas <gary@mlbassoc.com>
Subject: Re: [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe
Date: Tue, 28 Apr 2015 20:24:38 +0300 [thread overview]
Message-ID: <553FC256.2010006@mail.bg> (raw)
In-Reply-To: <CAP9ODKqq9rT+ZMyGm8S3wLU---0NrNhAn_PRp2JZkiPQgcTrZw@mail.gmail.com>
Hi Otavio,
On 04/28/2015 08:12 PM, Otavio Salvador wrote:
> Hello Nikolay,
>
> On Tue, Apr 28, 2015 at 2:10 PM, Nikolay Dimitrov <picmaster@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@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.
Regards,
Nikolay
next prev parent reply other threads:[~2015-04-28 17:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 4:35 [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe Nikolay Dimitrov
2015-04-27 4:35 ` [meta-fsl-arm-extra][PATCH 2/2] linux-riotboard: Fix broken boot Nikolay Dimitrov
2015-04-27 11:40 ` [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe Otavio Salvador
2015-04-27 15:27 ` Nikolay Dimitrov
2015-04-27 16:26 ` Otavio Salvador
2015-04-27 16:54 ` Daiane Angolini
2015-04-27 16:59 ` Otavio Salvador
2015-04-28 4:14 ` Nikolay Dimitrov
2015-04-28 13:46 ` Daiane Angolini
2015-04-28 13:53 ` Fabio Estevam
2015-04-28 13:57 ` Gary Thomas
2015-04-28 14:01 ` Fabio Estevam
2015-04-28 15:39 ` Fabio Estevam
2015-04-28 16:25 ` Gary Thomas
2015-04-28 16:42 ` Otavio Salvador
2015-04-28 17:10 ` Nikolay Dimitrov
2015-04-28 17:12 ` Otavio Salvador
2015-04-28 17:24 ` Nikolay Dimitrov [this message]
2015-04-28 17:38 ` Otavio Salvador
2015-04-28 17:44 ` Otavio Salvador
2015-04-29 6:18 ` Nikolay Dimitrov
2015-04-28 18:19 ` Nikolay Dimitrov
2015-04-28 18:33 ` Otavio Salvador
2015-04-28 18:45 ` Nikolay Dimitrov
2015-04-27 11:54 ` Daiane Angolini
2015-04-27 15:54 ` Nikolay Dimitrov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553FC256.2010006@mail.bg \
--to=picmaster@mail.bg \
--cc=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.