[meta-fsl-ppc][PATCH v4 0/8] all the patches for meta-fsl-ppc

[meta-fsl-ppc][PATCH v4 0/8] all the patches for meta-fsl-ppc

[b28495]

From: Ting Liu <b28495@freescale.com>

V4: squash two patches; add back FILESEXTRAPATHS setting

The changes were based on the commit:
04c0bdab21f1c85723b83bb66a8b1e1a4f33cbb2 - remove images folder

Chunrong Guo (1):
  lio-utils: add tcm_start.sh and lio_start.sh to rootfs

Ting Liu (7):
  remove lm_sensor as it is already in meta-oe
  qemu: configure properly check if -lrt is needed
  sysvinit: remove SDK specific bits
  procps: remove customized sysctl.conf which is SDK specific
  udev-extraconf: move rules from udev and netbase
  udev-extraconf: added to the list of MACHINE_EXTRA_RRECOMMENDS
  udev-extraconf: add rule to rename network interfaces for t4/b4

 conf/machine/e500mc.inc                            |    2 +-
 conf/machine/e500v2.inc                            |    2 +-
 conf/machine/e5500-64b.inc                         |    2 +-
 conf/machine/e5500.inc                             |    2 +-
 conf/machine/e6500-64b.inc                         |    2 +-
 conf/machine/e6500.inc                             |    2 +-
 recipes-append/netbase/netbase_5.0.bbappend        |   10 +---
 recipes-append/procps/files/sysctl.conf            |   64 --------------------
 recipes-append/procps/procps_3.2.8.bbappend        |    3 +-
 .../sysvinit/files/auto-detect-hostname.patch      |   16 -----
 recipes-append/sysvinit/sysvinit_2.88dsf.bbappend  |    5 +-
 recipes-append/udev/udev_182.bbappend              |    3 +-
 .../71-fsl-dpaa-persistent-networking.rules        |    0
 .../72-fsl-dpaa-persistent-networking.rules        |   21 +++++++
 .../udev/udev-extraconf}/local.rules               |    0
 recipes-core/udev/udev-extraconf_1.0.bbappend      |   11 ++++
 ...configure-properly-check-if-lrt-is-needed.patch |   43 +++++++++++++
 recipes-devtools/qemu/qemu_1.0.bb                  |    6 +-
 .../lm_sensors/lmsensors-apps_3.3.2.bb             |   50 ---------------
 recipes-tools/lio-utils/lio-utils_4.0.bb           |    9 ++-
 20 files changed, 95 insertions(+), 158 deletions(-)
 delete mode 100644 recipes-append/procps/files/sysctl.conf
 delete mode 100644 recipes-append/sysvinit/files/auto-detect-hostname.patch
 rename {recipes-append/netbase/files => recipes-core/udev/udev-extraconf}/71-fsl-dpaa-persistent-networking.rules (100%)
 create mode 100644 recipes-core/udev/udev-extraconf/72-fsl-dpaa-persistent-networking.rules
 rename {recipes-append/udev/files => recipes-core/udev/udev-extraconf}/local.rules (100%)
 create mode 100644 recipes-core/udev/udev-extraconf_1.0.bbappend
 create mode 100644 recipes-devtools/qemu/files/0001-configure-properly-check-if-lrt-is-needed.patch
 delete mode 100644 recipes-extended/lm_sensors/lmsensors-apps_3.3.2.bb

-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[b28495]

From: Ting Liu <b28495@freescale.com>

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 .../lm_sensors/lmsensors-apps_3.3.2.bb             |   50 --------------------
 1 files changed, 0 insertions(+), 50 deletions(-)
 delete mode 100644 recipes-extended/lm_sensors/lmsensors-apps_3.3.2.bb

diff --git a/recipes-extended/lm_sensors/lmsensors-apps_3.3.2.bb b/recipes-extended/lm_sensors/lmsensors-apps_3.3.2.bb
deleted file mode 100644
index 62da814..0000000
--- a/recipes-extended/lm_sensors/lmsensors-apps_3.3.2.bb
+++ /dev/null
@@ -1,50 +0,0 @@
-SUMMARY = "A hardware health monitoring package for Linux"
-DESCRIPTION = "Lm-sensors is a hardware health monitoring package for Linux. \
-               It allows you to access information from temperature, voltage, \
-               and fan speed sensors."
-HOMEPAGE = "http://www.lm-sensors.org/"
-DEPENDS = "sysfsutils virtual/libiconv \
-           bison-native flex-native"
-LICENSE = "GPLv2 & LGPLv2.1"
-LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
-                    file://COPYING.LGPL;md5=4fbd65380cdd255951079008b364516c"
-
-PR = "r2"
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-
-SRC_URI = "http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-${PV}.tar.bz2"
-
-SRC_URI[md5sum] = "f357ba00b080ab102a170f7bf8bb2578"
-SRC_URI[sha256sum] = "f13dd885406841a7352ccfb8b9ccb23c4c057abe3de4258da5444c149a9e3ae1"
-
-S = "${WORKDIR}/lm_sensors-${PV}"
-
-EXTRA_OEMAKE = 'LINUX=${STAGING_KERNEL_DIR} EXLDFLAGS="${LDFLAGS}" \
-		MACHINE=${TARGET_ARCH} PREFIX=${prefix} CC="${CC}" \
-		AR="${AR}" MANDIR=${mandir}'
-
-do_compile() {
-	oe_runmake user PROG_EXTRA=sensors
-}
-
-do_install() {
-	oe_runmake user_install DESTDIR=${D}
-}
-
-PACKAGES =+ "libsensors libsensors-dev libsensors-staticdev libsensors-dbg libsensors-doc"
-PACKAGES =+ "lmsensors-sensors lmsensors-sensors-dbg lmsensors-sensors-doc"
-PACKAGES =+ "lmsensors-scripts"
-
-FILES_lmsensors-scripts = "${bindir}/*.pl ${bindir}/ddcmon ${sbindir}/fancontrol* ${sbindir}/pwmconfig ${sbindir}/sensors-detect"
-RDEPENDS_lmsensors-scripts += "lmsensors-sensors perl bash"
-RDEPENDS_lmsensors-apps += "perl-module-strict perl-module-vars perl-module-warnings-register perl-module-warnings"
-RDEPENDS_lmsensors-scripts += "perl-module-fcntl perl-module-exporter perl-module-xsloader perl-module-exporter-heavy perl-module-file-basename perl-module-constant"
-
-FILES_lmsensors-sensors = "${bindir}/sensors ${sysconfdir}"
-FILES_lmsensors-sensors-dbg += "${bindir}/.debug/sensors"
-FILES_lmsensors-sensors-doc = "${mandir}/man1 ${mandir}/man5"
-FILES_libsensors = "${libdir}/libsensors.so.*"
-FILES_libsensors-dbg += "${libdir}/.debug"
-FILES_libsensors-dev = "${libdir}/libsensors.so ${includedir}"
-FILES_libsensors-staticdev = "${libdir}/libsensors.a"
-FILES_libsensors-doc = "${mandir}/man3"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 2/8] qemu: configure properly check if -lrt is needed

[b28495]

From: Ting Liu <b28495@freescale.com>

-lrt is needed to avoid the error "undefined reference to
`timer_settime'". add the check in configure.

Backport from http://git.qemu.org/?p=qemu.git
commit: 8bacde8d86a09699207d85d4bab06162aed18dc4

Fix the below build issue:
| ../qemu-timer.o: In function `dynticks_rearm_timer':
| .../qemu/1.0+fsl-r2/git/qemu-timer.c:597: undefined reference to `timer_gettime'
| .../qemu/1.0+fsl-r2/git/qemu-timer.c:610: undefined reference to `timer_settime'
| ../qemu-timer.o: In function `dynticks_stop_timer':
| .../qemu/1.0+fsl-r2/git/qemu-timer.c:583: undefined reference to `timer_delete'
| ../qemu-timer.o: In function `dynticks_start_timer':
| .../qemu/1.0+fsl-r2/git/qemu-timer.c:565: undefined reference to `timer_create'
| ivshmem.o: In function `pci_ivshmem_init':
| .../qemu/1.0+fsl-r2/git/hw/ivshmem.c:720: undefined reference to `shm_open'
| .../qemu/1.0+fsl-r2/git/hw/ivshmem.c:727: undefined reference to `shm_open'
| collect2: error: ld returned 1 exit status
| make[1]: *** [qemu-system-ppc] Error 1
| make: *** [subdir-ppc-softmmu] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile

Yocto 1.4_M4 uses qemu 1.3.1 which includes this fix. So
this issue only appeared to us.

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 ...configure-properly-check-if-lrt-is-needed.patch |   43 ++++++++++++++++++++
 recipes-devtools/qemu/qemu_1.0.bb                  |    6 ++-
 2 files changed, 47 insertions(+), 2 deletions(-)
 create mode 100644 recipes-devtools/qemu/files/0001-configure-properly-check-if-lrt-is-needed.patch

diff --git a/recipes-devtools/qemu/files/0001-configure-properly-check-if-lrt-is-needed.patch b/recipes-devtools/qemu/files/0001-configure-properly-check-if-lrt-is-needed.patch
new file mode 100644
index 0000000..d74ddb9
--- /dev/null
+++ b/recipes-devtools/qemu/files/0001-configure-properly-check-if-lrt-is-needed.patch
@@ -0,0 +1,43 @@
+From e5906138d8042817cc3b49872dd181c66a11abdf Mon Sep 17 00:00:00 2001
+From: Ting Liu <b28495@freescale.com>
+Date: Wed, 6 Mar 2013 01:56:35 -0600
+Subject: [PATCH] configure: properly check if -lrt is needed
+
+Upstream-Status: Backport
+commit  8bacde8d86a09699207d85d4bab06162aed18dc4
+
+Signed-off-by: Natanael Copa <ncopa@alpinelinux.org>
+Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
+Signed-off-by: Ting Liu <b28495@freescale.com>
+---
+ configure |    9 +++++++--
+ 1 file changed, 7 insertions(+), 2 deletions(-)
+
+diff --git a/configure b/configure
+index 999375a..29b3e30 100755
+--- a/configure
++++ b/configure
+@@ -2444,13 +2444,18 @@ fi
+ cat > $TMPC <<EOF
+ #include <signal.h>
+ #include <time.h>
+-int main(void) { clockid_t id; return clock_gettime(id, NULL); }
++int main(void) {
++  timer_create(CLOCK_REALTIME, NULL, NULL);
++  return clock_gettime(CLOCK_REALTIME, NULL);
++}
+ EOF
+ 
+ if compile_prog "" "" ; then
+   :
+-elif compile_prog "" "-lrt" ; then
++# we need pthread for static linking. use previous pthread test result
++elif compile_prog "" "-lrt $pthread_lib" ; then
+   LIBS="-lrt $LIBS"
++  libs_qga="-lrt $libs_qga"
+ fi
+ 
+ if test "$darwin" != "yes" -a "$mingw32" != "yes" -a "$solaris" != yes -a \
+-- 
+1.7.9.7
+
diff --git a/recipes-devtools/qemu/qemu_1.0.bb b/recipes-devtools/qemu/qemu_1.0.bb
index ff4afde..19efd9f 100644
--- a/recipes-devtools/qemu/qemu_1.0.bb
+++ b/recipes-devtools/qemu/qemu_1.0.bb
@@ -5,11 +5,13 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=441c28d2cf86e15a37fa47e15a72fbac \
 
 # This means v1.0 with FSL specific patches applied
 PV = "1.0+fsl"
-PR = "r2"
+PR = "r3"
 
 DEPENDS += "dtc"
 
-SRC_URI = "git://git.freescale.com/ppc/sdk/qemu.git"
+SRC_URI = "git://git.freescale.com/ppc/sdk/qemu.git \
+            file://0001-configure-properly-check-if-lrt-is-needed.patch \
+"
 SRCREV = "7feabd47a814214dc4bebfd97d0eaf30dc50a68f"
 
 S = "${WORKDIR}/git"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 3/8] lio-utils: add tcm_start.sh and lio_start.sh to rootfs

[b28495]

From: Chunrong Guo <b40290@freescale.com>

           *following scripts had  been added
            /etc/init.d/target
            /etc/target/tcm_start.sh
            /etc/target/lio_start.sh

Signed-off-by: Chunrong Guo <b40290@freescale.com>
---
 recipes-tools/lio-utils/lio-utils_4.0.bb |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/recipes-tools/lio-utils/lio-utils_4.0.bb b/recipes-tools/lio-utils/lio-utils_4.0.bb
index 31aa4fa..98101b3 100644
--- a/recipes-tools/lio-utils/lio-utils_4.0.bb
+++ b/recipes-tools/lio-utils/lio-utils_4.0.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "http://linux-iscsi.org/index.php/Lio-utils"
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://debian/copyright;md5=c3ea231a32635cbb5debedf3e88aa3df"
 
-PR = "r1"
+PR = "r2"
 
 SRC_URI = "git://risingtidesystems.com/lio-utils.git;protocal=git \
     file://lio-utils-install-more-modules.patch "
@@ -46,13 +46,16 @@ do_install() {
     if test -d ${S}/tools; then
         oe_runmake install
     fi
-
+ 
+    install -d ${D}/etc/target/
     install -d ${D}/etc/init.d/
     install -m 755 ${S}/scripts/rc.target ${D}/etc/init.d/
+    install -m 755 ${S}/conf/tcm_start.default ${D}/etc/target/tcm_start.sh
+    install -m 755 ${S}/conf/lio_start.default ${D}/etc/target/lio_start.sh
 }
 
 RDEPENDS_${PN} += "python-stringold python-subprocess python-shell \ 
     python-datetime python-textutils python-crypt python-netclient python-email"
 
 
-FILES_${PN} += "${sbindir}/* /etc/init.d/*"
+FILES_${PN} += "${sbindir}/* /etc/init.d/* /etc/target/*"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 4/8] sysvinit: remove SDK specific bits

[b28495]

From: Ting Liu <b28495@freescale.com>

This is fsl SDK specific, and was recommended to go to SDK layer:
http://patches.openembedded.org/patch/34623/

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 .../sysvinit/files/auto-detect-hostname.patch      |   16 ----------------
 recipes-append/sysvinit/sysvinit_2.88dsf.bbappend  |    5 +----
 2 files changed, 1 insertions(+), 20 deletions(-)
 delete mode 100644 recipes-append/sysvinit/files/auto-detect-hostname.patch

diff --git a/recipes-append/sysvinit/files/auto-detect-hostname.patch b/recipes-append/sysvinit/files/auto-detect-hostname.patch
deleted file mode 100644
index da70184..0000000
--- a/recipes-append/sysvinit/files/auto-detect-hostname.patch
+++ /dev/null
@@ -1,16 +0,0 @@
-diff --git a/rcS b/rcS
-index 080b04f..51425ff 100755
---- a/rcS
-+++ b/rcS
-@@ -22,6 +22,11 @@ export PATH runlevel prevlevel
- . /etc/default/rcS
- 
- #
-+#       Update the hostname according to actual board type
-+#
-+echo `cat /proc/cpuinfo | grep model | cut -d "," -f 2 | tr "[A-Z]" "[a-z]"` > /etc/hostname
-+
-+#
- #	Trap CTRL-C &c only in this shell so we can interrupt subprocesses.
- #
- trap ":" INT QUIT TSTP
diff --git a/recipes-append/sysvinit/sysvinit_2.88dsf.bbappend b/recipes-append/sysvinit/sysvinit_2.88dsf.bbappend
index 9c9dc75..8445337 100644
--- a/recipes-append/sysvinit/sysvinit_2.88dsf.bbappend
+++ b/recipes-append/sysvinit/sysvinit_2.88dsf.bbappend
@@ -1,5 +1,2 @@
-FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
+PRINC := "${@int(PRINC) + 1}"
 
-PR_fsl .= "+${DISTRO}.1"
-
-SRC_URI_append_fsl = " file://auto-detect-hostname.patch;patchdir=../"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 5/8] procps: remove customized sysctl.conf which is SDK specific

[b28495]

From: Ting Liu <b28495@freescale.com>

It was added to disable rp_filter to enhance ASF IP forward
performance, which is really fsl SDK specific.

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 recipes-append/procps/files/sysctl.conf     |   64 ---------------------------
 recipes-append/procps/procps_3.2.8.bbappend |    3 +-
 2 files changed, 1 insertions(+), 66 deletions(-)
 delete mode 100644 recipes-append/procps/files/sysctl.conf

diff --git a/recipes-append/procps/files/sysctl.conf b/recipes-append/procps/files/sysctl.conf
deleted file mode 100644
index 6148472..0000000
--- a/recipes-append/procps/files/sysctl.conf
+++ /dev/null
@@ -1,64 +0,0 @@
-# This configuration file is taken from Debian.
-#
-# /etc/sysctl.conf - Configuration file for setting system variables
-# See sysctl.conf (5) for information.
-#
-
-#kernel.domainname = example.com
-
-# Uncomment the following to stop low-level messages on console
-#kernel.printk = 4 4 1 7
-
-##############################################################3
-# Functions previously found in netbase
-#
-
-# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
-# Turn on Source Address Verification in all interfaces to
-# prevent some spoofing attacks
-net.ipv4.conf.default.rp_filter=0
-net.ipv4.conf.all.rp_filter=0
-
-# Uncomment the next line to enable TCP/IP SYN cookies
-#net.ipv4.tcp_syncookies=1
-
-# Uncomment the next line to enable packet forwarding for IPv4
-#net.ipv4.ip_forward=1
-
-# Uncomment the next line to enable packet forwarding for IPv6
-#net.ipv6.conf.all.forwarding=1
-
-
-###################################################################
-# Additional settings - these settings can improve the network
-# security of the host and prevent against some network attacks
-# including spoofing attacks and man in the middle attacks through
-# redirection. Some network environments, however, require that these
-# settings are disabled so review and enable them as needed.
-#
-# Ignore ICMP broadcasts
-#net.ipv4.icmp_echo_ignore_broadcasts = 1
-#
-# Ignore bogus ICMP errors
-#net.ipv4.icmp_ignore_bogus_error_responses = 1
-#
-# Do not accept ICMP redirects (prevent MITM attacks)
-#net.ipv4.conf.all.accept_redirects = 0
-#net.ipv6.conf.all.accept_redirects = 0
-# _or_
-# Accept ICMP redirects only for gateways listed in our default
-# gateway list (enabled by default)
-# net.ipv4.conf.all.secure_redirects = 1
-#
-# Do not send ICMP redirects (we are not a router)
-#net.ipv4.conf.all.send_redirects = 0
-#
-# Do not accept IP source route packets (we are not a router)
-#net.ipv4.conf.all.accept_source_route = 0
-#net.ipv6.conf.all.accept_source_route = 0
-#
-# Log Martian Packets
-#net.ipv4.conf.all.log_martians = 1
-#
-
-#kernel.shmmax = 141762560
diff --git a/recipes-append/procps/procps_3.2.8.bbappend b/recipes-append/procps/procps_3.2.8.bbappend
index f5d4fd1..8445337 100644
--- a/recipes-append/procps/procps_3.2.8.bbappend
+++ b/recipes-append/procps/procps_3.2.8.bbappend
@@ -1,3 +1,2 @@
-PR_fsl .= "+${DISTRO}.0"
+PRINC := "${@int(PRINC) + 1}"
 
-FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 6/8] udev-extraconf: move rules from udev and netbase

[b28495]

From: Ting Liu <b28495@freescale.com>

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 recipes-append/netbase/netbase_5.0.bbappend        |   10 +---------
 recipes-append/udev/udev_182.bbappend              |    3 +--
 .../71-fsl-dpaa-persistent-networking.rules        |    0
 .../udev/udev-extraconf}/local.rules               |    0
 recipes-core/udev/udev-extraconf_1.0.bbappend      |   11 +++++++++++
 5 files changed, 13 insertions(+), 11 deletions(-)
 rename {recipes-append/netbase/files => recipes-core/udev/udev-extraconf}/71-fsl-dpaa-persistent-networking.rules (100%)
 rename {recipes-append/udev/files => recipes-core/udev/udev-extraconf}/local.rules (100%)
 create mode 100644 recipes-core/udev/udev-extraconf_1.0.bbappend

diff --git a/recipes-append/netbase/netbase_5.0.bbappend b/recipes-append/netbase/netbase_5.0.bbappend
index dc0fd0a..8445337 100644
--- a/recipes-append/netbase/netbase_5.0.bbappend
+++ b/recipes-append/netbase/netbase_5.0.bbappend
@@ -1,10 +1,2 @@
-FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
+PRINC := "${@int(PRINC) + 1}"
 
-SRC_URI_append_fsl += "file://71-fsl-dpaa-persistent-networking.rules"
-
-do_install_append_fsl () {
-	install -d ${D}${sysconfdir}/udev/rules.d/
-	install -m 0644 ${WORKDIR}/71-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
-}
-
-PR_fsl .= "+${DISTRO}"
diff --git a/recipes-append/udev/udev_182.bbappend b/recipes-append/udev/udev_182.bbappend
index f15533b..8445337 100644
--- a/recipes-append/udev/udev_182.bbappend
+++ b/recipes-append/udev/udev_182.bbappend
@@ -1,3 +1,2 @@
-FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
+PRINC := "${@int(PRINC) + 1}"
 
-PR_fsl .= "+${DISTRO}.1"
diff --git a/recipes-append/netbase/files/71-fsl-dpaa-persistent-networking.rules b/recipes-core/udev/udev-extraconf/71-fsl-dpaa-persistent-networking.rules
similarity index 100%
rename from recipes-append/netbase/files/71-fsl-dpaa-persistent-networking.rules
rename to recipes-core/udev/udev-extraconf/71-fsl-dpaa-persistent-networking.rules
diff --git a/recipes-append/udev/files/local.rules b/recipes-core/udev/udev-extraconf/local.rules
similarity index 100%
rename from recipes-append/udev/files/local.rules
rename to recipes-core/udev/udev-extraconf/local.rules
diff --git a/recipes-core/udev/udev-extraconf_1.0.bbappend b/recipes-core/udev/udev-extraconf_1.0.bbappend
new file mode 100644
index 0000000..f3ddb8e
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf_1.0.bbappend
@@ -0,0 +1,11 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/udev-extraconf:"
+
+PRINC := "${@int(PRINC) + 1}"
+
+SRC_URI_append = " file://71-fsl-dpaa-persistent-networking.rules"
+
+do_install_append () {
+    install -d ${D}${sysconfdir}/udev/rules.d/
+    install -m 0644 ${WORKDIR}/71-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
+}
+
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 7/8] udev-extraconf: added to the list of MACHINE_EXTRA_RRECOMMENDS

[b28495]

From: Ting Liu <b28495@freescale.com>

It will then added into packagegroup-basic and packagegroup-base.

Signed-off-by: Ting Liu <b28495@freescale.com>
---
 conf/machine/e500mc.inc    |    2 +-
 conf/machine/e500v2.inc    |    2 +-
 conf/machine/e5500-64b.inc |    2 +-
 conf/machine/e5500.inc     |    2 +-
 conf/machine/e6500-64b.inc |    2 +-
 conf/machine/e6500.inc     |    2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/conf/machine/e500mc.inc b/conf/machine/e500mc.inc
index 505d805..e523a87 100644
--- a/conf/machine/e500mc.inc
+++ b/conf/machine/e500mc.inc
@@ -3,7 +3,7 @@ TARGET_FPU = "hard"
 require conf/machine/include/tune-ppce500mc.inc
 
 MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
diff --git a/conf/machine/e500v2.inc b/conf/machine/e500v2.inc
index 12086f7..cb3d7ad 100644
--- a/conf/machine/e500v2.inc
+++ b/conf/machine/e500v2.inc
@@ -1,7 +1,7 @@
 require conf/machine/include/tune-ppce500v2.inc
 
 MACHINE_FEATURES = "kernel26 pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
diff --git a/conf/machine/e5500-64b.inc b/conf/machine/e5500-64b.inc
index 650585f..d2fa078 100644
--- a/conf/machine/e5500-64b.inc
+++ b/conf/machine/e5500-64b.inc
@@ -4,7 +4,7 @@ DEFAULTTUNE ?= "ppc64e5500"
 require conf/machine/include/tune-ppce5500.inc
 
 MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
diff --git a/conf/machine/e5500.inc b/conf/machine/e5500.inc
index 1a1bb20..09870c9 100644
--- a/conf/machine/e5500.inc
+++ b/conf/machine/e5500.inc
@@ -3,7 +3,7 @@ TARGET_FPU = "hard"
 require conf/machine/include/tune-ppce5500.inc
 
 MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
diff --git a/conf/machine/e6500-64b.inc b/conf/machine/e6500-64b.inc
index 85bcb39..57e61b2 100644
--- a/conf/machine/e6500-64b.inc
+++ b/conf/machine/e6500-64b.inc
@@ -4,7 +4,7 @@ DEFAULTTUNE ?= "ppc64e6500"
 require conf/machine/include/tune-ppce6500.inc
 
 MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
diff --git a/conf/machine/e6500.inc b/conf/machine/e6500.inc
index 31c61a2..b343742 100644
--- a/conf/machine/e6500.inc
+++ b/conf/machine/e6500.inc
@@ -3,7 +3,7 @@ TARGET_FPU = "hard"
 require conf/machine/include/tune-ppce6500.inc
 
 MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial"
-MACHINE_EXTRA_RRECOMMENDS = "u-boot"
+MACHINE_EXTRA_RRECOMMENDS = "u-boot udev-extraconf"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.34"
-- 
1.7.3.4

[meta-fsl-ppc][PATCH v4 8/8] udev-extraconf: add rule to rename network interfaces for t4/b4

[b28495]

From: Ting Liu <b28495@freescale.com>

Since on FManv3 a MEMAC can be configured either as 1G or 10G, rename
all interfaces on T4/B4 to "fmX-macY", with X in the range 1..2 and
Y in the range 1..10.

Signed-off-by: Zhenhua Luo <b19537@freescale.com>
Signed-off-by: Ioana Radulescu <ruxandra.radulescu@freescale.com>
Signed-off-by: Ting Liu <b28495@freescale.com>
---
 .../72-fsl-dpaa-persistent-networking.rules        |   21 ++++++++++++++++++++
 recipes-core/udev/udev-extraconf_1.0.bbappend      |    8 +++---
 2 files changed, 25 insertions(+), 4 deletions(-)
 create mode 100644 recipes-core/udev/udev-extraconf/72-fsl-dpaa-persistent-networking.rules

diff --git a/recipes-core/udev/udev-extraconf/72-fsl-dpaa-persistent-networking.rules b/recipes-core/udev/udev-extraconf/72-fsl-dpaa-persistent-networking.rules
new file mode 100644
index 0000000..34e72a3
--- /dev/null
+++ b/recipes-core/udev/udev-extraconf/72-fsl-dpaa-persistent-networking.rules
@@ -0,0 +1,21 @@
+# Rules for handling naming the DPAA FMan ethernet ports in a consistent way
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4e0000", NAME="fm1-mac1"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4e2000", NAME="fm1-mac2"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4e4000", NAME="fm1-mac3"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4e6000", NAME="fm1-mac4"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4e8000", NAME="fm1-mac5"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4ea000", NAME="fm1-mac6"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4ec000", NAME="fm1-mac7"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4ee000", NAME="fm1-mac8"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4f0000", NAME="fm1-mac9"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe4f2000", NAME="fm1-mac10"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5e0000", NAME="fm2-mac1"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5e2000", NAME="fm2-mac2"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5e4000", NAME="fm2-mac3"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5e6000", NAME="fm2-mac4"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5e8000", NAME="fm2-mac5"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5ea000", NAME="fm2-mac6"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5ec000", NAME="fm2-mac7"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5ee000", NAME="fm2-mac8"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5f0000", NAME="fm2-mac9"
+SUBSYSTEM=="net", DRIVERS=="fsl_dpa", ATTR{device_addr}=="ffe5f2000", NAME="fm2-mac10"
diff --git a/recipes-core/udev/udev-extraconf_1.0.bbappend b/recipes-core/udev/udev-extraconf_1.0.bbappend
index f3ddb8e..f938e92 100644
--- a/recipes-core/udev/udev-extraconf_1.0.bbappend
+++ b/recipes-core/udev/udev-extraconf_1.0.bbappend
@@ -1,11 +1,11 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/udev-extraconf:"
+PRINC := "${@int(PRINC) + 2}"
 
-PRINC := "${@int(PRINC) + 1}"
-
-SRC_URI_append = " file://71-fsl-dpaa-persistent-networking.rules"
+SRC_URI_append = " file://${@bb.utils.contains("TUNE_FEATURES", "e6500", \
+    "72-fsl-dpaa-persistent-networking.rules", "71-fsl-dpaa-persistent-networking.rules", d)}"
 
 do_install_append () {
     install -d ${D}${sysconfdir}/udev/rules.d/
-    install -m 0644 ${WORKDIR}/71-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
+    install -m 0644 ${WORKDIR}/*-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
 }
 
-- 
1.7.3.4

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Otavio Salvador]

On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> From: Ting Liu <b28495@freescale.com>
>
> Signed-off-by: Ting Liu <b28495@freescale.com>

I have just checked the revision used in meta-oe and it is 'r1' so
you'll need to keep an bbappend to add PRINC otherwise we'll lost
upgrade path.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 6/8] udev-extraconf: move rules from udev and netbase

[Otavio Salvador]

On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> From: Ting Liu <b28495@freescale.com>
>
> Signed-off-by: Ting Liu <b28495@freescale.com>
> ---
>  recipes-append/netbase/netbase_5.0.bbappend        |   10 +---------
>  recipes-append/udev/udev_182.bbappend              |    3 +--
>  .../71-fsl-dpaa-persistent-networking.rules        |    0
>  .../udev/udev-extraconf}/local.rules               |    0
>  recipes-core/udev/udev-extraconf_1.0.bbappend      |   11 +++++++++++
>  5 files changed, 13 insertions(+), 11 deletions(-)
>  rename {recipes-append/netbase/files => recipes-core/udev/udev-extraconf}/71-fsl-dpaa-persistent-networking.rules (100%)
>  rename {recipes-append/udev/files => recipes-core/udev/udev-extraconf}/local.rules (100%)
>  create mode 100644 recipes-core/udev/udev-extraconf_1.0.bbappend
>
> diff --git a/recipes-append/netbase/netbase_5.0.bbappend b/recipes-append/netbase/netbase_5.0.bbappend
> index dc0fd0a..8445337 100644
> --- a/recipes-append/netbase/netbase_5.0.bbappend
> +++ b/recipes-append/netbase/netbase_5.0.bbappend
> @@ -1,10 +1,2 @@
> -FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
> +PRINC := "${@int(PRINC) + 1}"
>
> -SRC_URI_append_fsl += "file://71-fsl-dpaa-persistent-networking.rules"
> -
> -do_install_append_fsl () {
> -       install -d ${D}${sysconfdir}/udev/rules.d/
> -       install -m 0644 ${WORKDIR}/71-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
> -}
> -
> -PR_fsl .= "+${DISTRO}"
> diff --git a/recipes-append/udev/udev_182.bbappend b/recipes-append/udev/udev_182.bbappend
> index f15533b..8445337 100644
> --- a/recipes-append/udev/udev_182.bbappend
> +++ b/recipes-append/udev/udev_182.bbappend
> @@ -1,3 +1,2 @@
> -FILESEXTRAPATHS_prepend_fsl := "${THISDIR}/files:"
> +PRINC := "${@int(PRINC) + 1}"
>
> -PR_fsl .= "+${DISTRO}.1"
> diff --git a/recipes-append/netbase/files/71-fsl-dpaa-persistent-networking.rules b/recipes-core/udev/udev-extraconf/71-fsl-dpaa-persistent-networking.rules
> similarity index 100%
> rename from recipes-append/netbase/files/71-fsl-dpaa-persistent-networking.rules
> rename to recipes-core/udev/udev-extraconf/71-fsl-dpaa-persistent-networking.rules
> diff --git a/recipes-append/udev/files/local.rules b/recipes-core/udev/udev-extraconf/local.rules
> similarity index 100%
> rename from recipes-append/udev/files/local.rules
> rename to recipes-core/udev/udev-extraconf/local.rules
> diff --git a/recipes-core/udev/udev-extraconf_1.0.bbappend b/recipes-core/udev/udev-extraconf_1.0.bbappend
> new file mode 100644
> index 0000000..f3ddb8e
> --- /dev/null
> +++ b/recipes-core/udev/udev-extraconf_1.0.bbappend
> @@ -0,0 +1,11 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/udev-extraconf:"

I'd use ${PN} here.

> +PRINC := "${@int(PRINC) + 1}"
> +
> +SRC_URI_append = " file://71-fsl-dpaa-persistent-networking.rules"
> +
> +do_install_append () {
> +    install -d ${D}${sysconfdir}/udev/rules.d/
> +    install -m 0644 ${WORKDIR}/71-fsl-dpaa-persistent-networking.rules ${D}${sysconfdir}/udev/rules.d
> +}
> +
> --
> 1.7.3.4
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale



-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Liu Ting-B28495]

> -----Original Message-----
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> Behalf Of Otavio Salvador
> Sent: Saturday, March 09, 2013 8:21 PM
> To: Liu Ting-B28495
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> lm_sensor as it is already in meta-oe
> 
> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> > From: Ting Liu <b28495@freescale.com>
> >
> > Signed-off-by: Ting Liu <b28495@freescale.com>
> 
> I have just checked the revision used in meta-oe and it is 'r1' so you'll
> need to keep an bbappend to add PRINC otherwise we'll lost upgrade path.
> 

It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and lmsensors_3.3.2.bb in 
meta-oe. But they are the same pkg. I think we can skip to bump PR as they are using 
'different' recipe name.
If it does not make sense, I will generate new patches.

-Ting

> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Otavio Salvador]

On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495 <B28495@freescale.com> wrote:
>> -----Original Message-----
>> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> Behalf Of Otavio Salvador
>> Sent: Saturday, March 09, 2013 8:21 PM
>> To: Liu Ting-B28495
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> lm_sensor as it is already in meta-oe
>>
>> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
>> > From: Ting Liu <b28495@freescale.com>
>> >
>> > Signed-off-by: Ting Liu <b28495@freescale.com>
>>
>> I have just checked the revision used in meta-oe and it is 'r1' so you'll
>> need to keep an bbappend to add PRINC otherwise we'll lost upgrade path.
>>
>
> It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and lmsensors_3.3.2.bb in
> meta-oe. But they are the same pkg. I think we can skip to bump PR as they are using
> 'different' recipe name.
> If it does not make sense, I will generate new patches.

Regarding the PR you're right, good catch! However we need to take
care of binary packages. You should provide a
RPROVIDES/RREPLACES/RCONFLICTS for the binary packages which were
renamed so the upgrade path works.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Liu Ting-B28495]

> -----Original Message-----
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> Behalf Of Otavio Salvador
> Sent: Saturday, March 09, 2013 10:54 PM
> To: Liu Ting-B28495
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> lm_sensor as it is already in meta-oe
> 
> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495 <B28495@freescale.com>
> wrote:
> >> -----Original Message-----
> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> >> Behalf Of Otavio Salvador
> >> Sent: Saturday, March 09, 2013 8:21 PM
> >> To: Liu Ting-B28495
> >> Cc: meta-freescale@yoctoproject.org
> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> >> lm_sensor as it is already in meta-oe
> >>
> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> >> > From: Ting Liu <b28495@freescale.com>
> >> >
> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
> >>
> >> I have just checked the revision used in meta-oe and it is 'r1' so
> >> you'll need to keep an bbappend to add PRINC otherwise we'll lost
> upgrade path.
> >>
> >
> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I think we
> > can skip to bump PR as they are using 'different' recipe name.
> > If it does not make sense, I will generate new patches.
> 
> Regarding the PR you're right, good catch! However we need to take care
> of binary packages. You should provide a RPROVIDES/RREPLACES/RCONFLICTS
> for the binary packages which were renamed so the upgrade path works.
> 

I think we can skip it too. They are identical, just with different name. 
RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will install 
the two at the same time. They will find lmsensors-apps has gone away and 
use the one in meta-oe.

-Ting

> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Otavio Salvador]

On Sat, Mar 9, 2013 at 12:21 PM, Liu Ting-B28495 <B28495@freescale.com> wrote:
>> -----Original Message-----
>> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> Behalf Of Otavio Salvador
>> Sent: Saturday, March 09, 2013 10:54 PM
>> To: Liu Ting-B28495
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> lm_sensor as it is already in meta-oe
>>
>> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495 <B28495@freescale.com>
>> wrote:
>> >> -----Original Message-----
>> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> >> Behalf Of Otavio Salvador
>> >> Sent: Saturday, March 09, 2013 8:21 PM
>> >> To: Liu Ting-B28495
>> >> Cc: meta-freescale@yoctoproject.org
>> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> >> lm_sensor as it is already in meta-oe
>> >>
>> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
>> >> > From: Ting Liu <b28495@freescale.com>
>> >> >
>> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
>> >>
>> >> I have just checked the revision used in meta-oe and it is 'r1' so
>> >> you'll need to keep an bbappend to add PRINC otherwise we'll lost
>> upgrade path.
>> >>
>> >
>> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
>> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I think we
>> > can skip to bump PR as they are using 'different' recipe name.
>> > If it does not make sense, I will generate new patches.
>>
>> Regarding the PR you're right, good catch! However we need to take care
>> of binary packages. You should provide a RPROVIDES/RREPLACES/RCONFLICTS
>> for the binary packages which were renamed so the upgrade path works.
>>
>
> I think we can skip it too. They are identical, just with different name.
> RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will install
> the two at the same time. They will find lmsensors-apps has gone away and
> use the one in meta-oe.

If someone has an image and has a lmsensors-apps-<foo> it will fail to
build. That's why you should have the overrides so the images will not
need to be changed to be kept working.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Liu Ting-B28495]

> -----Original Message-----
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> Behalf Of Otavio Salvador
> Sent: Saturday, March 09, 2013 11:34 PM
> To: Liu Ting-B28495
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> lm_sensor as it is already in meta-oe
> 
> On Sat, Mar 9, 2013 at 12:21 PM, Liu Ting-B28495 <B28495@freescale.com>
> wrote:
> >> -----Original Message-----
> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> >> Behalf Of Otavio Salvador
> >> Sent: Saturday, March 09, 2013 10:54 PM
> >> To: Liu Ting-B28495
> >> Cc: meta-freescale@yoctoproject.org
> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> >> lm_sensor as it is already in meta-oe
> >>
> >> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495
> >> <B28495@freescale.com>
> >> wrote:
> >> >> -----Original Message-----
> >> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com]
> >> >> On Behalf Of Otavio Salvador
> >> >> Sent: Saturday, March 09, 2013 8:21 PM
> >> >> To: Liu Ting-B28495
> >> >> Cc: meta-freescale@yoctoproject.org
> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> >> >> lm_sensor as it is already in meta-oe
> >> >>
> >> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> >> >> > From: Ting Liu <b28495@freescale.com>
> >> >> >
> >> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
> >> >>
> >> >> I have just checked the revision used in meta-oe and it is 'r1' so
> >> >> you'll need to keep an bbappend to add PRINC otherwise we'll lost
> >> upgrade path.
> >> >>
> >> >
> >> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
> >> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I think
> >> > we can skip to bump PR as they are using 'different' recipe name.
> >> > If it does not make sense, I will generate new patches.
> >>
> >> Regarding the PR you're right, good catch! However we need to take
> >> care of binary packages. You should provide a
> >> RPROVIDES/RREPLACES/RCONFLICTS for the binary packages which were
> renamed so the upgrade path works.
> >>
> >
> > I think we can skip it too. They are identical, just with different
> name.
> > RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will
> > install the two at the same time. They will find lmsensors-apps has
> > gone away and use the one in meta-oe.
> 
> If someone has an image and has a lmsensors-apps-<foo> it will fail to
> build. That's why you should have the overrides so the images will not
> need to be changed to be kept working.

So they will know the changes and use the right pkg name in image :-)

-Ting

> 
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Otavio Salvador]

On Sat, Mar 9, 2013 at 12:37 PM, Liu Ting-B28495 <B28495@freescale.com> wrote:
>> -----Original Message-----
>> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> Behalf Of Otavio Salvador
>> Sent: Saturday, March 09, 2013 11:34 PM
>> To: Liu Ting-B28495
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> lm_sensor as it is already in meta-oe
>>
>> On Sat, Mar 9, 2013 at 12:21 PM, Liu Ting-B28495 <B28495@freescale.com>
>> wrote:
>> >> -----Original Message-----
>> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> >> Behalf Of Otavio Salvador
>> >> Sent: Saturday, March 09, 2013 10:54 PM
>> >> To: Liu Ting-B28495
>> >> Cc: meta-freescale@yoctoproject.org
>> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> >> lm_sensor as it is already in meta-oe
>> >>
>> >> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495
>> >> <B28495@freescale.com>
>> >> wrote:
>> >> >> -----Original Message-----
>> >> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com]
>> >> >> On Behalf Of Otavio Salvador
>> >> >> Sent: Saturday, March 09, 2013 8:21 PM
>> >> >> To: Liu Ting-B28495
>> >> >> Cc: meta-freescale@yoctoproject.org
>> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> >> >> lm_sensor as it is already in meta-oe
>> >> >>
>> >> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
>> >> >> > From: Ting Liu <b28495@freescale.com>
>> >> >> >
>> >> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
>> >> >>
>> >> >> I have just checked the revision used in meta-oe and it is 'r1' so
>> >> >> you'll need to keep an bbappend to add PRINC otherwise we'll lost
>> >> upgrade path.
>> >> >>
>> >> >
>> >> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
>> >> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I think
>> >> > we can skip to bump PR as they are using 'different' recipe name.
>> >> > If it does not make sense, I will generate new patches.
>> >>
>> >> Regarding the PR you're right, good catch! However we need to take
>> >> care of binary packages. You should provide a
>> >> RPROVIDES/RREPLACES/RCONFLICTS for the binary packages which were
>> renamed so the upgrade path works.
>> >>
>> >
>> > I think we can skip it too. They are identical, just with different
>> name.
>> > RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will
>> > install the two at the same time. They will find lmsensors-apps has
>> > gone away and use the one in meta-oe.
>>
>> If someone has an image and has a lmsensors-apps-<foo> it will fail to
>> build. That's why you should have the overrides so the images will not
>> need to be changed to be kept working.
>
> So they will know the changes and use the right pkg name in image :-)

This breaks user image; we ought to avoid to do that. People using the
BSP/SDK are kept working nowadays so you're moving them to a new
package so please take care to not break them.

I won't ack the package without a proper upgrade path. Matt, your call.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Liu Ting-B28495]

> -----Original Message-----
> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> Behalf Of Otavio Salvador
> Sent: Saturday, March 09, 2013 11:40 PM
> To: Liu Ting-B28495
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> lm_sensor as it is already in meta-oe
> 
> On Sat, Mar 9, 2013 at 12:37 PM, Liu Ting-B28495 <B28495@freescale.com>
> wrote:
> >> -----Original Message-----
> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> >> Behalf Of Otavio Salvador
> >> Sent: Saturday, March 09, 2013 11:34 PM
> >> To: Liu Ting-B28495
> >> Cc: meta-freescale@yoctoproject.org
> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> >> lm_sensor as it is already in meta-oe
> >>
> >> On Sat, Mar 9, 2013 at 12:21 PM, Liu Ting-B28495
> >> <B28495@freescale.com>
> >> wrote:
> >> >> -----Original Message-----
> >> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com]
> >> >> On Behalf Of Otavio Salvador
> >> >> Sent: Saturday, March 09, 2013 10:54 PM
> >> >> To: Liu Ting-B28495
> >> >> Cc: meta-freescale@yoctoproject.org
> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
> >> >> lm_sensor as it is already in meta-oe
> >> >>
> >> >> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495
> >> >> <B28495@freescale.com>
> >> >> wrote:
> >> >> >> -----Original Message-----
> >> >> >> From: otavio.salvador@gmail.com
> >> >> >> [mailto:otavio.salvador@gmail.com]
> >> >> >> On Behalf Of Otavio Salvador
> >> >> >> Sent: Saturday, March 09, 2013 8:21 PM
> >> >> >> To: Liu Ting-B28495
> >> >> >> Cc: meta-freescale@yoctoproject.org
> >> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8]
> >> >> >> remove lm_sensor as it is already in meta-oe
> >> >> >>
> >> >> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
> >> >> >> > From: Ting Liu <b28495@freescale.com>
> >> >> >> >
> >> >> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
> >> >> >>
> >> >> >> I have just checked the revision used in meta-oe and it is 'r1'
> >> >> >> so you'll need to keep an bbappend to add PRINC otherwise we'll
> >> >> >> lost
> >> >> upgrade path.
> >> >> >>
> >> >> >
> >> >> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
> >> >> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I
> >> >> > think we can skip to bump PR as they are using 'different' recipe
> name.
> >> >> > If it does not make sense, I will generate new patches.
> >> >>
> >> >> Regarding the PR you're right, good catch! However we need to take
> >> >> care of binary packages. You should provide a
> >> >> RPROVIDES/RREPLACES/RCONFLICTS for the binary packages which were
> >> renamed so the upgrade path works.
> >> >>
> >> >
> >> > I think we can skip it too. They are identical, just with different
> >> name.
> >> > RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will
> >> > install the two at the same time. They will find lmsensors-apps has
> >> > gone away and use the one in meta-oe.
> >>
> >> If someone has an image and has a lmsensors-apps-<foo> it will fail
> >> to build. That's why you should have the overrides so the images will
> >> not need to be changed to be kept working.
> >
> > So they will know the changes and use the right pkg name in image :-)
> 
> This breaks user image; we ought to avoid to do that. People using the
> BSP/SDK are kept working nowadays so you're moving them to a new package
> so please take care to not break them.

Consider this case: people include poky, meta-fsl-ppc and other layers except meta-oe. If we remove lmsensors-apps_3.3.2.bb in meta-fsl-ppc, then their image that has lmsensors-apps will absolutely fail to build. I wonder how to get a proper upgrade path in this case? Dose RPROVIDES/RREPLACES/RCONFLICTS works? They have to do some changes.

-Ting

> 
> I won't ack the package without a proper upgrade path. Matt, your call.

All right.
RPROVIDES/RREPLACES/RCONFLICTS
> 
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Matthew McClintock]

Ting, Otavio,

I think Otavio is referring to binary feeds to some degree here? Where
in a package has already generated an ipk/deb/rpm and it's being
upgraded in a live install. It's worth noting that some SDKs use this
method to upgrading / deploying vs. doing a build from source that
poky does.

With that in mind, given the package has changed we may need a
RREPLACES? I'm really not that familiar with this and I don't know
that anyone that uses ppc does this method yet. Do any SDKs/DISTROs
out there do this with meta-fsl-ppc? If so speak up, or let me know if
I am completely off base.

Also, please CC me on the patches and commentary so I see it sooner.

-M

On Sun, Mar 10, 2013 at 9:10 PM, Liu Ting-B28495 <B28495@freescale.com> wrote:
>> -----Original Message-----
>> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> Behalf Of Otavio Salvador
>> Sent: Saturday, March 09, 2013 11:40 PM
>> To: Liu Ting-B28495
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> lm_sensor as it is already in meta-oe
>>
>> On Sat, Mar 9, 2013 at 12:37 PM, Liu Ting-B28495 <B28495@freescale.com>
>> wrote:
>> >> -----Original Message-----
>> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
>> >> Behalf Of Otavio Salvador
>> >> Sent: Saturday, March 09, 2013 11:34 PM
>> >> To: Liu Ting-B28495
>> >> Cc: meta-freescale@yoctoproject.org
>> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> >> lm_sensor as it is already in meta-oe
>> >>
>> >> On Sat, Mar 9, 2013 at 12:21 PM, Liu Ting-B28495
>> >> <B28495@freescale.com>
>> >> wrote:
>> >> >> -----Original Message-----
>> >> >> From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com]
>> >> >> On Behalf Of Otavio Salvador
>> >> >> Sent: Saturday, March 09, 2013 10:54 PM
>> >> >> To: Liu Ting-B28495
>> >> >> Cc: meta-freescale@yoctoproject.org
>> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8] remove
>> >> >> lm_sensor as it is already in meta-oe
>> >> >>
>> >> >> On Sat, Mar 9, 2013 at 11:37 AM, Liu Ting-B28495
>> >> >> <B28495@freescale.com>
>> >> >> wrote:
>> >> >> >> -----Original Message-----
>> >> >> >> From: otavio.salvador@gmail.com
>> >> >> >> [mailto:otavio.salvador@gmail.com]
>> >> >> >> On Behalf Of Otavio Salvador
>> >> >> >> Sent: Saturday, March 09, 2013 8:21 PM
>> >> >> >> To: Liu Ting-B28495
>> >> >> >> Cc: meta-freescale@yoctoproject.org
>> >> >> >> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH v4 1/8]
>> >> >> >> remove lm_sensor as it is already in meta-oe
>> >> >> >>
>> >> >> >> On Sat, Mar 9, 2013 at 12:30 AM,  <b28495@freescale.com> wrote:
>> >> >> >> > From: Ting Liu <b28495@freescale.com>
>> >> >> >> >
>> >> >> >> > Signed-off-by: Ting Liu <b28495@freescale.com>
>> >> >> >>
>> >> >> >> I have just checked the revision used in meta-oe and it is 'r1'
>> >> >> >> so you'll need to keep an bbappend to add PRINC otherwise we'll
>> >> >> >> lost
>> >> >> upgrade path.
>> >> >> >>
>> >> >> >
>> >> >> > It is named as lmsensors-apps_3.3.2.bb in meta-fsl-ppc, and
>> >> >> > lmsensors_3.3.2.bb in meta-oe. But they are the same pkg. I
>> >> >> > think we can skip to bump PR as they are using 'different' recipe
>> name.
>> >> >> > If it does not make sense, I will generate new patches.
>> >> >>
>> >> >> Regarding the PR you're right, good catch! However we need to take
>> >> >> care of binary packages. You should provide a
>> >> >> RPROVIDES/RREPLACES/RCONFLICTS for the binary packages which were
>> >> renamed so the upgrade path works.
>> >> >>
>> >> >
>> >> > I think we can skip it too. They are identical, just with different
>> >> name.
>> >> > RPROVIDES/RREPLACES/RCONFLICTS does not make sense. No one will
>> >> > install the two at the same time. They will find lmsensors-apps has
>> >> > gone away and use the one in meta-oe.
>> >>
>> >> If someone has an image and has a lmsensors-apps-<foo> it will fail
>> >> to build. That's why you should have the overrides so the images will
>> >> not need to be changed to be kept working.
>> >
>> > So they will know the changes and use the right pkg name in image :-)
>>
>> This breaks user image; we ought to avoid to do that. People using the
>> BSP/SDK are kept working nowadays so you're moving them to a new package
>> so please take care to not break them.
>
> Consider this case: people include poky, meta-fsl-ppc and other layers except meta-oe. If we remove lmsensors-apps_3.3.2.bb in meta-fsl-ppc, then their image that has lmsensors-apps will absolutely fail to build. I wonder how to get a proper upgrade path in this case? Dose RPROVIDES/RREPLACES/RCONFLICTS works? They have to do some changes.
>
> -Ting
>
>>
>> I won't ack the package without a proper upgrade path. Matt, your call.
>
> All right.
> RPROVIDES/RREPLACES/RCONFLICTS
>>
>> --
>> Otavio Salvador                             O.S. Systems
>> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
>> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-fsl-ppc][PATCH v4 1/8] remove lm_sensor as it is already in meta-oe

[Otavio Salvador]

On Tue, Mar 12, 2013 at 1:21 AM, Matthew McClintock
<msm-oss@mcclintock.net> wrote:
> Ting, Otavio,
>
> I think Otavio is referring to binary feeds to some degree here? Where
> in a package has already generated an ipk/deb/rpm and it's being
> upgraded in a live install. It's worth noting that some SDKs use this
> method to upgrading / deploying vs. doing a build from source that
> poky does.

Yes; correct.

> With that in mind, given the package has changed we may need a
> RREPLACES? I'm really not that familiar with this and I don't know
> that anyone that uses ppc does this method yet. Do any SDKs/DISTROs
> out there do this with meta-fsl-ppc? If so speak up, or let me know if
> I am completely off base.

RPROVIDES, RCONFLICTS and RREPLACES.

> Also, please CC me on the patches and commentary so I see it sooner.

Will do :-) Thanks :-D

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br