Re: [yocto] busybox udhcpd service file
Really no one any idea or hint? I could make it "dirty" but I would like to
understand where the problem is.
Am 30.09.2015 um 09:28 schrieb Lukas Böhm:
Hello,
I want to use the busybox udhcpd server in conjunction with systemd. As there is
no service file included in the recipe (v1.22.1) and no udhcpd.conf I made a
bbappend to add this. Unfortunatelly the service file is not added to the final
image but the conf-file.
My busybox_%.bbappend looks as follows:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += " \
file://udhcpd.conf \
file://udhcpd.service \
"
SYSTEMD_PACKAGES += " \
${PN}-udhcpd \
"
SYSTEMD_SERVICE_${PN}-udhcpd = "udhcpd.service"
FILES_${PN}-udhcpd += "${systemd_unitdir}/system/udhcpd.service
${sysconfdir}/udhcpd.conf"
do_install_append () {
install -d ${D}${systemd_unitdir}/system
install -d ${D}${sysconfdir}
install -m 0644 ${WORKDIR}/udhcpd.conf ${D}${sysconfdir}
install -m 0644 ${WORKDIR}/udhcpd.service
${D}${systemd_unitdir}/system/udhcpd.service
}
-
The strange thing is, that the service file is installed to
${WORKDIR}/image/lib/systemd/system but not to the final image.
Any hints how to make it will be highly appreciated.
Thanks
Lukas Böhm
--
Lukas Böhm fon: ++49 351 26996-0
iseg Spezialelektronik GmbH fax: ++49 351 26996-21
Bautzner Landstr. 23 mail: lukas.bo...@iseg-hv.de
D-01454 Radeberg OT Rossendorf web: www.iseg-hv.de
Geschäftsführer/Managing Director:
Dr. Frank Gleisberg, Dr. Joachim Pöthig
Registergericht/Lower District Court:
Amtsgericht Dresden HRB 16250
Umsatzsteuer-Identnummer / VAT Id:
DE 812 50 89 42
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged
information. If you are not the intended recipient
(or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying,
disclosure or distribution of the material in this e-mail
is strictly forbidden.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] ref-manual: document strace dependency for Swabber
image-swab class depends on "strace" package to be present in the Build Host. Document that dependency. [YOCTO #8439] Signed-off-by: Maxin B. John --- documentation/ref-manual/ref-classes.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index d87c9ff..fdee92a 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -1363,7 +1363,8 @@ tool in order to detect and log accesses to the host system during the OpenEmbedded build process. -This class is currently unmaintained. +We need to install strace package in the build host as a +dependency for this tool.This class is currently unmaintained. -- 2.4.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] gma500_gfx: Avoid inserting gma500_gfx module for certain devices
The gma500_gfx driver will match certain devices on which it causes incorrect
functionality,
we want to avoid inserting this module, basicallly blacklist it for specific
hardware,
but still allow it to work on other hardware by default; usually when we have
an already working system,
using udev rules would do the job, but since we are building it, it is
impossible to blacklist
a driver when a certain udev rule matches, since rootfs isn't writeable at this
point during boot time,
the solution is to use modprobe install, which runs a certain command instead
of inserting a matching module,
this command needs to insert the module manually afterwards and have a flag
--ignore-install
so it doesnt create an infinite loop executing itself everytime it wants to
insert the module,
busybox's modprobe doesn't provide this functionality, so a small hack had to
be used to avoid
the infite loop instead.
Signed-off-by: Alejandro Hernandez
---
meta-yocto-bsp/conf/machine/genericx86.conf| 2 ++
.../gma500-gfx-check/gma500-gfx-check.conf | 2 ++
.../gma500-gfx-check/gma500-gfx-check.sh | 11 +++
.../gma500-gfx-check/gma500-gfx-check_1.0.bb | 18 ++
4 files changed, 33 insertions(+)
create mode 100644
meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.conf
create mode 100644
meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.sh
create mode 100644
meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bb
diff --git a/meta-yocto-bsp/conf/machine/genericx86.conf
b/meta-yocto-bsp/conf/machine/genericx86.conf
index 2642cab..798b62ec 100644
--- a/meta-yocto-bsp/conf/machine/genericx86.conf
+++ b/meta-yocto-bsp/conf/machine/genericx86.conf
@@ -6,3 +6,5 @@
DEFAULTTUNE ?= "core2-32"
require conf/machine/include/tune-core2.inc
require conf/machine/include/genericx86-common.inc
+
+MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "gma500-gfx-check"
diff --git
a/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.conf
b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.conf
new file mode 100644
index 000..69f109e
--- /dev/null
+++
b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.conf
@@ -0,0 +1,2 @@
+# Mimic modprobe's install funcitonality with busybox's modprobe
+install gma500_gfx lsmod | grep gma || { gma500_gfx_check.sh || modprobe
gma500_gfx; }
diff --git
a/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.sh
b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.sh
new file mode 100644
index 000..0c7b3aa
--- /dev/null
+++
b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check/gma500-gfx-check.sh
@@ -0,0 +1,11 @@
+#!/bin/sh
+
+# Check for devices we wish to avoid gma500_gfx for
+DEVICES="0x8119 0x4108"
+for DEVICE in $DEVICES; do
+if udevadm trigger --subsystem-match=pci --verbose
--attr-match=device=$DEVICE | grep "pci" >> /dev/null ; then
+echo "Found $DEVICE, avoiding gma500_gfx module" >> /dev/kmsg;
+exit 0
+fi
+done
+exit 1
diff --git
a/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bb
b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bb
new file mode 100644
index 000..00680de
--- /dev/null
+++ b/meta-yocto-bsp/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bb
@@ -0,0 +1,18 @@
+SUMMARY = "Intel gma500_gfx fix for certain hardware"
+DESCRIPTION = "Avoid inserting gma500_gfx module for certain hardware devices."
+LICENSE="GPLv2"
+LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
+
+SRC_URI = "file://gma500-gfx-check.conf \
+ file://gma500-gfx-check.sh "
+
+do_install(){
+install -d ${D}${sysconfdir}/modprobe.d/
+install -m 755 ${WORKDIR}/gma500-gfx-check.sh
${D}${sysconfdir}/modprobe.d/gma500-gfx-check.sh
+install -m 644 ${WORKDIR}/gma500-gfx-check.conf
${D}${sysconfdir}/modprobe.d/gma500-gfx-check.conf
+}
+
+FILES_${PN}="${sysconfdir}/modprobe.d/gma500-gfx-check.conf \
+ ${sysconfdir}/modprobe.d/gma500-gfx-check.sh"
+
+COMPATIBLE_MACHINE = "genericx86"
--
1.8.4.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] busybox udhcpd service file
On Wed, Sep 30, 2015 at 12:28 AM, Lukas Böhm wrote:
> Hello,
>
> I want to use the busybox udhcpd server in conjunction with systemd. As
> there is no service file included in the recipe (v1.22.1) and no udhcpd.conf
> I made a bbappend to add this. Unfortunatelly the service file is not added
> to the final image but the conf-file.
> My busybox_%.bbappend looks as follows:
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> SRC_URI += " \
> file://udhcpd.conf \
> file://udhcpd.service \
> "
> SYSTEMD_PACKAGES += " \
> ${PN}-udhcpd \
> "
> SYSTEMD_SERVICE_${PN}-udhcpd = "udhcpd.service"
> FILES_${PN}-udhcpd += "${systemd_unitdir}/system/udhcpd.service
> ${sysconfdir}/udhcpd.conf"
>
> do_install_append () {
> install -d ${D}${systemd_unitdir}/system
> install -d ${D}${sysconfdir}
> install -m 0644 ${WORKDIR}/udhcpd.conf ${D}${sysconfdir}
> install -m 0644 ${WORKDIR}/udhcpd.service
> ${D}${systemd_unitdir}/system/udhcpd.service
> }
> -
> The strange thing is, that the service file is installed to
> ${WORKDIR}/image/lib/systemd/system but not to the final image.
>
> Any hints how to make it will be highly appreciated.
Did you inherit systemd ?
> Thanks
>
> Lukas Böhm
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] busybox udhcpd service file
I would suggest you to setup build history and look files installed by
busybox package.
2015-10-05 13:13 GMT-03:00 Khem Raj :
> On Wed, Sep 30, 2015 at 12:28 AM, Lukas Böhm wrote:
>> Hello,
>>
>> I want to use the busybox udhcpd server in conjunction with systemd. As
>> there is no service file included in the recipe (v1.22.1) and no udhcpd.conf
>> I made a bbappend to add this. Unfortunatelly the service file is not added
>> to the final image but the conf-file.
>> My busybox_%.bbappend looks as follows:
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> SRC_URI += " \
>> file://udhcpd.conf \
>> file://udhcpd.service \
>> "
I don't really understand what you said. The udhcpd.conf file was
installed on image but not
the udhcpd.service file? Is that right? Can you check if busybox
already ships udhcpd.conf file?
>> SYSTEMD_PACKAGES += " \
>> ${PN}-udhcpd \
>> "
>> SYSTEMD_SERVICE_${PN}-udhcpd = "udhcpd.service"
>> FILES_${PN}-udhcpd += "${systemd_unitdir}/system/udhcpd.service
>> ${sysconfdir}/udhcpd.conf"
>>
>> do_install_append () {
>> install -d ${D}${systemd_unitdir}/system
>> install -d ${D}${sysconfdir}
>> install -m 0644 ${WORKDIR}/udhcpd.conf ${D}${sysconfdir}
>> install -m 0644 ${WORKDIR}/udhcpd.service
>> ${D}${systemd_unitdir}/system/udhcpd.service
>> }
>> -
>> The strange thing is, that the service file is installed to
>> ${WORKDIR}/image/lib/systemd/system but not to the final image.
>>
>> Any hints how to make it will be highly appreciated.
>
> Did you inherit systemd ?
>
>
>> Thanks
>>
>> Lukas Böhm
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Cheers,
--
"Do or do not. There is no try"
Yoda Master
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Flashing Yocto to SOM?
Hi,
I'm trying to flash Yocto Dizzy (core-image-minimal built with BitBake)
onto a LogicPD DM3730 / AM3730 Torpedo + Wireless SOM using the following
commands at the U-Boot prompt:
# nand erase.chip
# env default -f
# setenv loadaddr 0x8100
# setenv ramdiskaddr 0x8200
# setenv kernel_nand_offset 0x0028
# setenv kernel_nand_size 0x0040
# setenv ramdisk_nand_offset 0x0068
# setenv ramdisk_nand_size 0x00dd8680
# setenv kernel_location nand
# setenv rootfs_location nand
# setenv rootfs_type ramdisk
# saveenv
# mmc init
# mw.l ${loadaddr} 0x 0x40
# fatload mmc 0 ${loadaddr} mlo
# nandecc hw
# nand write ${loadaddr} 0x 0x0002
# nand write ${loadaddr} 0x0002 0x0002
# nand write ${loadaddr} 0x0004 0x0002
# nand write ${loadaddr} 0x0006 0x0002
# mw.l ${loadaddr} 0x 0x40
# fatload mmc 0 ${loadaddr} u-boot.bin
# nandecc sw
# nand write.i ${loadaddr} 0x0008 0x0008
# mw.l ${loadaddr} 0x 0x40
# fatload mmc 0 ${loadaddr} uImage
# nand write.i ${loadaddr} ${kernel_nand_offset} ${kernel_nand_size}
# mw.l ${loadaddr} 0x 0x40
# fatload mmc 0 ${loadaddr} rootfs.ext2.gz.u-boot
# nand write.i ${loadaddr} ${ramdisk_nand_offset} ${ramdisk_nand_size}
The source files I'm using in my boot partition are the MLO, u-boot.bin,
rootfs.ext2.gz.u-boot, uImage, and u-boot.img. I am able to burn all the
necessary files onto the SOM, but when I complete the steps and power
cycle, I get:
U-Boot SPL 2012.07-dirty (Sep 30 2015 - 17:31:44)
Board: DM37xx Torpedo
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
...
mkimage signature not found - ih_magic = ea14
...
Error: Bad compare! failed
Error: Bad compare! failed
...
I've done a good amount of research online and some people say that it's an
issue with the nandecc setting, but my only options in U-Boot are hw
(hardware) and sw (software) ecc algorithms. Just curious if anyone could
identify my errors or possibly point me in the direction of good
documentation?
Thanks!
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Oct. 6, 2015 8:00 AM US Pacific Time
Tuesday, Oct. 6, 2015 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features * Opens - 10 min * Team Sharing - 10 min We encourage people attending the meeting to logon the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference Details: Company: WIND RIVER SYS Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 For International numbers see: https://www.yoctoproject.org/tools-resources/community/monthly-technical-call Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-docs][PATCH 0/1] new PTEST_RUN_SCRIPT_PATH
> New PTEST_RUN_SCRIPT_PATH allows recipes to override the default > location of the run-ptest script. Please disregard, open-embedded was patched in a simpler way. Ian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
