Re: [yocto] update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version)

[Patrick Ohly]

On Wed, 2016-11-30 at 17:19 +, André Draszik wrote:
> On Wed, 2016-11-30 at 15:59 +0100, Patrick Ohly wrote:
> > I've started a Wiki page
> > https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
> > moment, but might as well be mentioned already now.
> > 
> > Perhaps you can say a few words about your usage of swupd and what you
> > liked or didn't like about it? Note that performance will become better
> > with the upcoming update.
> 
> In the wiki or here? I'll be out for the next week, but when I come back I
> will write some more.

Let's discuss here and if necessary, summarize in the wiki.

> BTW, you probably know this: 
> https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-May/002061.html

I might have seen it at some point, but I hadn't paid that much
attention then and it's a good, timely reminder. I'll link to it from
the Wiki page.

> I liked swupd for its ability to be used both for initial provisioning

You mean installing from the update repository? That's something that
Clear Linux OS can do with their installer, but nothing like that has
been tried with a Yocto-based build. That doesn't mean that it can't be
done, it's just work.

>  as
> well as for incremental updates. The latter being important when you have
> *loads* of devices, where it doesn't seem to make sense to download a full
> image for a tiny change to each device (think cellular!),

That's indeed one of the strengths of swupd. OSTree comes close in terms
of some key characteristics (file-based, persistent /etc and /var). It
would be interesting to know how efficient updating via OSTree is.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto project in raspberry pi 3

[Khem Raj]

> On Nov 30, 2016, at 4:28 AM, Rushin Thakkar  wrote:
> 
> hello there i am trying to do yocto project on raspberry pi 3.
> when i run bitbake rpi-basic-image.
> 
> 
> this task 0: bcm2835-bootfiles-20151021-r3 do_fetch (pid 4922) is taking too 
> much time. after that
> 

You should use latest master where we have switched to tarball fetch
especially

http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/commit/?id=716b6a9cd7f24a8bacd539bb40519d185e3f963a
 

> i am getting message like
> 
> 
> 
> 
> ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
> Cloning into bare repository 
> '/home/rushin/yoctopi/poky/build/downloads/git2/github.com.raspberrypi.firmware.git'...
> fatal: The remote end hung up unexpectedly
> fatal: early EOF
> fatal: index-pack failed
> 
> ERROR: Function failed: Fetcher failure for URL: 
> 'git://github.com/raspberrypi/firmware.git;protocol=git;branch=master'. 
> Unable to fetch URL from any source.
> ERROR: Logfile of failure stored in: 
> /home/rushin/yoctopi/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/bcm2835-bootfiles/20151021-r3/temp/log.do_fetch.3385
> ERROR: Task 207 
> (/home/rushin/yoctopi/poky/meta-raspberrypi/recipes-bsp/bootfiles/bcm2835-bootfiles.bb,
>  do_fetch) failed with exit code '1'
> 
> can you tell me how to download this file manually??
> 
> like in download folder there is file called 
> wpa_supplicant-2.4.tar.gz . i can download this file. but how to get these 
> files like wpa_supplicant-2.4.tar.gz.done,wpa_supplicant.sh.done??
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [patchwork][PATCH v3] patchwork.models: Include first patch's name in series name

[Jose Lamego]

Patch Series created without a cover letter are named using a
non-descriptive generic string.

This change names the series using either the first 30 characters in
patch #1 plus the remaining patches number, or the patch name for
one-patch (1/1) series.

[YOCTO #10625]

Signed-off-by: Jose Lamego 
---
 patchwork/models.py | 13 +
 1 file changed, 13 insertions(+)

diff --git a/patchwork/models.py b/patchwork/models.py
index 3f531e6..1521641 100644
--- a/patchwork/models.py
+++ b/patchwork/models.py
@@ -1042,6 +1042,19 @@ def _series_supersede_previous_patches(series):
 def _on_revision_complete(sender, revision, **kwargs):
 series = revision.series
 
+# Now we know how many patches are in the revision,
+# so we can update the name for series without a cover letter
+if series.name == SERIES_DEFAULT_NAME:
+name = series.latest_revision().ordered_patches()[0].name
+n = re.compile(r'(\[\d+\/\d+\]\s?)')
+name = n.sub('', name)
+c = len(series.latest_revision().ordered_patches())
+# For one-patch series (1/1) without cover letter
+if c == 1:
+series.name = name
+else:
+series.name = "\"%s...\" and %s more" % (name[:30], c-1)
+
 # update series.last_revision
 series.last_revision = series.latest_revision()
 series.save()
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH v4] u-boot: Simplify boot script

[Paul Barker]

On Wed, 30 Nov 2016 10:14:01 +1100
Jonathan Liu  wrote:

> Hi Paul,
> 
> On 30 November 2016 at 07:39, Paul Barker  wrote:
> 
> > On Sun, 27 Nov 2016 17:37:53 +1100
> > Jonathan Liu  wrote:
> >
> > > A patch is backported to check if the firmware loaded a device tree blob
> > > into memory and set the fdt_addr variable if it is found. The U-Boot
> > > script will then read the command line arguments generated by the
> > > firmware from the device tree and boot the kernel with the command
> > > line arguments and the loaded device tree.
> > >
> > > This allows things like MAC address, board revision and serial number
> > > to be correctly configured and options in config.txt to be used.
> > >
> > > Signed-off-by: Jonathan Liu 
> > > ---
> > > Changes in v4:
> > >  - Backport patch from upstream instead of using own patch
> >
> > I had to make a few additional changes on top of this patch to get a
> > successful compile with u-boot v2016.03. These changes can be seen here:
> >
> > https://gitlab.com/pbarker/meta-raspberrypi/commit/
> > f880569e62d431cbead1555cf6c47342fe79c969
> >
> > After those changes though, everything worked as expected on both an
> > original rpi B+ and an rpi3.
> >
> > Does your patch work cleanly on a later version of u-boot? I know
> > oe-core is likely to upgrade to v2016.11 any day now. We could either
> > apply the changes I've linked to above or hold off until v2016.11 is
> > merged to oe-core if that's what you've tested with.
> >
> 
> Yes, my patch applies cleanly to v2016.11 as well. I only tested with
> Raspberry Pi 3 as I didn't have a Raspberry Pi 2 around at the time.
> The upstream commits landed in master after v2016.11 so backports will be
> needed until at least v2017.01.
> 
> Are you able to squash your changes into this patch and submit a v5 with
> your Signed-off-by tag?
> 

Will do. Currently in progress, will send once I've given it a quick
test.

Thanks,
Paul Barker
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH v5] u-boot: Simplify boot script

[Paul Barker]

From: Jonathan Liu 

A patch is backported to check if the firmware loaded a device tree blob
into memory and set the fdt_addr variable if it is found. The U-Boot
script will then read the command line arguments generated by the
firmware from the device tree and boot the kernel with the command
line arguments and the loaded device tree.

This allows things like MAC address, board revision and serial number
to be correctly configured and options in config.txt to be used.

An additional patch is backported and further changes are made to support
this.

Signed-off-by: Jonathan Liu 
Signed-off-by: Paul Barker 
---
Changes in v5:
 - Backport an additional patch and make further changes to support u-boot
   v2016.03
Changes in v4:
 - Backport patch from upstream instead of using own patch
Changes in v3:
 - Removed incorrect check if fdt_addr_r is already set. The check
   condition was inverted and fdt_addr_r variable is always set to
   0x100 by default.
Changes in v2:
 - Instead of setting device_tree_address to 0x100 in config.txt, patch
   U-Boot to detect the device tree blob address if it was loaded.

 recipes-bsp/rpi-u-boot-scr/files/boot.cmd  |   3 +
 .../rpi-u-boot-scr/files/raspberrypi/boot.cmd  |   6 -
 .../rpi-u-boot-scr/files/raspberrypi0/boot.cmd |   6 -
 .../rpi-u-boot-scr/files/raspberrypi2/boot.cmd |   6 -
 .../rpi-u-boot-scr/files/raspberrypi3/boot.cmd |   6 -
 ...0001-arm-add-save_boot_params-for-ARM1176.patch |  56 
 ...through-of-the-firmware-provided-FDT-blob.patch | 156 +
 .../0003-Include-lowlevel_init.o-for-rpi2.patch|  25 
 recipes-bsp/u-boot/u-boot_%.bbappend   |   6 +
 9 files changed, 246 insertions(+), 24 deletions(-)
 create mode 100644 recipes-bsp/rpi-u-boot-scr/files/boot.cmd
 delete mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi/boot.cmd
 delete mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi0/boot.cmd
 delete mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi2/boot.cmd
 delete mode 100644 recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd
 create mode 100644 
recipes-bsp/u-boot/files/0001-arm-add-save_boot_params-for-ARM1176.patch
 create mode 100644 
recipes-bsp/u-boot/files/0002-rpi-passthrough-of-the-firmware-provided-FDT-blob.patch
 create mode 100644 
recipes-bsp/u-boot/files/0003-Include-lowlevel_init.o-for-rpi2.patch

diff --git a/recipes-bsp/rpi-u-boot-scr/files/boot.cmd 
b/recipes-bsp/rpi-u-boot-scr/files/boot.cmd
new file mode 100644
index 000..2e8452e
--- /dev/null
+++ b/recipes-bsp/rpi-u-boot-scr/files/boot.cmd
@@ -0,0 +1,3 @@
+fdt addr ${fdt_addr} && fdt get value bootargs /chosen bootargs
+fatload mmc 0:1 ${kernel_addr_r} uImage
+bootm ${kernel_addr_r} - ${fdt_addr}
diff --git a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi/boot.cmd 
b/recipes-bsp/rpi-u-boot-scr/files/raspberrypi/boot.cmd
deleted file mode 100644
index c86c758..000
--- a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi/boot.cmd
+++ /dev/null
@@ -1,6 +0,0 @@
-setenv fdtfile bcm2708-rpi-b.dtb
-setenv bootargs 'earlyprintk console=tty0 console=ttyAMA0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait noinitrd'
-mmc dev 0
-fatload mmc 0:1 ${kernel_addr_r} uImage
-fatload mmc 0:1 ${fdt_addr_r} ${fdtfile}
-bootm ${kernel_addr_r} - ${fdt_addr_r}
diff --git a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi0/boot.cmd 
b/recipes-bsp/rpi-u-boot-scr/files/raspberrypi0/boot.cmd
deleted file mode 100644
index c86c758..000
--- a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi0/boot.cmd
+++ /dev/null
@@ -1,6 +0,0 @@
-setenv fdtfile bcm2708-rpi-b.dtb
-setenv bootargs 'earlyprintk console=tty0 console=ttyAMA0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait noinitrd'
-mmc dev 0
-fatload mmc 0:1 ${kernel_addr_r} uImage
-fatload mmc 0:1 ${fdt_addr_r} ${fdtfile}
-bootm ${kernel_addr_r} - ${fdt_addr_r}
diff --git a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi2/boot.cmd 
b/recipes-bsp/rpi-u-boot-scr/files/raspberrypi2/boot.cmd
deleted file mode 100644
index aa4ea64..000
--- a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi2/boot.cmd
+++ /dev/null
@@ -1,6 +0,0 @@
-setenv fdtfile bcm2709-rpi-2-b.dtb
-setenv bootargs 'earlyprintk console=tty0 console=ttyAMA0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait noinitrd'
-mmc dev 0
-fatload mmc 0:1 ${kernel_addr_r} uImage
-fatload mmc 0:1 ${fdt_addr_r} ${fdtfile}
-bootm ${kernel_addr_r} - ${fdt_addr_r}
diff --git a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd 
b/recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd
deleted file mode 100644
index 2950856..000
--- a/recipes-bsp/rpi-u-boot-scr/files/raspberrypi3/boot.cmd
+++ /dev/null
@@ -1,6 +0,0 @@
-setenv fdtfile bcm2710-rpi-3-b.dtb
-setenv bootargs 'earlyprintk console=tty0 console=ttyAMA0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait noinitrd'
-mmc dev 0
-fatload mmc 0:1 ${kernel_addr_r} uImage
-fatload mmc 0:1 ${fdt_addr_r} ${fdtfile}
-bootm ${kernel_addr_r} - ${fdt_addr_r}
diff --git 
a/recipes-bsp/u-boot/files/0001-a

[yocto] any recommendations for ARM-powered, yocto-based drones?

[Robert P. J. Day]

  i want to get a drone, and i'd prefer that it was linux-powered --
specifically, i'd like an ARM-based drone with an OS created by yocto
project.

  i can see that there's an atom-powered drone here:

http://www.theregister.co.uk/2016/08/17/intel_aero_developer_board/

which runs "Yocto GNU/Linux", but i'd prefer something based on ARM.
any pointers?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Seeing "dd: failed to open '/core-image-minimal-raspberrypi3-20161129134515.rootfs.rpi-sdimg': Permission denied" Errors After Update

[Thomas Thorne]

Obviously I was having some trouble when I created this work area: 

~/work/yocto-rpi/meta-raspberrypi$ git branch -l
  krogoth
* master
  origin/krogoth
  origon/krogoth
  origonkrogoth

So I delete all those and try:

$ git checkout origin/krogoth 
warning: refname 'origin/krogoth' is ambiguous.
Switched to branch 'origin/krogoth'

It is not safe to ignore that warning.  What it means is everything went 
terribly wrong.  Time to delete and try again.  

~/work/yocto-rpi/meta-raspberrypi$ git checkout -b krogoth --track 
origin/krogoth 
Branch krogoth set up to track remote branch krogoth from origin.
Switched to a new branch 'krogoth'
thomasthorne@thorne-ul-dt:~/work/yocto-rpi/meta-raspberrypi$ git status 
On branch krogoth
Your branch is up-to-date with 'origin/krogoth'.
nothing to commit, working directory clean

That looks more hopeful. 

$ bitbake core-image-minimal
WARNING: Host distribution "Ubuntu-16.04" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Parsing recipes: 100% 
|##| Time: 
00:00:34
Parsing of 1940 .bb files complete (0 cached, 1940 parsed). 2493 targets, 347 
skipped, 0 masked, 0 errors.
NOTE: There are 1 recipes to be removed from sysroot raspberrypi3, removing...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi3"
DISTRO= "poky"
DISTRO_VERSION= "2.1.2"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard 
cortexa7"
TARGET_FPU= "hard"
meta  
meta-poky 
meta-yocto-bsp= "krogoth:ae9b341ecfcc60e970f29cfe04306411ad26c0cf"
meta-oe   
meta-multimedia   
meta-networking   
meta-python   = "krogoth:851a064b53dca3b14dd33eaaaca9573b1a36bf0e"
meta-qt5  = "HEAD:2b1871f0d139dc3caaa779a32a1931409c245a36"
meta-raspberrypi  = "krogoth:a5f9b07a820d50ae5fb62e07306cd4e72d8638a9"
meta-quectel-community = "krogoth:ae9b341ecfcc60e970f29cfe04306411ad26c0cf"
meta-rpi  = "krogoth:b10b0f1bf64ad7e8b1ab00e0a67f0c6e77ef0a97"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 1645 tasks of which 1595 didn't need to be rerun 
and all succeeded.


Success!  Thank you for your help.  Not sure why I did not spot the odd branch 
name.  

Any ideas why the meta-raspberrypi repository will tab-complete branch names 
without then correctly linking to the remote branch?  To me there is only one 
mention of krogoth besides that one I created.  

$ git branch --list --all --verbose
* krogoth a5f9b07 bcm2835: Compile examples correct LDFLAGS 
to avoid HASH errors
  master  44d41bf raspberrypi3.conf: fix typo for BCM43430
  remotes/origin/HEAD -> origin/master
  remotes/origin/ag-dev   139e7ff .gitignore: Ignore some stuff
  remotes/origin/daisy946b692 gstreamer1.0-plugins-bad: Build 
eglglessink for Raspberry Pi
  remotes/origin/danny1ad98cf README: Modify dependencies for danny 
branch
  remotes/origin/denzil   34eef2e linux-raspberrypi_3.1.9: Fix typo
  remotes/origin/dizzyefd760d linux-raspberrypi: faulty branch and 
srcrev for 3.16
  remotes/origin/dora 1c696a9 omxplayer: Install fonts directory in 
datadir
  remotes/origin/dylan770b88b sdcard_image-rpi.bbclass: Fix error in 
conditional test
  remotes/origin/fido 428602b rpi-default-providers: Let users 
overwrite the default providers
  remotes/origin/jethro   f2cff83 README: Fix documentation to disable 
overscan
  remotes/origin/khem_wayland cc4dc7b userland: Fix build with clang compiler
  remotes/origin/krogoth  a5f9b07 bcm2835: Compile examples correct LDFLAGS 
to avoid HASH errors
  remotes/origin/master   44d41bf raspberrypi3.conf: fix typo for BCM43430

The main things I that the builds are all working again.  I will try and pay 
more attention when doing the checkout step in the future.  
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [patchwork][PATCH v2] patchwork/models: Include first patch's name in series name

[Jose Lamego]

Patch Series created without a cover letter are named using a
non-descriptive generic string.

This change names the series using either the first 30 characters in
patch #1 plus the remaining patches number, or the patch name for
one-patch (1/1) series.

[Yocto #10625]

Signed-off-by: Jose Lamego 
---
 patchwork/models.py | 16 
 1 file changed, 16 insertions(+)

diff --git a/patchwork/models.py b/patchwork/models.py
index 3f531e6..2dfd884 100644
--- a/patchwork/models.py
+++ b/patchwork/models.py
@@ -1042,6 +1042,22 @@ def _series_supersede_previous_patches(series):
 def _on_revision_complete(sender, revision, **kwargs):
 series = revision.series
 
+# Now we know how many patches are in the revision,
+# so we can update the name for series without a cover letter
+if series.name == SERIES_DEFAULT_NAME:
+try:
+name = series.latest_revision().ordered_patches()[0].name
+n = re.compile(r'(\[\d+\/\d+\]\s?)')
+name = n.sub('', name)
+c = len(series.latest_revision().ordered_patches())
+# For one-patch series (1/1) without cover letter
+if c == 1:
+series.name = name
+else:
+series.name = "\"%s...\" and %s more" % (name[:30], c-1)
+except:
+pass
+
 # update series.last_revision
 series.last_revision = series.latest_revision()
 series.save()
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version)

[André Draszik]

On Wed, 2016-11-30 at 15:59 +0100, Patrick Ohly wrote:
> On Wed, 2016-11-30 at 14:31 +, André Draszik wrote:
> > On Wed, 2016-11-30 at 12:04 +0100, Patrick Ohly wrote:
> > > On Mon, 2016-11-21 at 12:03 +, André Draszik wrote:
> > > > This allows us to completely remove the build time
> > > > depenency on libcheck when not needed, reducing
> > > > overall build time, and in addition tests can be
> > > > converted into a PACKAGECONFIG to enable them if
> > > > needed.
> > > 
> > > +1
> > > 
> > > Sorry for the delay, I had to check with Joshua first who's going to
> > > merge your patches. I'm currently working on a major update of
> > > meta-swupd (see https://github.com/ostroproject/ostro-os/pull/198) and
> > > if there's enough interest for using it as part of Yocto, might
> > > continue
> > > maintaining it.
> > 
> > Thanks Patrick. Are you saying you would otherwise abandon meta-swupd
> > completely, or have it be a part of ostro-os only?
> 
> That's undecided. We are currently trying to figure out which update
> mechanism is a good fit for Yocto. Depending on the outcome of that and
> available resources, we may or may not have the time to support
> something.
> 
> I've started a Wiki page
> https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
> moment, but might as well be mentioned already now.
> 
> Perhaps you can say a few words about your usage of swupd and what you
> liked or didn't like about it? Note that performance will become better
> with the upcoming update.

In the wiki or here? I'll be out for the next week, but when I come back I
will write some more.

BTW, you probably know this: 
https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-May/002061.html

I liked swupd for its ability to be used both for initial provisioning as
well as for incremental updates. The latter being important when you have
*loads* of devices, where it doesn't seem to make sense to download a full
image for a tiny change to each device (think cellular!), the former
streamlining the update mechanism, so that not two different independent
things have to be maintained.


Cheers,
Andre'

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-swupd][PATCH] swupd-client: do out-of-tree builds

[André Draszik]

On Wed, 2016-11-30 at 13:55 +0100, Patrick Ohly wrote:
> change would just lead to conflicts with my development branch. Is it
> okay to wait for this version update?

Sure, no worries.

A.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Recipe To Add 3 Script Files To /etc/ppp/peers/

[Thomas Thorne]

Thank you for your assistance.  The final recipe I used looks like this:

#
# Copy the ppp script files for  chips to the target filesystem
# These files are based on the details provided in
#

SUMMARY = "PPP Scripts for Basic Chip Operation"
SECTION = "net"
LICENSE = "MIT"
LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
DESCRIPTION = "A set of Linux PPP scripts that provide connect, disconnect and 
other basic Point-to-Point Protocol functionality for Quectel wireless modems.  
"

RDEPENDS_${PN} = "ppp"

SRC_URI += "file://-ppp"
SRC_URI += "file://-chat-connect"
SRC_URI += "file://-chat-disconnect"

S = "${WORKDIR}"

inherit allarch

# Install script on target's root filesystem
do_install () {
# Install init script and default settings
# ${sysconfdir}
install -d ${D}${sysconfdir}/
install -d ${D}${sysconfdir}/ppp
install -d ${D}${sysconfdir}/ppp/peers
install -m 0755 ${S}/-ppp ${D}${sysconfdir}/ppp/peers/
install -m 0755 ${S}/-chat-connect ${D}${sysconfdir}/ppp/peers/
install -m 0755 ${S}/-chat-disconnect ${D}${sysconfdir}/ppp/peers/
}

# Mark the files which are part of this package
FILES_${PN} += "{sysconfdir}/ppp/"
FILES_${PN} += "{sysconfdir}/ppp/peers/"
FILES_${PN} += "{sysconfdir}/ppp/peers/-ppp"
FILES_${PN} += "{sysconfdir}/ppp/peers/-chat-connect"
FILES_${PN} += "{sysconfdir}/ppp/peers/-chat-disconnect"


The above places the three script files into /etc/ppp/peers on the root 
filesystem a I hoped.  I chose to generate a -ppp_0.1.bb recipe 
rather than a bbappend recipe as these script files are relatively independent 
of the version of ppp used.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-mono][PATCH 0/7] Updates to meta-mono layer

[Alex J Lennon]

On 06/11/2016 04:22, Barry Grussling wrote:
> I have a need to run Mono 4.6.1 on an ARM system.  The last commit to
> the yocto meta-mono tree is over six months old so I figured I would take
> a crack at it myself.  Hopefully these patches help somebody else.

Merged and tested on qemux86. Many thanks Barry
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] CommonAPI *.so bindings

[Clemens Lang]

Hi Pawel,

Pawel Suchy  wrote:

> That is causing a problem with binding CommonAPI dynamic libraries via  
> commonapi.ini.
> The commonapi.ini file contains sections where dependencies to proxy  
> objects could be defined:
> [proxy]  
> local:commonapi.examples.Test:commonapi.examples.Test=libTest-DBus.so
>
> But it cannot take link to versioned library because of that code:
> http://docs.projects.genivi.org/ipc.common-api-runtime/3.1.5/Runtime_8cpp_source.html#l00283
>
>  Runtime::loadLibrary(const std::string &_library) {
> 321  std::string itsLibrary(_library);
> 322
> 323  // TODO: decide whether this really is a good idea...
> 324  #ifdef WIN32
> 325  if (itsLibrary.rfind(".dll") != itsLibrary.length() - 4) {
> 326  itsLibrary += ".dll";
> 327  }
> 328  #else
> 329  if (itsLibrary.rfind(".so") != itsLibrary.length() - 3) {
> 330  itsLibrary += ".so";
> 331  }
> 332  #endif
>
> Questions:
> 1. How to solve best this?

Our solution to that is to not rely on runtime loading of CommonAPI  
libraries and just link the libraries that you need into the binary  
directly, in which case this code will not be run at all. If your project  
does not need the ability to switch between different communication  
backends of CommonAPI, that should also work for you.

Note that you may need -Wl,--push-state,--no-as-needed,-library,--pop-state  
depending on what your libraries look like.


HTH,
Clemens
-- 
BMW Car IT GmbH
Clemens Lang
Spezialist Entwicklung
Lise-Meitner-Straße 14
89081 Ulm

Tel: +49-731-37804182
Mail: clemens.l...@bmw-carit.de
Web: http://www.bmw-carit.de

BMW Car IT GmbH
Geschäftsführer: Michael Würtenberger und Alexis Trolin
Sitz und Registergericht: München HRB 134810

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] CommonAPI *.so bindings

[Burton, Ross]

On 30 November 2016 at 15:32, Suchy, Pawel  wrote:

> Questions:
> 1. How to solve best this?
>
> 2. Is it a good Yocto practice to not allow to have symbolic links in
> none-dev images?
>
> 3. Is there a way to have symbolic links to libs in */usr/lib *directory
> in none-dev images?
>

If the libraries that this piece of code is dlopen()ing are specific to
this framework and generally unversioned then you can just fix the
packaging so that they don't put the .so into the -dev package.

If it's doing dlopen() of general purpose libraries then the TODO at the
top is very relevant and no, it's not a good idea. It should support
versions.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] CommonAPI *.so bindings

[Suchy, Pawel]

Hi,

Yocto in none dev image does not allow to have symbolic links to versioned 
shared libraries.
That is causing a problem with binding CommonAPI dynamic libraries via 
commonapi.ini.
The commonapi.ini file contains sections where dependencies to proxy objects 
could be defined:
[proxy] local:commonapi.examples.Test:commonapi.examples.Test=libTest-DBus.so

But it cannot take link to versioned library because of that code:
http://docs.projects.genivi.org/ipc.common-api-runtime/3.1.5/Runtime_8cpp_source.html#l00283

 
Runtime::loadLibrary(const
 std::string &_library) {
321  std::string itsLibrary(_library);
322
323  // TODO: decide whether this really is a good idea...
324  #ifdef WIN32
325  if (itsLibrary.rfind(".dll") != itsLibrary.length() - 4) {
326  itsLibrary += ".dll";
327  }
328  #else
329  if (itsLibrary.rfind(".so") != itsLibrary.length() - 3) {
330  itsLibrary += ".so";
331  }
332  #endif

Questions:
1. How to solve best this?
2. Is it a good Yocto practice to not allow to have symbolic links in none-dev 
images?
3. Is there a way to have symbolic links to libs in /usr/lib directory in 
none-dev images?

References:
https://lists.linux-foundation.org/pipermail/genivi-ipc/2015-August/000525.html
Kind Regards,
Pawel


 Note: If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify us immediately by replying to the message 
and deleting it from your computer. Thank you. 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] yocto project in raspberry pi 3

[Rushin Thakkar]

hello there i am trying to do yocto project on raspberry pi 3.
when i run bitbake rpi-basic-image.


this task 0: bcm2835-bootfiles-20151021-r3 do_fetch (pid 4922) is taking too 
much time. after that

i am getting message like




ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository 
'/home/rushin/yoctopi/poky/build/downloads/git2/github.com.raspberrypi.firmware.git'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

ERROR: Function failed: Fetcher failure for URL: 
'git://github.com/raspberrypi/firmware.git;protocol=git;branch=master'. Unable 
to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/home/rushin/yoctopi/poky/build/tmp/work/raspberrypi2-poky-linux-gnueabi/bcm2835-bootfiles/20151021-r3/temp/log.do_fetch.3385
ERROR: Task 207 
(/home/rushin/yoctopi/poky/meta-raspberrypi/recipes-bsp/bootfiles/bcm2835-bootfiles.bb,
 do_fetch) failed with exit code '1'

can you tell me how to download this file manually??

like in download folder there is file called 
wpa_supplicant-2.4.tar.gz . i can download this file. but how to get these 
files like wpa_supplicant-2.4.tar.gz.done,wpa_supplicant.sh.done??
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version)

[Patrick Ohly]

On Wed, 2016-11-30 at 14:31 +, André Draszik wrote:
> On Wed, 2016-11-30 at 12:04 +0100, Patrick Ohly wrote:
> > On Mon, 2016-11-21 at 12:03 +, André Draszik wrote:
> > > This allows us to completely remove the build time
> > > depenency on libcheck when not needed, reducing
> > > overall build time, and in addition tests can be
> > > converted into a PACKAGECONFIG to enable them if
> > > needed.
> > 
> > +1
> > 
> > Sorry for the delay, I had to check with Joshua first who's going to
> > merge your patches. I'm currently working on a major update of
> > meta-swupd (see https://github.com/ostroproject/ostro-os/pull/198) and
> > if there's enough interest for using it as part of Yocto, might continue
> > maintaining it.
> 
> Thanks Patrick. Are you saying you would otherwise abandon meta-swupd
> completely, or have it be a part of ostro-os only?

That's undecided. We are currently trying to figure out which update
mechanism is a good fit for Yocto. Depending on the outcome of that and
available resources, we may or may not have the time to support
something.

I've started a Wiki page
https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
moment, but might as well be mentioned already now.

Perhaps you can say a few words about your usage of swupd and what you
liked or didn't like about it? Note that performance will become better
with the upcoming update.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-swupd][PATCH] bsdiff: update to latest version

[André Draszik]

On Wed, 2016-11-30 at 12:04 +0100, Patrick Ohly wrote:
> On Mon, 2016-11-21 at 12:03 +, André Draszik wrote:
> > This allows us to completely remove the build time
> > depenency on libcheck when not needed, reducing
> > overall build time, and in addition tests can be
> > converted into a PACKAGECONFIG to enable them if
> > needed.
> 
> +1
> 
> Sorry for the delay, I had to check with Joshua first who's going to
> merge your patches. I'm currently working on a major update of
> meta-swupd (see https://github.com/ostroproject/ostro-os/pull/198) and
> if there's enough interest for using it as part of Yocto, might continue
> maintaining it.

Thanks Patrick. Are you saying you would otherwise abandon meta-swupd
completely, or have it be a part of ostro-os only?
swupd via meta-swupd seems to be a very good addition to yocto.

Thanks,
Andre'

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-mono][PATCH] mono-4.xx: Remove --disable-static from EXTRA_OECONF

[Alex J Lennon]

On 27/06/2016 19:41, Fabio Berton wrote:
> Any update on this?
>

Applied, thanks Fabio
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-swupd][PATCH] swupd-client: fix invalid directory in do_install_append()

[Patrick Ohly]

On Mon, 2016-11-28 at 12:18 +, André Draszik wrote:
> diff --git a/recipes-core/swupd-client/swupd-client_git.bb 
> b/recipes-core/swupd-client/swupd-client_git.bb
> index fd4716f..3aed480 100644
> --- a/recipes-core/swupd-client/swupd-client_git.bb
> +++ b/recipes-core/swupd-client/swupd-client_git.bb
> @@ -38,7 +38,7 @@ SWUPD_FORMAT ??= "3"
>  SWUPD_PINNED_PUBKEY ??= ""
>  do_install_append () {
>  # TODO: This should be a less os-specific directory and not hard-code 
> datadir
> -install -d ${D}$/usr/share/clear/bundles
> +install -d ${D}/usr/share/clear/bundles
>  
>  # Write default values to the configuration hierarchy (since 3.4.0)
>  install -d ${D}/usr/share/defaults/swupd

I'm about to remove this entire do_install_append.
create_bundle_manifest() in swupd-image.bbclass is what really creates
that directory, and onfiguring the image so that the swupd-client is
usable is part of image creation, not of compiling the client.

For example, different images may need different settings, and that
can't be done with settings compiled into swupd-client because it gets
built only once.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-swupd][PATCH] swupd-client: do out-of-tree builds

[Patrick Ohly]

On Mon, 2016-11-21 at 15:42 +, André Draszik wrote:
> From: André Draszik 
> 
> Backport a patch that fixes out-of-tree builds, and at
> the same time switch to using autotools.bbclass rather
> than autotools-brokensep.bbclass

I'll update swupd-client to the latest version soon and merging this
change would just lead to conflicts with my development branch. Is it
okay to wait for this version update?

Thanks for fixing this problem also upstream!

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-swupd][PATCH] bsdiff: update to latest version

[Patrick Ohly]

On Mon, 2016-11-21 at 12:03 +, André Draszik wrote:
> This allows us to completely remove the build time
> depenency on libcheck when not needed, reducing
> overall build time, and in addition tests can be
> converted into a PACKAGECONFIG to enable them if
> needed.

+1

Sorry for the delay, I had to check with Joshua first who's going to
merge your patches. I'm currently working on a major update of
meta-swupd (see https://github.com/ostroproject/ostro-os/pull/198) and
if there's enough interest for using it as part of Yocto, might continue
maintaining it.

I'm going to stage your patches in that branch and after one round of
testing, will also push them to meta-swupd master.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto