[yocto] [meta-intel][PATCH] mce-test: add it
Signed-off-by: Dengke Du
---
.../mce-test/files/makefile-remove-ldflags.patch | 23 +++
recipes-kernel/mce-test/mce-test_git.bb| 48 ++
2 files changed, 71 insertions(+)
create mode 100644 recipes-kernel/mce-test/files/makefile-remove-ldflags.patch
create mode 100644 recipes-kernel/mce-test/mce-test_git.bb
diff --git a/recipes-kernel/mce-test/files/makefile-remove-ldflags.patch
b/recipes-kernel/mce-test/files/makefile-remove-ldflags.patch
new file mode 100644
index 000..0ffedd2
--- /dev/null
+++ b/recipes-kernel/mce-test/files/makefile-remove-ldflags.patch
@@ -0,0 +1,23 @@
+Remove the default CFLAGS and LDFLAGS in Makefile. Ensure the extra linker
flags can be passed.
+
+Upstream-Status: Inappropriate [embedded specific]
+
+Signed-off-by: Yi Zhao
+
+diff --git a/cases/stress/hwpoison/Makefile b/cases/stress/hwpoison/Makefile
+index da1cbd8..dec5b14 100644
+--- a/cases/stress/hwpoison/Makefile
b/cases/stress/hwpoison/Makefile
+@@ -1,8 +1,8 @@
+-CFLAGS := -g -Wall
+-LDFLAGS := -g
++#CFLAGS := -g -Wall
++#LDFLAGS := -g
+
+-export CFLAGS
+-export LDFLAGS
++#export CFLAGS
++#export LDFLAGS
+
+ all:
+ mkdir -p bin
diff --git a/recipes-kernel/mce-test/mce-test_git.bb
b/recipes-kernel/mce-test/mce-test_git.bb
new file mode 100644
index 000..5c86d07
--- /dev/null
+++ b/recipes-kernel/mce-test/mce-test_git.bb
@@ -0,0 +1,48 @@
+#
+# Copyright (C) 2012 Wind River Systems, Inc.
+#
+SUMMARY = "MCE test suite"
+
+DESCRIPTION = "The MCE test suite is a collection of tools and test scripts
for \
+testing the Linux RAS related features, including CPU/Memory error \
+containment and recovery, ACPI/APEI support etc."
+
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3"
+
+PR = "r2"
+
+SRC_URI =
"git://git.kernel.org/pub/scm/linux/kernel/git/gong.chen/mce-test.git;protocol=git
\
+ file://makefile-remove-ldflags.patch \
+ "
+# Use the commit date of SRCREV in PV.
+#
+SRCREV = "b3fdfaa7a025b68f30913c9cc7a8fe4ae9c7ed7f"
+PE = "1"
+PV = "20131218+git${SRCPV}"
+
+RDEPENDS_${PN} = "mcelog mce-inject dialog bash"
+
+COMPATIBLE_HOST = '(i.86|x86_64).*-linux'
+
+S ="${WORKDIR}/git"
+
+inherit autotools-brokensep
+
+do_install_append(){
+ install -d ${D}/opt/mce-test
+ cp -rf ${S}/* ${D}/opt/mce-test/
+}
+
+FILES_${PN} += "/opt"
+FILES_${PN}-dbg += "/opt/mce-test/cases/function/hwpoison/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/cases/function/erst-inject/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/cases/function/pfa/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/cases/function/core_recovery/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/cases/stress/hwpoison/bin/.debug"
+FILES_${PN}-dbg +=
"/opt/mce-test/cases/stress/hwpoison/tools/page-poisoning/.debug"
+FILES_${PN}-dbg +=
"/opt/mce-test/cases/stress/hwpoison/tools/fs-metadata/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/bin/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/tools/ltp-pan/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/tools/simple_process/.debug"
+FILES_${PN}-dbg += "/opt/mce-test/tools/page-types/.debug"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-raspberrypi systemd rpi0-w bluetooth startup
After some tests, I found the following appearance:
1) When I add "enable_uart=1" to the /boot/config.txt, the
brcm43438.service(use /dev/ttyAMA0) can start successfully *definitely*.
2) When I remove "enable_uart=1" from the /boot/config.txt, the
brcm43438.service can't start always.
You can try the 1).
On 2018年03月20日 23:17, r10kindsofpeople wrote:
FWIW: Dengke's email caused me to wonder why the RDEPENDS in bluez
hadn't triggered the inclusion of udev-rules-rpi in the first place.
I now suspect that when I tried to switch from 'rocko' to 'master',
the steps I took to force a rebuild were insufficient, and bluez5 was
not recompiled with the new patches, including the patch to increase
the timeout. I'm not able to check it at the moment, but will try to
retrace my steps when I get a chance.
John
On Tue, Mar 20, 2018 at 10:13 AM r10kindsofpeople
mailto:r10kindsofpeo...@gmail.com>> wrote:
Thanks Dengke, I thought I tried using the line
"After=dev-ttyAMA0.device" and referring to /dev/ttyAMA0 in the
hciattach command and the brcm43438.service was still being
triggered before the /dev/ttyAMA0 device was actually available on
some boots, but I may have had something else wrong at that point,
or I may be recalling incorrectly. If it works for you, great.
It doesn't make sense to me that we'd need the udev-rules-rpi for
bluez, but then refer to /dev/ttyAMA0 in the service. I thought
the point of the 99-com.rules file created by udev-rules-rpi was
to create a symbolic link equating /dev/ttyAMA0 and /dev/serial1
on the rpi0w.
It's my impression that the move to use /dev/serial1 (as an alias
for /dev/ttyAMA0) is an attempt to make software written for the
Raspberry Pi more portable across all variants of the Pi, since
some variants swap the role of /dev/ttyS0 and /dev/ttyAMA0 for the
console or swap which one is available on the GPIO expansion. Or
perhaps the goal was portablilty from Raspbian to Yocto and back.
The steps I outlined retain that, and still seem to work
reliably. I'm not entirely comfortable with relying on the udev
script to trigger the service that runs hciattach, (and all of
bluez dependent on that), but acknowledge that I don't know enough
about systemd and udev to know "proper" from "improper".
John
On Mon, Mar 19, 2018 at 11:01 PM Dengke Du
mailto:dengke...@windriver.com>> wrote:
Raspberry pi have two built-in UARTs, PL011 and mini UART
by default: /dev/ttyS0 refers to the mini UART, /dev/ttyAMA0
refers to the PL011
https://www.raspberrypi.org/documentation/configuration/uart.md
So I think the brcm43438 service should use the /dev/ttyAMA0.
On 2018年03月20日 10:41, Dengke Du wrote:
For rpi0-w bluetooth, before the commit:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-70e4910388c3702c52118d7acf7556e7
the brcm43438.service always failed, because it depends on
/dev/ttyAMA0,after that commit, the 'udev-rules-rpi' added to
the RDEPENDS for rpi0-w,we
can check it here:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-3b2568c620828b0ba653c1070041318aR52
for service brcm43438, but I still use the /dev/ttyAMA0 in
it, not /dev/serial1(when I use /dev/serial1, the service
failed), the service can start everytime correctly.
On 2018年03月19日 02:10, r10kindsofpeople wrote:
Update: I suspect this is not the proper way to do this,
but in case it provides useful information toward a better
solution...
1) systemctl disable brcm43438.service
2) modified 99-com.rules to include TAG+="systemd" and
ENV{SYSTEMD_WANTS}="device-brcm43438.service"
3) cp /lib/systemd/system/brcm43438.service
/etc/systemd/system/device-brcm43438.service
4) modified device-brcm43438.service to be as follows:
[Unit]
Description=Broadcom BCM43438 bluetooth HCI
[Service]
Type=simple
ExecStart=/usr/bin/hciattach -n /dev/serial1 bcm43xx 921600
noflow -
Restart=on-failure
note removal of Before, After, ConditionPath, Install
sections and addition of Restart=on-failure. This last was
to cope with an intermittent timeout in hciattach. Suppose
I should have tried increasing the timeout first.
This seems to have gotten me to the point of it starting up
at least 10 times successfully. Bottom line, in my opinion,
is that brcm43438.service is somehow running before the
udev script can create the symbolic link for
Re: [yocto] meta-raspberrypi systemd rpi0-w bluetooth startup
Raspberry pi have two built-in UARTs, PL011 and mini UART
by default: /dev/ttyS0 refers to the mini UART, /dev/ttyAMA0 refers to
the PL011
https://www.raspberrypi.org/documentation/configuration/uart.md
So I think the brcm43438 service should use the /dev/ttyAMA0.
On 2018年03月20日 10:41, Dengke Du wrote:
For rpi0-w bluetooth, before the commit:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-70e4910388c3702c52118d7acf7556e7
the brcm43438.service always failed, because it depends on
/dev/ttyAMA0,after that commit, the 'udev-rules-rpi' added to the
RDEPENDS for rpi0-w,we
can check it here:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-3b2568c620828b0ba653c1070041318aR52
for service brcm43438, but I still use the /dev/ttyAMA0 in it, not
/dev/serial1(when I use /dev/serial1, the service failed), the service
can start everytime correctly.
On 2018年03月19日 02:10, r10kindsofpeople wrote:
Update: I suspect this is not the proper way to do this, but in case
it provides useful information toward a better solution...
1) systemctl disable brcm43438.service
2) modified 99-com.rules to include TAG+="systemd" and
ENV{SYSTEMD_WANTS}="device-brcm43438.service"
3) cp /lib/systemd/system/brcm43438.service
/etc/systemd/system/device-brcm43438.service
4) modified device-brcm43438.service to be as follows:
[Unit]
Description=Broadcom BCM43438 bluetooth HCI
[Service]
Type=simple
ExecStart=/usr/bin/hciattach -n /dev/serial1 bcm43xx 921600 noflow -
Restart=on-failure
note removal of Before, After, ConditionPath, Install sections and
addition of Restart=on-failure. This last was to cope with an
intermittent timeout in hciattach. Suppose I should have tried
increasing the timeout first.
This seems to have gotten me to the point of it starting up at least
10 times successfully. Bottom line, in my opinion, is that
brcm43438.service is somehow running before the udev script can
create the symbolic link for /dev/serial1 -> /dev/ttyAMA0 despite the
"After=dev-serial1.device" clause.
John
On Sat, Mar 17, 2018 at 12:32 PM r10kindsofpeople
mailto:r10kindsofpeo...@gmail.com>> wrote:
Background: I'm trying to bring up the pi zero w's bluetooth
using systemd. Started with rocko and then moved to 'master' of
meta-raspberry pi, sync'd about a week ago after noticing that
there were some recent updates in this area.
There was an initial problem with /dev/serial1 not showing up...I
found udev-rules-rpi.bb <http://udev-rules-rpi.bb>, added it to
my layer, and when it still didn't show up in my rootfs, I punted
and installed it in /etc/udev/rules.d by hand and now
/dev/serial1 shows up. Given time, I can probably fix the recipe
on my own, so moving on.
But brcm43438.service still fails on boot. Despite having
"After=dev-serial1.device" in the service Unit section, it fails
with:
Mar 17 16:21:13 raspberrypi0-wifi systemd[1]: Started Broadcom
BCM43438 bluetooth HCI.
Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't open
serial port: No such file or directory
Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't
initialize device: No such file or directory
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Main process exited, code=exited,
status=1/FAILURE[[0m
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Unit entered failed state.[[0m
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Failed with result 'exit-code'.[[0m
If, after booting and ssh'ing into pi, I restart the service, it
starts successfully.
Any hints about what I might change to get the brcm43438.service
to start correctly the first time (every time)?
John
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-raspberrypi systemd rpi0-w bluetooth startup
For rpi0-w bluetooth, before the commit:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-70e4910388c3702c52118d7acf7556e7
the brcm43438.service always failed, because it depends on
/dev/ttyAMA0,after that commit, the 'udev-rules-rpi' added to the
RDEPENDS for rpi0-w,we
can check it here:
https://github.com/agherzan/meta-raspberrypi/commit/6235b0a8543bcf6704d0fe0156ab2b847a4ea0bc#diff-3b2568c620828b0ba653c1070041318aR52
for service brcm43438, but I still use the /dev/ttyAMA0 in it, not
/dev/serial1(when I use /dev/serial1, the service failed), the service
can start everytime correctly.
On 2018年03月19日 02:10, r10kindsofpeople wrote:
Update: I suspect this is not the proper way to do this, but in case
it provides useful information toward a better solution...
1) systemctl disable brcm43438.service
2) modified 99-com.rules to include TAG+="systemd" and
ENV{SYSTEMD_WANTS}="device-brcm43438.service"
3) cp /lib/systemd/system/brcm43438.service
/etc/systemd/system/device-brcm43438.service
4) modified device-brcm43438.service to be as follows:
[Unit]
Description=Broadcom BCM43438 bluetooth HCI
[Service]
Type=simple
ExecStart=/usr/bin/hciattach -n /dev/serial1 bcm43xx 921600 noflow -
Restart=on-failure
note removal of Before, After, ConditionPath, Install sections and
addition of Restart=on-failure. This last was to cope with an
intermittent timeout in hciattach. Suppose I should have tried
increasing the timeout first.
This seems to have gotten me to the point of it starting up at least
10 times successfully. Bottom line, in my opinion, is that
brcm43438.service is somehow running before the udev script can
create the symbolic link for /dev/serial1 -> /dev/ttyAMA0 despite the
"After=dev-serial1.device" clause.
John
On Sat, Mar 17, 2018 at 12:32 PM r10kindsofpeople
mailto:r10kindsofpeo...@gmail.com>> wrote:
Background: I'm trying to bring up the pi zero w's bluetooth
using systemd. Started with rocko and then moved to 'master' of
meta-raspberry pi, sync'd about a week ago after noticing that
there were some recent updates in this area.
There was an initial problem with /dev/serial1 not showing up...I
found udev-rules-rpi.bb , added it to my
layer, and when it still didn't show up in my rootfs, I punted and
installed it in /etc/udev/rules.d by hand and now /dev/serial1
shows up. Given time, I can probably fix the recipe on my own, so
moving on.
But brcm43438.service still fails on boot. Despite having
"After=dev-serial1.device" in the service Unit section, it fails with:
Mar 17 16:21:13 raspberrypi0-wifi systemd[1]: Started Broadcom
BCM43438 bluetooth HCI.
Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't open
serial port: No such file or directory
Mar 17 16:21:14 raspberrypi0-wifi hciattach[105]: Can't initialize
device: No such file or directory
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Main process exited, code=exited,
status=1/FAILURE[[0m
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Unit entered failed state.[[0m
Mar 17 16:21:14 raspberrypi0-wifi systemd[1]:
[[0;1;39mbrcm43438.service: Failed with result 'exit-code'.[[0m
If, after booting and ssh'ing into pi, I restart the service, it
starts successfully.
Any hints about what I might change to get the brcm43438.service
to start correctly the first time (every time)?
John
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Bluetooth
On 2017年12月15日 13:55, Sherif Omran wrote: when i do hciattach, i get initialization timeout. This is a bug for initialization timeout: https://github.com/agherzan/meta-raspberrypi/issues/148 Sometimes it works, sometimes it would not work. Still need research on it. could it be a branch related? Not branch related. I am using the morty branch meta-yocto-bsp: morty meta-raspberrypi: morty On Fri, Dec 15, 2017 at 6:30 AM, Dengke Du <mailto:dengke...@windriver.com>> wrote: You should attach the bluez stack with the raspberry firmware bcm43xx: hciattact -n /dev/ttyAMA0 bcm43xx 921600 noflow - or if you use systemd: systemctl restart brcm43438.service Now you can see the the device: rfkill list all Enable it: rfkill unblock all hciconfig hci0 up Checking the bluetooth: hciconfig -a On 2017年12月15日 12:43, Sherif Omran wrote: hello i ve been strugggeling since couple of days with raspberry pi 0 board and can not figure out how to enable the chip, whether it is enabled by default or it needs some intervention. I generated the rpi-basic-image and tested with the hiconfigure -a but the chip is not detected. Any body had similar issue and got it to solve? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Bluetooth
You should attach the bluez stack with the raspberry firmware bcm43xx: hciattact -n /dev/ttyAMA0 bcm43xx 921600 noflow - or if you use systemd: systemctl restart brcm43438.service Now you can see the the device: rfkill list all Enable it: rfkill unblock all hciconfig hci0 up Checking the bluetooth: hciconfig -a On 2017年12月15日 12:43, Sherif Omran wrote: hello i ve been strugggeling since couple of days with raspberry pi 0 board and can not figure out how to enable the chip, whether it is enabled by default or it needs some intervention. I generated the rpi-basic-image and tested with the hiconfigure -a but the chip is not detected. Any body had similar issue and got it to solve? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH V2] bluepy: add it
The bluepy can let us programming bluetooth le application in python.
Signed-off-by: Dengke Du
---
recipes-devtools/bluepy/bluepy_git.bb | 48 ++
...compiling-get-the-cross-compiler-from-env.patch | 28 +
2 files changed, 76 insertions(+)
create mode 100644 recipes-devtools/bluepy/bluepy_git.bb
create mode 100644
recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
diff --git a/recipes-devtools/bluepy/bluepy_git.bb
b/recipes-devtools/bluepy/bluepy_git.bb
new file mode 100644
index 000..3e2e7de
--- /dev/null
+++ b/recipes-devtools/bluepy/bluepy_git.bb
@@ -0,0 +1,48 @@
+SUMMARY = "Python module for interfacing with BLE devices through Bluez"
+HOMEPAGE = "https://github.com/IanHarvey/bluepy";
+# WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses
- it is
+# your responsibility to verify that the values are complete and correct.
+#
+# The following license files were not able to be identified and are
+# represented as "Unknown" below, you will need to check them yourself:
+# LICENSE.txt
+# bluez-5.29/COPYING.LIB
+#
+# NOTE: multiple licenses have been detected; they have been separated with &
+# in the LICENSE value for now since it is a reasonable assumption that all
+# of the licenses apply. If instead there is a choice between the multiple
+# licenses then you should change the value to separate the licenses with |
+# instead of &. If there is any doubt, check the accompanying documentation
+# to determine which situation is applicable.
+LICENSE = "Unknown & GPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=59e0d45ea684dda215889aa1b5acd001 \
+
file://bluez-5.29/COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
+
file://bluez-5.29/COPYING.LIB;md5=fb504b67c50331fc78734fed90fb0e09"
+
+SRC_URI = "git://github.com/IanHarvey/bluepy.git;protocol=https \
+
file://0001-When-cross-compiling-get-the-cross-compiler-from-env.patch \
+"
+
+# Modify these as desired
+PV = "1.1.2+git${SRCPV}"
+SRCREV = "b1178fba2729692532e02d95e7368c742814f725"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools
+
+DEPENDS += " glib-2.0"
+
+# WARNING: the following rdepends are determined through basic analysis of the
+# python sources, and might not be 100% accurate.
+RDEPENDS_${PN} += "python-argparse python-core python-io python-json
python-subprocess"
+
+# WARNING: We were unable to map the following python package/module
+# dependencies to the bitbake packages which include them:
+#bluepy
+#bluepy.btle
+#bs4
+#requests
+
+INHIBIT_PACKAGE_STRIP = "1"
+INSANE_SKIP_${PN} += "ldflags"
diff --git
a/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
b/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
new file mode 100644
index 000..8799058
--- /dev/null
+++
b/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
@@ -0,0 +1,28 @@
+From abf880ff4c276134564e1f1e63a3b6699060da7f Mon Sep 17 00:00:00 2001
+From: Dengke Du
+Date: Mon, 27 Nov 2017 03:48:16 -0500
+Subject: [PATCH] When cross compiling, get the cross compiler from environment
+
+Signed-off-by: Dengke Du
+---
+ bluepy/Makefile | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/bluepy/Makefile b/bluepy/Makefile
+index 76bafec..42f145b 100644
+--- a/bluepy/Makefile
b/bluepy/Makefile
+@@ -9,8 +9,8 @@ BLUEZ_SRCS += src/shared/io-glib.c src/shared/timeout-glib.c
+ IMPORT_SRCS = $(addprefix $(BLUEZ_PATH)/, $(BLUEZ_SRCS))
+ LOCAL_SRCS = bluepy-helper.c
+
+-CC = gcc
+-CFLAGS = -Os -g -Wall # -Werror
++CC ?= gcc
++CFLAGS ?= -Os -g -Wall # -Werror
+
+ CPPFLAGS = -DHAVE_CONFIG_H
+ ifneq ($(DEBUGGING),)
+--
+2.8.1
+
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [[meta-raspberrypi]][PATCH] bluepy: add it
The bluepy can let us programming bluetooth le application in python.
Signed-off-by: Dengke Du
---
recipes-devtools/bluepy/bluepy_git.bb | 48 ++
...compiling-get-the-cross-compiler-from-env.patch | 28 +
2 files changed, 76 insertions(+)
create mode 100644 recipes-devtools/bluepy/bluepy_git.bb
create mode 100644
recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
diff --git a/recipes-devtools/bluepy/bluepy_git.bb
b/recipes-devtools/bluepy/bluepy_git.bb
new file mode 100644
index 000..3e2e7de
--- /dev/null
+++ b/recipes-devtools/bluepy/bluepy_git.bb
@@ -0,0 +1,48 @@
+SUMMARY = "Python module for interfacing with BLE devices through Bluez"
+HOMEPAGE = "https://github.com/IanHarvey/bluepy";
+# WARNING: the following LICENSE and LIC_FILES_CHKSUM values are best guesses
- it is
+# your responsibility to verify that the values are complete and correct.
+#
+# The following license files were not able to be identified and are
+# represented as "Unknown" below, you will need to check them yourself:
+# LICENSE.txt
+# bluez-5.29/COPYING.LIB
+#
+# NOTE: multiple licenses have been detected; they have been separated with &
+# in the LICENSE value for now since it is a reasonable assumption that all
+# of the licenses apply. If instead there is a choice between the multiple
+# licenses then you should change the value to separate the licenses with |
+# instead of &. If there is any doubt, check the accompanying documentation
+# to determine which situation is applicable.
+LICENSE = "Unknown & GPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=59e0d45ea684dda215889aa1b5acd001 \
+
file://bluez-5.29/COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
+
file://bluez-5.29/COPYING.LIB;md5=fb504b67c50331fc78734fed90fb0e09"
+
+SRC_URI = "git://github.com/IanHarvey/bluepy.git;protocol=https \
+
file://0001-When-cross-compiling-get-the-cross-compiler-from-env.patch \
+"
+
+# Modify these as desired
+PV = "1.1.2+git${SRCPV}"
+SRCREV = "b1178fba2729692532e02d95e7368c742814f725"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools
+
+DEPENDS += " glib-2.0"
+
+# WARNING: the following rdepends are determined through basic analysis of the
+# python sources, and might not be 100% accurate.
+RDEPENDS_${PN} += "python-argparse python-core python-io python-json
python-subprocess"
+
+# WARNING: We were unable to map the following python package/module
+# dependencies to the bitbake packages which include them:
+#bluepy
+#bluepy.btle
+#bs4
+#requests
+
+INHIBIT_PACKAGE_STRIP = "1"
+INSANE_SKIP_${PN} += "ldflags"
diff --git
a/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
b/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
new file mode 100644
index 000..8799058
--- /dev/null
+++
b/recipes-devtools/bluepy/files/0001-When-cross-compiling-get-the-cross-compiler-from-env.patch
@@ -0,0 +1,28 @@
+From abf880ff4c276134564e1f1e63a3b6699060da7f Mon Sep 17 00:00:00 2001
+From: Dengke Du
+Date: Mon, 27 Nov 2017 03:48:16 -0500
+Subject: [PATCH] When cross compiling, get the cross compiler from environment
+
+Signed-off-by: Dengke Du
+---
+ bluepy/Makefile | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/bluepy/Makefile b/bluepy/Makefile
+index 76bafec..42f145b 100644
+--- a/bluepy/Makefile
b/bluepy/Makefile
+@@ -9,8 +9,8 @@ BLUEZ_SRCS += src/shared/io-glib.c src/shared/timeout-glib.c
+ IMPORT_SRCS = $(addprefix $(BLUEZ_PATH)/, $(BLUEZ_SRCS))
+ LOCAL_SRCS = bluepy-helper.c
+
+-CC = gcc
+-CFLAGS = -Os -g -Wall # -Werror
++CC ?= gcc
++CFLAGS ?= -Os -g -Wall # -Werror
+
+ CPPFLAGS = -DHAVE_CONFIG_H
+ ifneq ($(DEBUGGING),)
+--
+2.8.1
+
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH V2] keynote: update the SRC_URI
The old URL can't be available, give the new URL to keynote.
The project already moved to:
https://sourceforge.net/projects/keynote-2-3/
The different between old and new tarball was:
the old tarball contains doc directory, source codes were same.
Signed-off-by: Dengke Du
---
recipes-security/keynote/keynote_2.3.bb | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/recipes-security/keynote/keynote_2.3.bb
b/recipes-security/keynote/keynote_2.3.bb
index b1df880..e692485 100644
--- a/recipes-security/keynote/keynote_2.3.bb
+++ b/recipes-security/keynote/keynote_2.3.bb
@@ -9,16 +9,19 @@ SECTION = "security"
LICENSE = "ISC"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3a265095c549c1808686a676f2699c98"
-SRC_URI = "http://www.cs.columbia.edu/~angelos/Code/${BPN}.tar.gz \
+MAIN_ID = "${@d.getVar('PV').split('.')[0]}"
+MINOR_ID = "${@d.getVar('PV').split('.')[1]}"
+SRC_URI =
"${SOURCEFORGE_MIRROR}/project/${BPN}-${MAIN_ID}-${MINOR_ID}/${BPN}_${PV}.tar.gz
\
file://configure-remove-hardcode-path.patch \
file://makefile-add-ldflags.patch \
file://run-ptest \
"
+S = "${WORKDIR}/${BPN}-${PV}+dfsg.orig"
inherit autotools-brokensep ptest
-SRC_URI[md5sum] = "ba58a0297c421dc6aa671e6b753ef695"
-SRC_URI[sha256sum] =
"62f7a9d57ceb6bcdd47b604b637a7ac8ed337cef0ab02f1fa28b7e61c9b15821"
+SRC_URI[md5sum] = "a14553e6ad921b5c85026ce5bec3afe7"
+SRC_URI[sha256sum] =
"38d2acfa1c3630a07adcb5c8fe92d2aef7f0e6d242b8998b2bbb1c6e4c408d46"
DEPENDS = "flex openssl"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] keynote: update the SRC_URI
The old URL can't be available, give the new URL to keynote.
The project already moved to:
https://sourceforge.net/projects/keynote-2-3/
Signed-off-by: Dengke Du
---
recipes-security/keynote/keynote_2.3.bb | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/recipes-security/keynote/keynote_2.3.bb
b/recipes-security/keynote/keynote_2.3.bb
index b1df880..23e75e4 100644
--- a/recipes-security/keynote/keynote_2.3.bb
+++ b/recipes-security/keynote/keynote_2.3.bb
@@ -9,16 +9,19 @@ SECTION = "security"
LICENSE = "ISC"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3a265095c549c1808686a676f2699c98"
-SRC_URI = "http://www.cs.columbia.edu/~angelos/Code/${BPN}.tar.gz \
+MAIN_ID = "${@d.getVar('PV').split('.')[0]}"
+MINOR_ID = "${@d.getVar('PV').split('.')[1]}"
+SRC_URI =
"${SOURCEFORGE_MIRROR}/project/${PN}-${MAIN_ID}-${MINOR_ID}/${PN}_${PV}.tar.gz \
file://configure-remove-hardcode-path.patch \
file://makefile-add-ldflags.patch \
file://run-ptest \
"
+S = "${WORKDIR}/${PN}-${PV}+dfsg.orig"
inherit autotools-brokensep ptest
-SRC_URI[md5sum] = "ba58a0297c421dc6aa671e6b753ef695"
-SRC_URI[sha256sum] =
"62f7a9d57ceb6bcdd47b604b637a7ac8ed337cef0ab02f1fa28b7e61c9b15821"
+SRC_URI[md5sum] = "a14553e6ad921b5c85026ce5bec3afe7"
+SRC_URI[sha256sum] =
"38d2acfa1c3630a07adcb5c8fe92d2aef7f0e6d242b8998b2bbb1c6e4c408d46"
DEPENDS = "flex openssl"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH V5] rpm: modify the rpm bbappend file to suitable for rpm4
Changed in V5:
Let the subject more clear.
Changed in V4:
Make the comments more clear.
Changed in V3:
Rebase the patch on the latest master branch.
Delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/rpm_%.bbappend | 4
1 file changed, 4 deletions(-)
diff --git a/recipes-devtools/rpm/rpm_%.bbappend
b/recipes-devtools/rpm/rpm_%.bbappend
index 199a7e4..9f3ec90 100644
--- a/recipes-devtools/rpm/rpm_%.bbappend
+++ b/recipes-devtools/rpm/rpm_%.bbappend
@@ -1,8 +1,4 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
inherit with-selinux
PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V4] rpm: modify the rpm bbappend file to suitable for rpm4
Changed in V4:
Make the comments more clear.
Changed in V3:
Rebase the patch on the latest master branch.
Delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/rpm_%.bbappend | 4
1 file changed, 4 deletions(-)
diff --git a/recipes-devtools/rpm/rpm_%.bbappend
b/recipes-devtools/rpm/rpm_%.bbappend
index 199a7e4..9f3ec90 100644
--- a/recipes-devtools/rpm/rpm_%.bbappend
+++ b/recipes-devtools/rpm/rpm_%.bbappend
@@ -1,8 +1,4 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
inherit with-selinux
PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH V3] rpm: modify the rpm bbappend file to suitable for rpm4
Changed in V3:
rebase the patch on the latest master branch.
1. change the rpm_5.4.16.bbappend to rpm_git.bbappend, this is
because the rpm in oe-core has become rpm4 from rpm5.
2. drop the patch for rpm5.
3. delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/{rpm_%.bbappend => rpm_git.bbappend} | 4
1 file changed, 4 deletions(-)
rename recipes-devtools/rpm/{rpm_%.bbappend => rpm_git.bbappend} (56%)
diff --git a/recipes-devtools/rpm/rpm_%.bbappend
b/recipes-devtools/rpm/rpm_git.bbappend
similarity index 56%
rename from recipes-devtools/rpm/rpm_%.bbappend
rename to recipes-devtools/rpm/rpm_git.bbappend
index 199a7e4..9f3ec90 100644
--- a/recipes-devtools/rpm/rpm_%.bbappend
+++ b/recipes-devtools/rpm/rpm_git.bbappend
@@ -1,8 +1,4 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
inherit with-selinux
PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] rpm: modify the rpm bbappend file to suitable for rpm4
1. change the rpm_5.4.16.bbappend to rpm_git.bbappend, this is
because the rpm in oe-core has become rpm4 from rpm5.
2. drop the patch for rpm5.
3. delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/rpm_5.4.16.bbappend | 10 --
recipes-devtools/rpm/rpm_git.bbappend| 4
2 files changed, 4 insertions(+), 10 deletions(-)
delete mode 100644 recipes-devtools/rpm/rpm_5.4.16.bbappend
create mode 100644 recipes-devtools/rpm/rpm_git.bbappend
diff --git a/recipes-devtools/rpm/rpm_5.4.16.bbappend
b/recipes-devtools/rpm/rpm_5.4.16.bbappend
deleted file mode 100644
index 2a41a28..000
--- a/recipes-devtools/rpm/rpm_5.4.16.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://rpm-fix-build-bug.patch \
- "
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
-inherit with-selinux
-PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
diff --git a/recipes-devtools/rpm/rpm_git.bbappend
b/recipes-devtools/rpm/rpm_git.bbappend
new file mode 100644
index 000..9f3ec90
--- /dev/null
+++ b/recipes-devtools/rpm/rpm_git.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+inherit with-selinux
+PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-selinux][PATCH] rpm: modify the rpm bbappend file to suitable for rpm4
Please ignore this, thanks.
On 2017年05月09日 15:41, Dengke Du wrote:
1. change the rpm_5.4.16.bbappend to rpm_git.bbappend, this is
because the rpm in oe-core has become rpm4 from rpm5.
2. drop the patch for rpm5.
3. delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/rpm_5.4.16.bbappend | 10 --
recipes-devtools/rpm/rpm_git.bbappend| 4
2 files changed, 4 insertions(+), 10 deletions(-)
delete mode 100644 recipes-devtools/rpm/rpm_5.4.16.bbappend
create mode 100644 recipes-devtools/rpm/rpm_git.bbappend
diff --git a/recipes-devtools/rpm/rpm_5.4.16.bbappend
b/recipes-devtools/rpm/rpm_5.4.16.bbappend
deleted file mode 100644
index 2a41a28..000
--- a/recipes-devtools/rpm/rpm_5.4.16.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://rpm-fix-build-bug.patch \
- "
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
-inherit with-selinux
-PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
diff --git a/recipes-devtools/rpm/rpm_git.bbappend
b/recipes-devtools/rpm/rpm_git.bbappend
new file mode 100644
index 000..9f3ec90
--- /dev/null
+++ b/recipes-devtools/rpm/rpm_git.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+inherit with-selinux
+PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] rpm: modify the rpm bbappend file to suitable for rpm4
1. change the rpm_5.4.16.bbappend to rpm_git.bbappend, this is
because the rpm in oe-core has become rpm4 from rpm5.
2. drop the patch for rpm5.
3. delete the does not exist files when run task do_package.
Signed-off-by: Dengke Du
---
recipes-devtools/rpm/rpm_5.4.16.bbappend | 10 --
recipes-devtools/rpm/rpm_git.bbappend| 4
2 files changed, 4 insertions(+), 10 deletions(-)
delete mode 100644 recipes-devtools/rpm/rpm_5.4.16.bbappend
create mode 100644 recipes-devtools/rpm/rpm_git.bbappend
diff --git a/recipes-devtools/rpm/rpm_5.4.16.bbappend
b/recipes-devtools/rpm/rpm_5.4.16.bbappend
deleted file mode 100644
index 2a41a28..000
--- a/recipes-devtools/rpm/rpm_5.4.16.bbappend
+++ /dev/null
@@ -1,10 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "file://rpm-fix-build-bug.patch \
- "
-FILES_${PN} += "${libdir}/rpm/bin/spooktool \
-${libdir}/rpm/bin/semodule \
- "
-
-inherit with-selinux
-PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
diff --git a/recipes-devtools/rpm/rpm_git.bbappend
b/recipes-devtools/rpm/rpm_git.bbappend
new file mode 100644
index 000..9f3ec90
--- /dev/null
+++ b/recipes-devtools/rpm/rpm_git.bbappend
@@ -0,0 +1,4 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+inherit with-selinux
+PACKAGECONFIG[selinux] = "${WITH_SELINUX},${WITHOUT_SELINUX},libsemanage,"
--
2.8.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can I change the version of Yocto Project ?
On 2016年10月12日 22:05, 蔡尚義 wrote:
Hi Yocto Project:
Recently I downloaded the yocto project with the latest version
("krogoth") on my Ubuntu14.04 LTS.
But I found that Jethro version is the real version that I need to use
for BSP on APQ8053(Qualcomm chip)
So, How can I downgrade the version of yocto project to do this ?
Why not download Jethro directly?
Another question is that I found that the Desktop can not fit my
desktop monitor very well.
Maybe it was because your virtual-machine on windows.
So, how can I change the setting to let this issue disappeared ?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
