[yocto] smartpm: is there a checksum verification for rpm downloads?

Hi, I'm using Smart + RPM for package management on my embedded linux systems. We are currently using scripts for checksum verification of downloaded rpm packages. Does smart have an inbuilt facility to verify md5 or sha256 of rpm packages downloaded from server? Regards, Prasant --

Re: [linux-yocto] [PULL REQUEST]: mei driver fixes

On Mon, Aug 1, 2016 at 3:38 PM, Winkler, Tomas wrote: > Hello Bruce, here are 3 regression fixes for MEI driver, rebased over > standard/intel/base. > > All three are in pending review in upstream. > > > > The following changes since commit >

[yocto] Question regarding kernel modules using outoftree kernel builds (EXTERNALSRC)

All, I am unable to build kernel modules when using EXTERNALSRC. When you inherit module.bbclass, it depends on kernel shared dir (from do_shared_workdir). I do see that SRCTREECOVEREDTASKS has explicitly made sure we skip do_shared_workdir in kernel-yocto.bbclass. Is this intended? What is

Re: [yocto] Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"

On Mon, Aug 1, 2016 at 9:21 AM, Brian Hutchinson wrote: >> dosfsck 2.11, 12 Mar 2005, FAT32, LFN >> Starting check/repair pass. >> Starting verification pass. >> /dev/sdb1: 284 files, 60465/62894 clusters > > Another update. After seeing guys on the Raspberry Pi forums >

Re: [yocto] [OE-core] Snaps on Yocto/OpenEmbedded

On Mon, Aug 1, 2016 at 4:14 PM, Simon Fels wrote: > On 01.08.2016 16:06, Bruce Ashfield wrote: >> >> >> On Mon, Aug 1, 2016 at 7:32 AM, Simon Fels > > wrote: >> >> Hey everyone, >> >> I've worked on a new layer recently

[yocto] Release Candidate Build for yocto-2.1.1.rc2.rc2 now available.

A release candidate build for yocto-2.1.1.rc2 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.1.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-qt4 : 92a72a790a427af5f85ce86fea4fce86a72c7b58 meta-intel :

Re: [yocto] A question of sstate and compilers

On 2016-08-01 16:28, Burton, Ross wrote: On 1 August 2016 at 15:26, Gary Thomas > wrote: Nothing else changed, I'm sure. *Something* changed, although it may be something that shouldn't have caused a rebuild (at which point printdiff is

[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, August 2, 2016 8:00 AM US Pacific Time

Tuesday, August 2, 2016 8:00 AM US Pacific Time   Agenda:   * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake

Hi, >> On Jul 29, 2016, at 1:27 AM, Hartwig, Guido wrote: >> >> Hi, >> I have some trouble with the yocto sdk in collaboration with eclipse and >> yocto CMake project. I have install all necessary eclipse plugins and linked >> my sdk with the yocto-plugin as described in

Re: [yocto] A question of sstate and compilers

On 1 August 2016 at 15:26, Gary Thomas wrote: > Nothing else changed, I'm sure. > *Something* changed, although it may be something that shouldn't have caused a rebuild (at which point printdiff is useful to find that out). Ross --

Re: [yocto] A question of sstate and compilers

On 2016-08-01 16:04, Burton, Ross wrote: On 30 July 2016 at 09:41, Gary Thomas > wrote: I'm trying to isolate a problem that showed up in my builds in the last month. Little has changed in the sources, but the one big change was I

Re: [yocto] [OE-core] Snaps on Yocto/OpenEmbedded

On Mon, Aug 1, 2016 at 7:32 AM, Simon Fels wrote: > Hey everyone, > > I've worked on a new layer recently which brings snaps to any > Yocto/OpenEmbedded based system. > > If you have never heard about snaps yet you will find most details at > http://snapcraft.io/ but

Re: [yocto] A question of sstate and compilers

On 30 July 2016 at 09:41, Gary Thomas wrote: > I'm trying to isolate a problem that showed up in my builds > in the last month. Little has changed in the sources, but > the one big change was I moved from GCC/4.9 to GCC/5.x On > the surface, this seemed to be a

Re: [yocto] [meta][PATCH v2] python-3.4-manifest: Add some missing RDEPENDS

and when patch is ready send it to openembedded-core ml On Mon, Aug 1, 2016 at 6:49 AM, Kyle Russell wrote: > Well, that makes sense. I'm just tripping all over this one. > > On Mon, Aug 1, 2016 at 8:29 AM, Burton, Ross wrote: >> >> >> On 1 August

Re: [yocto] [OE-core] Snaps on Yocto/OpenEmbedded

Simon On Mon, Aug 1, 2016 at 5:32 AM, Simon Fels wrote: > Hey everyone, > > I've worked on a new layer recently which brings snaps to any > Yocto/OpenEmbedded based system. > > If you have never heard about snaps yet you will find most details at > http://snapcraft.io/ but

Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake

On Mon, Aug 1, 2016 at 12:04 AM, Hartwig, Guido wrote: > I have manually added the flags from CC (-march=armv7-a -marm -mfpu=neon > -mfloat-abi=hard -mcpu=cortex-a8) to the OECMAKE_C_FLAGS and then it works. I > try to find a way, where CMAKE works out of the Box with

Re: [yocto] Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"

> dosfsck 2.11, 12 Mar 2005, FAT32, LFN > Starting check/repair pass. > Starting verification pass. > /dev/sdb1: 284 files, 60465/62894 clusters Another update. After seeing guys on the Raspberry Pi forums complaining about a similar thing they hinted that dosfstools was tool old. Sure enough,

Re: [yocto] Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"

On 2016-08-01 15:06, Brian Hutchinson wrote: On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson wrote: If the USB drive is cold plugged (inserted before power on) it mounts fine, it is only a hotplug that results in the message "Volume was not properly unmounted. Some data

Re: [yocto] Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"

On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson wrote: > If the USB drive is cold plugged (inserted before power on) it mounts > fine, it is only a hotplug that results in the message "Volume was not > properly unmounted. Some data may be corrupt. Please run fsck" > > The

[yocto] Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"

If the USB drive is cold plugged (inserted before power on) it mounts fine, it is only a hotplug that results in the message "Volume was not properly unmounted. Some data may be corrupt. Please run fsck" The drive is mounted under /run/media/sdb1 but a listing of the directory just shows strange

Re: [yocto] [meta][PATCH v2] python-3.4-manifest: Add some missing RDEPENDS

Well, that makes sense. I'm just tripping all over this one. On Mon, Aug 1, 2016 at 8:29 AM, Burton, Ross wrote: > > On 1 August 2016 at 13:01, Kyle Russell wrote: > >> scripts/contrib/python/generate-manifest-3.4.py | 10 +- >> > >

Re: [yocto] [meta][PATCH v2] python-3.4-manifest: Add some missing RDEPENDS

On 1 August 2016 at 13:01, Kyle Russell wrote: > scripts/contrib/python/generate-manifest-3.4.py | 10 +- > Sorry, but you need to edit the script and then run the script, so the patch contains both the script and inc file changes. Ross --

[yocto] [meta][PATCH v2] python-3.4-manifest: Add some missing RDEPENDS

Several packages were missing RDEPENDS on other modules they import. Signed-off-by: Kyle Russell --- scripts/contrib/python/generate-manifest-3.4.py | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

Re: [yocto] [meta][PATCH] python-3.4-manifest: Add some missing RDEPENDS

Thanks, sorry I missed that. I'll post an updated patch. On Sun, Jul 31, 2016 at 9:12 PM, Martin Jansa wrote: > On Fri, Jul 29, 2016 at 04:20:37PM -0400, Kyle Russell wrote: > > Signed-off-by: Kyle Russell > > manifest is generated, you need to

Re: [yocto] Trouble with yocto sdk in collaboration with eclipse and cmake

I have manually added the flags from CC (-march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8) to the OECMAKE_C_FLAGS and then it works. I try to find a way, where CMAKE works out of the Box with yocto-plugin. I think the plugin is the problem for this issue. -Ursprüngliche