Hello All,
This is the full report for 2.6 M2 RC1:
https://wiki.yoctoproject.org/wiki/WW32_-_2018-08-07_-_Full_Test_Cycle_2.6_M2_rc1
=== Summary
All planned tests were executed except a few SDK automated tests were skipped
in Autobuilder (testrun# 9830-9836, 9796-9797).
Hi Anuj,
As per your suggestion, I have made the changes for "install option, Still
I am getting black screen,
Thanks,
Dhanasekar
On Wed, Aug 8, 2018 at 9:01 PM, Dhanasekar Jaganathan <
jdhanasekar...@gmail.com> wrote:
> Hi Anuj. You want me to add this change in systemd-boot..? If
All
We are using rocko.on variscite var-som-mx6.
In order to increase the security of our system (during a system upgrade), we
are looking to merge uImage (kernel image) and the device tree file into 1
file. Currently these are 2 different files and are worried that a file copy
operation
This set of changes builds upon the OE-Classic support we had previously
to enable importing data from other Linux distributions (or indeed other
operating systems) and linking and comparing the packages there to recipes
in OE. The initial support is just for importing RPM spec files, using
the
On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote:
>
> Hi All,
>
> I have created yocot bootable USB live image by this command "*sudo dd
> if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
> "
>
> After power on my system, I have got three options,
>
> 1. boot
> 2. install
> 3. Reboot
Hi All,
I have created yocot bootable USB live image by this command "* sudo dd
if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
"
After power on my system, I have got three options,
1. boot
2. install
3. Reboot into firmware.
When I select "install" to install yocto on mSata, I am
Hi All,
I have created yocot bootable USB live image by this command "* sudo dd
if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"*
"
After power on my system, I have got three options,
1. boot
2. install
3. Reboot into firmware.
When I select "install" to install yocto on mSata, I am
This patch fixes the "Collection Error during parsing layer conf"
when a parent layer is accidentally added before depend layers.
When removing layers from bblayers, we should not be following
the same sequence of adding the layers, it should be done in a
reversed order. This is an assumption that
Hi,
I am building the custom yocto image regularly so that I do have so may
versions of the image. But when an bug occured in older version images,
I could not find the changes in source code because of AUTOREV. Is there
any possibility to copy the hashes during the build and store in another
