On Wed, Apr 1, 2020 at 6:24 AM Richard Purdie
wrote:
...
> Sadly it breaks oe-selftest's sstatetests:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/825
>
> (reproduce with oe-selftest -r sstatetests.SStateTests)
>
> As well as world build file conflicts in deploy:
>
> https
Hi,
it's very handy to have the environment file in the DEPLOY folder to for
example be able to integrate it to a WIC image.
BR
On Tue, Mar 31, 2020 at 5:32 PM Stefano Babic wrote:
> Hi Otavio,
>
> On 31.03.20 17:16, Otavio Salvador wrote:
> > One significant change from previous OE-Core rele
On Tue, 2020-03-31 at 12:16 -0300, Otavio Salvador wrote:
> One significant change from previous OE-Core releases was the move
> from
> u-boot-fw-utils to libubootenv which offers a generic and not machine
> specific alternative. However, it is not fully functional as
> currently
> we don't provide
On Tue, Mar 31, 2020 at 2:03 PM Stefano Babic wrote:
> On 31.03.20 18:44, Otavio Salvador wrote:
> > Hello Stefano,
> >
> > On Tue, Mar 31, 2020 at 12:32 PM Stefano Babic wrote:
> >> On 31.03.20 17:16, Otavio Salvador wrote:
> > ...
> >>> - u-boot-initial-env on deploy
> >>> - fw_env.config on de
Hi Otavio,
On 31.03.20 18:44, Otavio Salvador wrote:
> Hello Stefano,
>
> On Tue, Mar 31, 2020 at 12:32 PM Stefano Babic wrote:
>> On 31.03.20 17:16, Otavio Salvador wrote:
> ...
>>> - u-boot-initial-env on deploy
>>> - fw_env.config on deploy
>>
>> Why do we need both of them in deploy ? For ma
Hello Stefano,
On Tue, Mar 31, 2020 at 12:32 PM Stefano Babic wrote:
> On 31.03.20 17:16, Otavio Salvador wrote:
...
> > - u-boot-initial-env on deploy
> > - fw_env.config on deploy
>
> Why do we need both of them in deploy ? For making system functional, we
> just need that both files are in /et
Hi Otavio,
On 31.03.20 17:16, Otavio Salvador wrote:
> One significant change from previous OE-Core releases was the move from
> u-boot-fw-utils to libubootenv which offers a generic and not machine
> specific alternative. However, it is not fully functional as currently
> we don't provide the def
One significant change from previous OE-Core releases was the move from
u-boot-fw-utils to libubootenv which offers a generic and not machine
specific alternative. However, it is not fully functional as currently
we don't provide the default environment nor the required configuration
file to be use
