Re: [ptxdist] boot problem w/ barebox

[Enrico Weigelt, metux IT consult]

On 11.09.2017 09:16, Uwe Kleine-König wrote:

Try adding a #define DEBUG in linux-4.13/arch/arm/boot/compressed/head.S > and make sure enabled DEBUG_LL and selected the right UART in your> 

.config.
After deep digging in the init code, I've meanwhile fixed it (at least
with self-compiled 2015 bbx - didn't try newer versions yet). In the end
was just dt misconfiguration (that wasn't obvious in this dts wood,
which I ported from the old 4.1-phy tree): the debug uart was disabled.

This lead to some funny situations:

* DEBUG_ll worked after fixing the port number (the counting is a bit
  confusing: ttymxc1 is #2)
* console works up to the point where the uarts tty drivers are
  configured. as the uart was disabled in dt, no tty driver was
  associated (while ll driver was still active), so the clock was
  disabled on some point, leading to supposedly hangup (actually,
  just the console was gone)
* hacking out the clock disable lead further to the point where rootfs
  is mounted and init started
* init couldn't do much, as it didn't get a console. first I suspected
  rootfs would be mounted too late, but then turned out that
  /dev/console indeed was there (in the internal initramfs), but open()
  returned ENODEV (hmm, we should have verbose errno printouts - already
  got some patches for that in some other trees ...)
* the reason for ENODEV was the lack of an tty driver for the uart
  (printk() still went through ll driver) -- may we should add a proper
  warning for that ...


--mtx

___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] Status of ptxdist and distrokit raspberry pi 2 images

[Anton Botvalde]

Hello,

I am new to the world of ptxdist and firmware image building. To get my
feet wet I have tried to build an image for my raspberry pi 2 with ptxdist
and distrokit following the blog post on the pengutronix homepage (
http://pengutronix.de/en/2017-08-28-distrokit-a-playground-
bsp-for-ptxdist.html).

The image for rpi2 is successfully built but I am unable to get the image
working on my rpi2. Nothing happens after the gpu firmware has booted and
using serial to usb connector gives nothing but radio silence so I am
guessing that the kernel is not booting at all. I have tried several sd
cards and another rpi2 so I have ruled out faulty hardware. I also tried
building an image for rpi1 but it didn't work as well.

I found the following github repo (https://github.com/rohieb/Dis
troKit-rpi-ibrdtn) which seemed aimed at distrokit and rpi images so I
tried to build an image with it instead and managed to get an image that
actually boots on my rpi2.

What is the official status of the distrokit support for raspberry pi?

Thanks
Anton Botvalde
___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] [PATCH v2] linuxptp: Update package and configs

[Michael Grzeschik]

Usualy we can not ensure only to use transparent clock switches.
Therefor we setup the fix option -P to the commandline to enable
the P2P mechanism in ptp4l.

The following options are highly depending on the usecase
so we remove them for the defaults.

path_trace_enabled
follow_up_info
tx_timestamp_timeout

With all other options were simple defaults the whole
config can be removed.

We also add some service files to start the ptp4l service on
dev eth0. In case the ptp4l daemon is configured
we add the option to install the phc2sys daemon to adjust the
system time by ptp.

Signed-off-by: Michael Grzeschik 
---
v1 -> v2: - removed install stage for gPTP.conf from rules file
  - limited to run ptp4l only on eth0 for the default setup case

 projectroot/etc/gPTP.conf  | 28 --
 projectroot/usr/lib/systemd/system/phc2sys.service | 10 
 projectroot/usr/lib/systemd/system/ptp4l@.service  | 12 ++
 rules/linuxptp.in  | 12 ++
 rules/linuxptp.make| 20 +---
 5 files changed, 51 insertions(+), 31 deletions(-)
 delete mode 100644 projectroot/etc/gPTP.conf
 create mode 100644 projectroot/usr/lib/systemd/system/phc2sys.service
 create mode 100644 projectroot/usr/lib/systemd/system/ptp4l@.service

diff --git a/projectroot/etc/gPTP.conf b/projectroot/etc/gPTP.conf
deleted file mode 100644
index 5bbbaf288..0
--- a/projectroot/etc/gPTP.conf
+++ /dev/null
@@ -1,28 +0,0 @@
-[global]
-#
-# Run time options
-#
-assume_two_step 1
-logging_level   6
-path_trace_enabled  1
-follow_up_info  1
-tx_timestamp_timeout40
-use_syslog  1
-verbose 0
-summary_interval0
-#
-# Transport options
-#
-transportSpecific   0x1
-ptp_dst_mac 01:80:C2:00:00:0E
-p2p_dst_mac 01:80:C2:00:00:0E
-uds_address /var/run/ptp4l
-#
-# Default interface options
-#
-network_transport   L2
-delay_mechanism P2P
-time_stamping   hardware
-
-[eth0]
-
diff --git a/projectroot/usr/lib/systemd/system/phc2sys.service 
b/projectroot/usr/lib/systemd/system/phc2sys.service
new file mode 100644
index 0..eb8e57037
--- /dev/null
+++ b/projectroot/usr/lib/systemd/system/phc2sys.service
@@ -0,0 +1,10 @@
+[Unit]
+Description=Precision Time Protocol system clock synchronization
+Wants=ptp4l@.service
+
+[Service]
+ExecStart=/usr/sbin/phc2sys -a -r -r
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
diff --git a/projectroot/usr/lib/systemd/system/ptp4l@.service 
b/projectroot/usr/lib/systemd/system/ptp4l@.service
new file mode 100644
index 0..7cd00dc45
--- /dev/null
+++ b/projectroot/usr/lib/systemd/system/ptp4l@.service
@@ -0,0 +1,12 @@
+[Unit]
+Description=Precision Time Protocol (PTP) service
+BindsTo = sys-subsystem-net-devices-%i.device
+After = sys-subsystem-net-devices-%i.device
+
+[Service]
+Type=simple
+ExecStart=/usr/sbin/ptp4l -P -i %i
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
diff --git a/rules/linuxptp.in b/rules/linuxptp.in
index 641d844c7..5418d2ad0 100644
--- a/rules/linuxptp.in
+++ b/rules/linuxptp.in
@@ -7,3 +7,15 @@ config LINUXPTP
  The Linux PTP project implements the Precision Time protocol (PTP),
  standardized as IEEE1588.
 
+if LINUXPTP
+
+config LINUXPTP_SYSTEMD_SERVICE
+   bool "install ptp4l and phc2sys systemd service files"
+   default y
+
+config LINUXPTP_PHC2SYS_SYSTEMD_SERVICE
+   bool "Enable phc2sys systemd service file"
+   default y
+   depends on LINUXPTP_SYSTEMD_SERVICE
+
+endif
diff --git a/rules/linuxptp.make b/rules/linuxptp.make
index 59cbb5123..6cfc0823d 100644
--- a/rules/linuxptp.make
+++ b/rules/linuxptp.make
@@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LINUXPTP) += linuxptp
 #
 # Paths and names
 #
-LINUXPTP_VERSION   := 1.6
-LINUXPTP_MD5   := 6aa15d83f5a35f1fd076ba9adc4e7285
+LINUXPTP_VERSION   := 1.8
+LINUXPTP_MD5   := 5688cdfe57932273e1dbf35b3b97b9a0
 LINUXPTP   := linuxptp-$(LINUXPTP_VERSION)
 LINUXPTP_SUFFIX:= tgz
 LINUXPTP_URL   := $(call ptx/mirror, SF, 
linuxptp/$(LINUXPTP).$(LINUXPTP_SUFFIX))
@@ -64,7 +64,21 @@ $(STATEDIR)/linuxptp.targetinstall:
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/phc2sys)
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/pmc)
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/hwstamp_ctl)
-   @$(call install_alternative, linuxptp, 0, 0, 0644, /etc/gPTP.conf)
+   @$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/phc_ctl)
+   @$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/timemaster)
+
+ifdef PTXCONF_LINUXPTP_SYSTEMD_SERVICE
+   @$(call install_alternative, linuxptp, 0, 0, 0644, 
/usr/lib/systemd/system/ptp4l@.service)
+   @$(call install_alternative, linuxptp, 0, 0, 0644, 

Re: [ptxdist] [PATCH 2/7] qpdf: new package: PDF inspection library and tools

[Juergen Borleis]

Hi Roland,

On Thursday 24 August 2017 00:39:06 Roland Hieber wrote:
> [...]
> +#
> +# Paths and names
> +#
> +QPDF_VERSION := 6.0.0
> +QPDF_MD5 := a0601b0bc56d3f412fd3afecfce2721c
> +QPDF := qpdf-$(QPDF_VERSION)
> +QPDF_SUFFIX  := tar.gz
> +QPDF_URL := $(call ptx/mirror, SF,
> /qpdf/qpdf/$(QPDF_VERSION)/$(QPDF).$(QPDF_SUFFIX)) +QPDF_SOURCE   :=
> $(SRCDIR)/$(QPDF).$(QPDF_SUFFIX)
> +QPDF_DIR := $(BUILDDIR)/$(QPDF)
> +QPDF_LICENSE := Artistic-2.0

Downloading the qpdf archive leads to a different content and thus the MD5 
sum differs. The a0601b0bc56d3f412fd3afecfce2721c package contains an 
unreleased version, which needs to create the 'configure' script first.

Where did you download your archive?

jb

-- 
Pengutronix e.K.                             | Juergen Borleis             |
Industrial Linux Solutions                   | http://www.pengutronix.de/  |

___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] [PATCH] linuxptp: Update package and configs

[Michael Grzeschik]

Usualy we can not ensure only to use transparent clock switches.
Therefor we setup the fix option -P to the commandline to enable
the P2P mechanism in ptp4l.

The following options are highly depending on the usecase
so we remove them for the defaults.

path_trace_enabled
follow_up_info
tx_timestamp_timeout

With all other options were simple defaults the whole
config can be removed.

We also add some service files to start the ptp4l service on
specific devices. In case the ptp4l daemon is configured
we add the option to install the phc2sys daemon to adjust the
system time by ptp.

Signed-off-by: Michael Grzeschik 
---
 projectroot/etc/gPTP.conf  | 28 --
 projectroot/usr/lib/systemd/system/phc2sys.service | 10 
 projectroot/usr/lib/systemd/system/ptp4l@.service  | 12 ++
 rules/linuxptp.in  | 17 +
 rules/linuxptp.make| 20 ++--
 5 files changed, 57 insertions(+), 30 deletions(-)
 delete mode 100644 projectroot/etc/gPTP.conf
 create mode 100644 projectroot/usr/lib/systemd/system/phc2sys.service
 create mode 100644 projectroot/usr/lib/systemd/system/ptp4l@.service

diff --git a/projectroot/etc/gPTP.conf b/projectroot/etc/gPTP.conf
deleted file mode 100644
index 5bbbaf288..0
--- a/projectroot/etc/gPTP.conf
+++ /dev/null
@@ -1,28 +0,0 @@
-[global]
-#
-# Run time options
-#
-assume_two_step 1
-logging_level   6
-path_trace_enabled  1
-follow_up_info  1
-tx_timestamp_timeout40
-use_syslog  1
-verbose 0
-summary_interval0
-#
-# Transport options
-#
-transportSpecific   0x1
-ptp_dst_mac 01:80:C2:00:00:0E
-p2p_dst_mac 01:80:C2:00:00:0E
-uds_address /var/run/ptp4l
-#
-# Default interface options
-#
-network_transport   L2
-delay_mechanism P2P
-time_stamping   hardware
-
-[eth0]
-
diff --git a/projectroot/usr/lib/systemd/system/phc2sys.service 
b/projectroot/usr/lib/systemd/system/phc2sys.service
new file mode 100644
index 0..eb8e57037
--- /dev/null
+++ b/projectroot/usr/lib/systemd/system/phc2sys.service
@@ -0,0 +1,10 @@
+[Unit]
+Description=Precision Time Protocol system clock synchronization
+Wants=ptp4l@.service
+
+[Service]
+ExecStart=/usr/sbin/phc2sys -a -r -r
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
diff --git a/projectroot/usr/lib/systemd/system/ptp4l@.service 
b/projectroot/usr/lib/systemd/system/ptp4l@.service
new file mode 100644
index 0..7cd00dc45
--- /dev/null
+++ b/projectroot/usr/lib/systemd/system/ptp4l@.service
@@ -0,0 +1,12 @@
+[Unit]
+Description=Precision Time Protocol (PTP) service
+BindsTo = sys-subsystem-net-devices-%i.device
+After = sys-subsystem-net-devices-%i.device
+
+[Service]
+Type=simple
+ExecStart=/usr/sbin/ptp4l -P -i %i
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
diff --git a/rules/linuxptp.in b/rules/linuxptp.in
index 641d844c7..6d1177667 100644
--- a/rules/linuxptp.in
+++ b/rules/linuxptp.in
@@ -7,3 +7,20 @@ config LINUXPTP
  The Linux PTP project implements the Precision Time protocol (PTP),
  standardized as IEEE1588.
 
+if LINUXPTP
+
+config LINUXPTP_SYSTEMD_SERVICE
+   bool "install ptp4l and phc2sys systemd service files"
+   default y
+
+config LINUXPTP_SYSTEMD_SERVICE_PTP4L_INTF
+   string "Enable ptp4l systemd service file for this interface"
+   default "eth0"
+   depends on LINUXPTP_SYSTEMD_SERVICE
+
+config LINUXPTP_PHC2SYS_SYSTEMD_SERVICE
+   bool "Enable phc2sys systemd service file"
+   default y
+   depends on LINUXPTP_SYSTEMD_SERVICE
+
+endif
diff --git a/rules/linuxptp.make b/rules/linuxptp.make
index 59cbb5123..e7ef5507d 100644
--- a/rules/linuxptp.make
+++ b/rules/linuxptp.make
@@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LINUXPTP) += linuxptp
 #
 # Paths and names
 #
-LINUXPTP_VERSION   := 1.6
-LINUXPTP_MD5   := 6aa15d83f5a35f1fd076ba9adc4e7285
+LINUXPTP_VERSION   := 1.8
+LINUXPTP_MD5   := 5688cdfe57932273e1dbf35b3b97b9a0
 LINUXPTP   := linuxptp-$(LINUXPTP_VERSION)
 LINUXPTP_SUFFIX:= tgz
 LINUXPTP_URL   := $(call ptx/mirror, SF, 
linuxptp/$(LINUXPTP).$(LINUXPTP_SUFFIX))
@@ -64,8 +64,24 @@ $(STATEDIR)/linuxptp.targetinstall:
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/phc2sys)
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/pmc)
@$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/hwstamp_ctl)
+   @$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/phc_ctl)
+   @$(call install_copy, linuxptp, 0, 0, 0755, -, /usr/sbin/timemaster)
+
@$(call install_alternative, linuxptp, 0, 0, 0644, /etc/gPTP.conf)
 
+ifdef PTXCONF_LINUXPTP_SYSTEMD_SERVICE
+   @$(call install_alternative, linuxptp, 0, 0, 0644, 
/usr/lib/systemd/system/ptp4l@.service)
+   

Re: [ptxdist] Yocto

[Guillermo Rodriguez Garcia]

Hello,

My team is using ptxdist for several projects on several different boards
and while
there are of course things that can be improved, we are very happy with it.

I have not used Yocto but have looked into it from time to time; my feeling
is that
it raises the level of abstraction too much ("too much" for my personal
preferences,
that is), thus making it difficult to see what is happening under the hood.
I share
your feeling that Yocto is becoming "the Ubuntu of the embedded world".

The main good thing about Yocto is that it is becoming hugely popular and
has a
very strong and active community. It would be great if the same would
happen with
ptxdist :-)

Guillermo

2017-09-09 15:03 GMT+02:00 Erwin Rol :

> Hey all,
>
> yes I know the topic is blasphemy ;-)  but I was wondering if there are
> ppl that made usecase comparisons between ptxdist and Yocto? My personal
> experience with small systems (no GUI/X/wayland) is that ptxdist is
> really easy to get going. With large systems that need QT 5.9,
> webkitgtk/chromium, different OpenGL versions etc. is that ptxdist is
> not always that easy. But I am not experienced enough with Yocto to say
> if that will be easier/better.
>
> So hence the question, anybody out there that tried both and picked
> ptxdist (or yocto) for a reason ?
>
> - Erwin
>
>
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de




-- 
Guillermo Rodriguez Garcia
guille.rodrig...@gmail.com
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [PATCH] barebox: fix CONFIG_DEFAULT_ENVIRONMENT_PATH on oldconfig/nconfig/menuconfig

[Bastian Stender]

On 07/28/2017 12:31 PM, Bastian Stender wrote:

ptxdist adds ".ptxdist-defaultenv" if PTXCONF_BAREBOX_EXTRA_ENV is
enabled. If barebox oldconfig/nconfig/menuconfig do not modify the
configuration the barebox config from the BSP is copied without
executing the prepare stage responsible for amending
".ptxdist-defaultenv".

Steps to reproduce:

   ptxdist targetinstall barebox
   ptxdist menuconfig barebox (without modification)
   ptxdist drop barebox.compile
   ptxdist targetinstall barebox

Now CONFIG_DEFAULT_ENVIRONMENT_PATH is missing ".ptxdist-defaultenv"
leading to an unexpected environment.

Fix this by amending ".ptxdist-defaultenv" after
oldconfig/nconfig/menuconfig.

Signed-off-by: Bastian Stender 
---
  rules/barebox.make | 7 +++
  1 file changed, 7 insertions(+)

diff --git a/rules/barebox.make b/rules/barebox.make
index bdfefe8c6..d391ec9eb 100644
--- a/rules/barebox.make
+++ b/rules/barebox.make
@@ -208,4 +208,11 @@ barebox_oldconfig barebox_menuconfig barebox_nconfig: 
$(STATEDIR)/barebox.extrac
cp $(BAREBOX_DIR)/.config $(BAREBOX_CONFIG); \
fi
  
+ifdef PTXCONF_BAREBOX_EXTRA_ENV

+   @if test -e $(BAREBOX_CONFIG); then \
+   @sed -i -e "s,^\(CONFIG_DEFAULT_ENVIRONMENT_PATH=.*\)\"$$,\1 
.ptxdist-defaultenv\"," \
+   $(BAREBOX_DIR)/.config
+   fi
+endif
+
  # vim: syntax=make



Any thoughts on this patch?

Bastian

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] system bash replacement

[Erwin Rol]

On Mon, 2017-09-11 at 10:28 +0200, Michael Olbrich wrote:
> Hi,
> 
> On Sat, Sep 09, 2017 at 10:59:34AM +0200, Erwin Rol wrote:
> > I have several (older) CentOS 6.X (and even 5.X :-/ ) systems that have
> > bash 4.1.2 which is to old for newer ptxdist releases.
> > 
> > Ptxdist checks for several tools and places links in its $PTXDIR/bin/
> > dir. Tools include cp, ls, awk, and bash. The ptxdist $PTXDIR/bin/ dir
> > is placed in PATH so those links in $PTXDIR/bin/ are found first.
> > 
> > But! all ptxdist scripts have "#!/bin/bash" in them, so that bash link
> > in $PTXDIR/bin/ is never used. 
> > 
> > I have some success by replacing "#!/bin/bash" with "#!/usr/bin/env
> > bash" but before I go ahead with that I would like to hear if someone
> > already tried that and failed (or succeeded).
> > 
> > BTW the same for the python link, scripts with #!/bin/python  will not
> > use it. 
> 
> I've never tried this, but I had some ideas:
> 
> 1. We already set SHELL=$(PTXDIST_TOPDIR)/bin/bash in
>rules/other/Toplevel.make so that handles some of it.
> 2. PTXdist itself is a problem. I had some ideas about re-executing ptxdist
>if the shell is different from $(PTXDIST_TOPDIR)/bin/bash.

I already have some "wrapper" around ptxdist so I have a bash there and
that is first in the path so "#!/usr/bin/env bash" works for me. But
that surely isn't a general solution for ptxdist.  

BTW I found out the awk should be version checked, cause the CentOS 6
awk silently fails, causing the dependencies to be not generated and so
building just starts with some random package. 

In the end things still didn't want to work right. So I ended up
creating a chroot where I bind mount everything from the host under
host_root. Than create a bin dir  and symlink everything from
host_root/bin/. Than replace the bash link with the new bash (and the
same with the awk). The other dirs like lib, etc, opt I just ln to the
dir in host_root. After that I can chroot in it and everything looks
like my host but with a new shell and awk. Also had to get a new host
GCC (4.4.8 is to old for the toolchain building). But in the end I was
able to build the lastest ptxdist toolchain on Centos 6 without changing
the host OS. 

It is like a mini "container", if I would selectively setup usr/lib/ and
usr/include it could also be used to prevent pulling in host stuff. 

- Erwin


___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] system bash replacement

[Michael Olbrich]

Hi,

On Sat, Sep 09, 2017 at 10:59:34AM +0200, Erwin Rol wrote:
> I have several (older) CentOS 6.X (and even 5.X :-/ ) systems that have
> bash 4.1.2 which is to old for newer ptxdist releases.
> 
> Ptxdist checks for several tools and places links in its $PTXDIR/bin/
> dir. Tools include cp, ls, awk, and bash. The ptxdist $PTXDIR/bin/ dir
> is placed in PATH so those links in $PTXDIR/bin/ are found first.
> 
> But! all ptxdist scripts have "#!/bin/bash" in them, so that bash link
> in $PTXDIR/bin/ is never used. 
> 
> I have some success by replacing "#!/bin/bash" with "#!/usr/bin/env
> bash" but before I go ahead with that I would like to hear if someone
> already tried that and failed (or succeeded).
> 
> BTW the same for the python link, scripts with #!/bin/python  will not
> use it. 

I've never tried this, but I had some ideas:

1. We already set SHELL=$(PTXDIST_TOPDIR)/bin/bash in
   rules/other/Toplevel.make so that handles some of it.
2. PTXdist itself is a problem. I had some ideas about re-executing ptxdist
   if the shell is different from $(PTXDIST_TOPDIR)/bin/bash.

That should help for PTXdist. Most files are not directly executed so the
shebang is just cosmetics.

Michael

-- 
Pengutronix e.K.   | |
Industrial Linux Solutions | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [PATCH v2] networkmanager: version bump: 1.8.0 -> 1.8.2

[Ladislav Michl]

On Mon, Jul 10, 2017 at 04:42:06PM +0200, Ladislav Michl wrote:
> New stable release with most notable fixes:
>  * Fix bug blocking startup wrongly waiting for carrier.
>  * Fix crash activating bluetooth or WWAN connection.

Gentle ping... I was expecting this to enter 2017.08, but there was
no such release, and it didn't go into 2017.09 either. Please let me
know if there are any problems with this patch.

> Signed-off-by: Ladislav Michl 
> ---
>  [forgot to sign-off...]
>  rules/networkmanager.make | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/rules/networkmanager.make b/rules/networkmanager.make
> index cba6fd643..e8905d840 100644
> --- a/rules/networkmanager.make
> +++ b/rules/networkmanager.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_NETWORKMANAGER) += networkmanager
>  #
>  # Paths and names
>  #
> -NETWORKMANAGER_VERSION   := 1.8.0
> -NETWORKMANAGER_MD5   := de0e70933a17ee6a682e8440015c9b1e
> +NETWORKMANAGER_VERSION   := 1.8.2
> +NETWORKMANAGER_MD5   := 1acf7a551905ae85d9987aadbb5f7205
>  NETWORKMANAGER   := NetworkManager-$(NETWORKMANAGER_VERSION)
>  NETWORKMANAGER_SUFFIX:= tar.xz
>  NETWORKMANAGER_URL   := 
> https://ftp.gnome.org/pub/GNOME/sources/NetworkManager/1.8/$(NETWORKMANAGER).$(NETWORKMANAGER_SUFFIX)
> -- 
> 2.11.0
> 
> 
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [PATCH] pulseaudio: version bump 8.0 -> 11.0

[Juergen Borleis]

Hi Lucas,

On Friday 08 September 2017 17:15:18 Lucas Stach wrote:
> [...]
> + --with-system-user=root \
> + --with-system-group=root \
> [...9

Like Clemens already stated: forcing to "root" is a no-go.

jb

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] boot problem w/ barebox

[Uwe Kleine-König]

On Sat, Sep 09, 2017 at 11:01:34AM +0200, Enrico Weigelt, metux IT consult 
wrote:
> Hi folks,
> 
> 
> I've got a really strange booting problem on an phycore-imx6
> based board (pretty much the same as mira):
> 
> * barebox v2017.06.1-phy2 comes up properly, but cant boot
>   the kernel (v4.13) - just hangs w/o any output (not even
>   uncompression message)
> * putting the kernel manually into the factory-image (sdcard)
>   w/ old 2015 barebox boots the kernel
> * w/ DEBUG_LL + earlyprintk it doesn't even does that, just
>   hangs like w/ new barebox
> 
> 
> Here's the last output I've got: (added few more debug outputs)
> 
> > Loading ARM Linux zImage '/mnt/mmc/boot/zImage'
> > Loading devicetree from '/mnt/mmc/boot/imx6q-phytec-mira-rdk-emmc.dtb'
> > Updating DT commandline:  console=ttymxc1,115200n8 root=/dev/mmcblk0p2
> rootwait rw earlyprintk=1
> > DT commandline:  console=ttymxc1,115200n8  root=/dev/mmcblk0p2 rootwait rw
> earlyprintk=1
> > booting kernel with devicetree
> > start_linux: kernel entry point: 1200
> >dtb: 1800
> >   swap: 0
> >   arch: 0
> > shutting down barebox
> 
> My first suspicion was zero'ed DT memory node (which OTOH doesn't
> explain why earlyprintk doesn't work), but fixing that didn't help.
> 
> Could there be any vital low-level init missing in the new bbx ?
> Maybe the entry point correct ?
> 
> Any ideas where I could have a deeper look at ?

Try adding a #define DEBUG in linux-4.13/arch/arm/boot/compressed/head.S
and make sure enabled DEBUG_LL and selected the right UART in your
.config.

Best regards
Uwe

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] Yocto

[Schenk, Gavin]

Hi,

> 
> yes I know the topic is blasphemy ;-)  but I was wondering if there are
> ppl that made usecase comparisons between ptxdist and Yocto? My personal
> experience with small systems (no GUI/X/wayland) is that ptxdist is
> really easy to get going. With large systems that need QT 5.9,
> webkitgtk/chromium, different OpenGL versions etc. is that ptxdist is
> not always that easy. But I am not experienced enough with Yocto to say
> if that will be easier/better.
> 
> So hence the question, anybody out there that tried both and picked
> ptxdist (or yocto) for a reason ?
> 

My company uses PTXDIST for quite some Years and we go very good with it! 
Thanks for this great tool.

In September 2016 I visited a Yocto workshop to have a look at it and build an 
opinion: Switch to Yocto, or stay with PTXDIST in the near future?

As a result I recommended to stick to PTXDIST, and have a look at Yocto from 
time to time because of the big community and its progress.

In September 2016 ( Maybe the information is a little outdated ) I noted:

PRO Yocto:
* Releasetrain every half year a new YOCTO. PTXDIST releases more often. 
Sometimes with only some bugfixes, sometimes major changes. Maybe a factor for 
planning stuff.
* Fully implemented in Python you can see/change everything. (Same concept in 
PTXDIST).
* Strict object-oriented design in the recipes.
* Licensing is part of the concept in Yocto. (Meanwhile PTXDIST support license 
reports, too)
* Documentation is extensive. (Meanwhile PTXDIST docu is getting better, too)
* Package based logfiles
* Reduce build time with state-caches (PTXDIST supports pre build packages, 
ccache and ICECREAM to reduce build time, too)
* In YOCTO you have free choice for package management (RPM, DEB, ipkg, opkg). 
That impressed me, as I remember.
  And the trend in PTXDIST is to manage and update the whole firmware using 
RAUC, right? 
* The build process splits up in tasks, and for every task YOCTO creates 
scripts that can be called manually. Useful for searching problems I guess. 
  (PTXDIST has its get, extract, prepare, compile, install, targetinstall 
stages)


CON Yocto:
* No nativ support for NFS boot (Maybe outdated?). The lecturer tried to sell 
it as an advantage, but I did not hear him ... I was in stage of shock.
* Strange in such a modern systems to build semantic on top of filenames (e.g. 
No '_' in package name because the must only be one '_' that separates name 
from version ...
* Changes in source (that must be marked see GPL...) are done in patchstacks 
(same in PTXDIST). 
  But there is even less support for this in Yocto than PTXDIST offers (git 
ptx-patches). 
  Everything has to be done manualy. For me THE big regress.
* No Tab-completition as PTXDIST offers it. 5 Stages, ~130packages and 100.000 
commands. I think a very usefull feature in PTXDIST!
* The generic design of Yocto leaves you with a complicated, not really 
intuitive, folder structure. (Maybe a learning process)
* No graphical support, not even dialog based. In the lesson it seemed to me 
that you edit configfiles until the end of time...

Ok, so my conclusion was not 100% clear. Yocto is new, shiny, generic ... and 
not simple.

Hope my information is useful

Regards
Gavin Schenk


Eckelmann AG
Vorstand: Dipl.-Ing. Peter Frankenbach (Sprecher) Dipl.-Wi.-Ing. Philipp 
Eckelmann
Dr.-Ing. Marco Münchhof Dr.-Ing. Frank Uhlemann
Vorsitzender des Aufsichtsrats: Hubertus G. Krossa
Stv. Vorsitzender des Aufsichtsrats: Dr.-Ing. Gerd Eckelmann
Sitz der Gesellschaft: Berliner Str. 161, 65205 Wiesbaden, Amtsgericht 
Wiesbaden HRB 12636
http://www.eckelmann.de 

___
ptxdist mailing list
ptxdist@pengutronix.de