[linux-yocto] [PATCH] edac: Drop CONFIG_EDAC_MM_EDAC and add dependency

[Hongzhi.Song]

CONFIG_EDAC depends on RAS.
CONFIG_EDAC_MM_EDAC was removed by kernel.[Commit: e3c4ff6d8c9]

Signed-off-by: Hongzhi.Song 
---
 features/edac/edac.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/features/edac/edac.cfg b/features/edac/edac.cfg
index ad9c98f..e7be14e 100644
--- a/features/edac/edac.cfg
+++ b/features/edac/edac.cfg
@@ -11,6 +11,6 @@
 #
 #.
 
+CONFIG_RAS=y
 CONFIG_EDAC=y
-CONFIG_EDAC_MM_EDAC=m
 CONFIG_EDAC_DEBUG=y
-- 
2.8.1

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

[linux-yocto] [PATCH] kernel-cache: edac: correct config

[Hongzhi.Song]

Please merge to master/v4.19~v4.14

Hongzhi.Song (1):
  edac: Drop CONFIG_EDAC_MM_EDAC and add dependency

 features/edac/edac.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.8.1

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

Re: [yocto] [OE-core] OEDAM @ SCaLE 2019

[Trevor Woerner]

Hi Jon,

On Thu, Nov 1, 2018 at 3:56 PM Jon Mason  wrote:

> I am planning on being at SCaLE (assuming the OEDEM happens there).
>
> Many corporate travel budgets are tied to presenting at conferences.
> So, if we could somehow get a track there (which might be too late in
> the game to do now), then we might be able to get enough people
> present to make it happen and pull in others whose budget is more
> flexible.
>

As it turns out, I'll be organising the YP/OE Miniconf that will most
likely be run on the Sunday. I was going to send out a separate email
discussing the Miniconf, but I guess now is as good a time as any :-)

While it's true that the CFP has closed for SCaLE, I plan to open my own
CFP specifically for the Miniconf, and I don't plan to close it until
closer to the conference itself. I want to encourage people to give talks
about current things, as such, having a CFP close this early wouldn't do.

We haven't decided on a format for the Miniconf, exactly, if we have
traditional talks, we'll have 6 sessions (2 before lunch, 4 after). But
depending on interest and what sort of proposals we get, we might do some
longer, some shorter talks.

 I hope this helps. Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Where to look when literally nothing happens?

[Erik Hoogeveen]

Thank you for the tip Outback.

Since sending my email I’ve actually tried exactly that, I built a fresh image 
with target raspberrypi-cm3.
And the funny thing is, it does the exact same thing. It works fine on the 
regular pi, and nothing with my cm3 lite.

My current suspicion is that this is related to u-boot somehow. I need u-boot 
because I’d like to use Mender for the OTA updating of my devices.

I’m going to see if I can get a stripped down version with just u-boot but 
without Mender going first. Then maybe I can take it from there.

In the mean time all tips and tricks you could give me are very much 
appreciated.

Kind regards,
Erik
On 1 Nov 2018, 12:51 +0100, Outback Dingo , wrote:
On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen
 wrote:

Hello,

I’m rather new to embedded software and Yocto. I hope this is the right place 
to ask. If not I’d appreciate it if someone could point me the right way to do 
so.

I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and 
doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over 
serial console I can log in and do things.
But the ultimate target is to run this image on my own board which is built 
around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve 
used so far) works fine on both boards without modification I assumed that this 
would be the case as well with this image I made myself. But it turns out I was 
wrong.

When I take the image from the build and stick it in my compute module board, 
literally nothing happens. The boot sequence doesn’t seem to even begin, I get 
nothing on the serial console, and none of the peripherals like the ethernet 
ever come to life either.

And since nothing happens I really have no idea where to look for a solution. 
I’m guessing this is a bit of a noob issue? It would be great if someone could 
point me in a direction to look at.

you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit

i believe the compute module 3 target is raspberrypi-cm3

you could pretty muuchh do a diff uunder the meta-raspberryypi ffor
the differences in whats built


Kind regards,
Erik Hoogeveen.
--
___
yocto mailing list
yocto@yoctoproject.org
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyoctodata=02%7C01%7C%7C0bd7e7fee835429b62b808d63ff0595e%7C84df9e7fe9f640afb435%7C1%7C0%7C636766698851268696sdata=7aiUvFhvNbWvMN8VMy%2BnqlUh9VCAQpnCTMohVpYnmKs%3Dreserved=0
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Removing hostapd init file

[Darcy Watkins]

Hi,

I have tried schemes like these and found that although they appear to work 
during rootfs generation, it can result in RPM transaction failures if you try 
to perform in-place upgrades using RPMs.  The post install scriptlets can fail 
as they attempt to run the update-rc.d command, passing bad (or missing) parms.

Fortunately for this particular case there is a hook variable that is used to 
leep sysvinit out of the way when using system (or other alternative).  I fixed 
it by adding the following to my bbappend…

  INHIBIT_UPDATERCD_BBCLASS = “1”



Regards,

Darcy

Darcy Watkins ::  Senior Staff Engineer, Firmware

SIERRA WIRELESS
Direct  +1 604 233 7989   ::  Fax  +1 604 231 1109  ::  Main  +1 604 231 1100
13811 Wireless Way  :: Richmond, BC Canada V6V 3A4
[P2]
dwatk...@sierrawireless.com :: 
www.sierrawireless.com

From: yocto-boun...@yoctoproject.org  On Behalf 
Of Joshua Watt
Sent: November-01-18 10:39 AM
To: Kristupas Savickas ; yocto@yoctoproject.org
Subject: Re: [yocto] Removing hostapd init file

On Tue, 2018-10-23 at 09:03 +0300, Kristupas Savickas wrote:

Greetings,

I'm trying to remove the hostapd init file as I'll handle startup of it on my 
own. I've created a .bbappend file in my layer to do this:

do_install_append() {
rm -rf ${D}${sysconfdir}/init.d
}

However, this results in a compilation warning when building my image and the 
ipk-postinst is still being run on my target:

WARNING: tlt-image-1.0-r0 do_rootfs: hostapd.postinst returned 1, marking as 
unpacked only, configuration required on target.
WARNING: tlt-image-1.0-r0 do_rootfs: Intentionally failing postinstall 
scriptlets of ['hostapd'] to defer them to first boot is deprecated. Please 
place them into pkg_postinst_ontarget_${PN} ().
If deferring to first boot wasn't the intent, then scriptlet failure may mean 
an issue in the recipe, or a regression elsewhere.
Details of the failure are in 
/home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/temp/log.do_rootfs.
WARNING: tlt-image-1.0-r0 do_rootfs: [log_check] tlt-image: found 1 warning 
message in the logfile:
[log_check] WARNING: Intentionally failing postinstall scriptlets of 
['hostapd'] to defer them to first boot is deprecated. Please place them into 
pkg_postinst_ontarget_${PN} ().



I tried setting INITSCRIPT_NAME to "" in my .bbappend, but it fails with an 
error during do_rootfs task of my image:
cat 
build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/temp/log.do_rootfs.24919
 | grep hostapd
NOTE: Found hostapd-dbg_2.6-r0_armv7ahf-neon.ipk in Packages, but mtime differs 
- re-reading
Found hostapd-dev_2.6-r0_armv7ahf-neon.ipk in Packages, but mtime differs - 
re-reading
Found hostapd_2.6-r0_armv7ahf-neon.ipk in Packages, but mtime differs - 
re-reading
NOTE: Installing the following packages: android-system-core-adbd 
android-system-core-liblog android-system-core-usb ap6212 avlcommd base-files 
base-passwd boot-config config-backup curl dnsmasq dropbear ethtool eventslog 
factory-restore firewall3 fsl-rc-local gps-control gps-utils gpsd gpsd-conf 
gsmd hostapd iio-utils iiod iproute2 iptables iputils iw kernel-modules 
libcutils0 libglib-2.0-0 libnl-3-200 libstdc++6 libtlt-lua libxml2 
lsm6dsl-rebind lsqlite3 luci lucihttp mnf-info motion-monitor mtd-utils-ubifs 
netifd openssl os-release packagegroup-core-boot perl ppp preinit procd qmuxd 
recgend rpcd run-postinsts shadow sms-utilities sqlite3 storage sysntpd system 
sysup tlt-base-files tlt-connection-manager tlt-eventslog-lua tzdata ubus 
uhttpd update-rc.d ustream-ssl
NOTE: 
/home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg
 --volatile-cache -f 
/home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/opkg.conf
 -t 
/home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/temp/ipktemp/
 -o 
/home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/rootfs
  --force_postinstall --prefer-arch-to-version --no-install-recommends  
--force-overwrite install android-system-core-adbd android-system-core-liblog 
android-system-core-usb ap6212 avlcommd base-files base-passwd boot-config 
config-backup curl dnsmasq dropbear ethtool eventslog factory-restore firewall3 
fsl-rc-local gps-control gps-utils gpsd gpsd-conf gsmd hostapd iio-utils iiod 
iproute2 iptables iputils iw kernel-modules libcutils0 libglib-2.0-0 
libnl-3-200 libstdc++6 libtlt-lua libxml2 lsm6dsl-rebind lsqlite3 luci lucihttp 
mnf-info motion-monitor mtd-utils-ubifs netifd openssl os-release 
packagegroup-core-boot perl ppp preinit procd qmuxd recgend rpcd run-postinsts 
shadow sms-utilities sqlite3 storage sysntpd system sysup 

Re: [yocto] [OE-core] OEDAM @ SCaLE 2019

[Jon Mason]

On Thu, Nov 1, 2018 at 10:04 AM Trevor Woerner  wrote:
>
> Hello Fellow YP/OE Enthusiasts!
>
> There were discussions at our recent OEDEM regarding:
> - our next developers meeting
> - SCaLE 2019
> - expanding/adding to the YP/OE presence at conferences (i.e. our own
>   miniconf?)
>
> Please see time indices: 12:13 and 16:45
> https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk
>
> Unfortunately, although lots of opinions were expressed, nothing concrete was
> decided. Many people pointed out that their travel budgets are already
> strained or maxed out, so adding another conference would be difficult if not
> impossible. It's unclear how many "core" YP/OE people might show up at next
> year's SCaLE. Also, given that this year's ELC scheduling hiccup is a one-off,
> maybe it doesn't make as much sense to put in all the work required to run an
> OEDAM at SCaLE if it's only ever going to happen once. Therefore I think I can
> safely say the organizing committee for YP/OE Things at SCaLE 2019 is leaning
> towards not running an OEDAM.
>
> It's not too late to change our plans. If a large number of core people reply
> to this email saying they want and OEDAM in March and will be available in
> Pasadena, then we could accommodate it. It's just that we didn't leave
> Edinburgh with the feeling that an OEDAM at SCaLE was feasible. Also, at this
> point SCaLE isn't on the radars of many of the core YP/OE people, and
> currently the conference tends to attract users rather than developers (or so
> is my impression).
>
> Thoughts?

I am planning on being at SCaLE (assuming the OEDEM happens there).

Many corporate travel budgets are tied to presenting at conferences.
So, if we could somehow get a track there (which might be too late in
the game to do now), then we might be able to get enough people
present to make it happen and pull in others whose budget is more
flexible.

Thanks,
Jon

>
> Best regards,
> Trevor
> --
> ___
> Openembedded-core mailing list
> openembedded-c...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] nginx: module: add ngx-http-auth-pam-module

[Kosta Zertsekel]

Guys,

I sent the commit to discuss if this is the right way to include NGINX
module in the customization layer.
It actully compiles OK and works in run-time on target.
But, again, I'm looking for the **right** way to do it.
I'll be happy to get some feedback.

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

[yocto] [PATCH] nginx: module: add ngx-http-auth-pam-module

[Kosta Zertsekel]

NGINX support adding third-party modules.
These modules are created and maintained by members of the NGINX community.
NGINX, Inc. provides support for some of these modules.

Each module is developed as a separate git project, but can be compiled
only as part of NGINX compilation using `--add-module` parameter.

Signed-off-by: Kosta Zertsekel 
---
 recipes-httpd/nginx/nginx_%.bbappend  |  5 
 .../ngx-http-auth-pam-module_git.bb   | 24 +++
 2 files changed, 29 insertions(+)
 create mode 100644 recipes-httpd/nginx/nginx_%.bbappend
 create mode 100644 
recipes-ngx-http-auth-pam-module/ngx-http-auth-pam-module/ngx-http-auth-pam-module_git.bb

diff --git a/recipes-httpd/nginx/nginx_%.bbappend 
b/recipes-httpd/nginx/nginx_%.bbappend
new file mode 100644
index 000..d3ed1bf
--- /dev/null
+++ b/recipes-httpd/nginx/nginx_%.bbappend
@@ -0,0 +1,5 @@
+DEPENDS += "ngx-http-auth-pam-module"
+
+EXTRA_OECONF += " \
+--add-module=${STAGING_DIR_TARGET}/ngx-http-auth-pam-module \
+"
diff --git 
a/recipes-ngx-http-auth-pam-module/ngx-http-auth-pam-module/ngx-http-auth-pam-module_git.bb
 
b/recipes-ngx-http-auth-pam-module/ngx-http-auth-pam-module/ngx-http-auth-pam-module_git.bb
new file mode 100644
index 000..8f13c3f
--- /dev/null
+++ 
b/recipes-ngx-http-auth-pam-module/ngx-http-auth-pam-module/ngx-http-auth-pam-module_git.bb
@@ -0,0 +1,24 @@
+LICENSE = "Unknown"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=1eccc8f95bc958cb0e1569c433286a22"
+
+SRC_URI = "git://github.com/sto/ngx_http_auth_pam_module;protocol=https"
+
+PV = "1.5+git${SRCPV}"
+SRCREV = "d9286fc7b52e1a3584da2cb20423f912ec99169f"
+
+S = "${WORKDIR}/git"
+
+SYSROOT_DIRS += "/${PN}"
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+
+# Nginx module is compiled as part of nginx build using --add-module,
+# hence, just copy the sources here to be picked up by nginx later.
+do_install () {
+   cd ${S}
+   git checkout-index -a --prefix=${D}/${PN}/
+   cd -
+}
+
+FILES_${PN} = "${PN}/*"
-- 
2.17.1

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

Re: [yocto] Removing hostapd init file

[Joshua Watt]

On Tue, 2018-10-23 at 09:03 +0300, Kristupas Savickas wrote:
> Greetings,
> I'm trying to remove the hostapd init file as I'll handle startup
>   of it on my own. I've created a .bbappend file in my layer to
> do
>   this:
> 
> >   do_install_append() {
> > 
> > rm -rf ${D}${sysconfdir}/init.d
> > 
> > }
> > 
> >   
> > 
> 
> However, this results in a compilation warning when building my
>   image and the ipk-postinst is still being run on my target:
> 
> >   WARNING: tlt-image-1.0-r0 do_rootfs: hostapd.postinst
> > returned
> > 1, marking as unpacked only, configuration required on
> > target.
> > 
> > WARNING: tlt-image-1.0-r0 do_rootfs: Intentionally failing
> > postinstall scriptlets of ['hostapd'] to defer them to
> > first
> > boot is deprecated. Please place them into
> > pkg_postinst_ontarget_${PN} ().
> > 
> > If deferring to first boot wasn't the intent, then
> > scriptlet
> > failure may mean an issue in the recipe, or a regression
> > elsewhere.
> > 
> > Details of the failure are in
> > /home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-
> > glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-
> > r0/temp/log.do_rootfs.
> > 
> > WARNING: tlt-image-1.0-r0 do_rootfs: [log_check] tlt-image:
> > found 1 warning message in the logfile:
> > 
> > [log_check] WARNING: Intentionally failing postinstall
> > scriptlets of ['hostapd'] to defer them to first boot is
> > deprecated. Please place them into
> > pkg_postinst_ontarget_${PN}
> > ().
> >   
> > 
> >   
> > 
> 
> I tried setting INITSCRIPT_NAME to "" in my .bbappend, but it
>   fails with an error during do_rootfs task of my image:
> 
> > cat
> > build/tmp-glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-
> > r0/temp/log.do_rootfs.24919
> >   | grep hostapd
> > 
> >   NOTE: Found hostapd-dbg_2.6-r0_armv7ahf-neon.ipk in Packages,
> > but
> >   mtime differs - re-reading
> > 
> >   Found hostapd-dev_2.6-r0_armv7ahf-neon.ipk in Packages, but
> > mtime
> >   differs - re-reading
> > 
> >   Found hostapd_2.6-r0_armv7ahf-neon.ipk in Packages, but mtime
> >   differs - re-reading
> > 
> >   NOTE: Installing the following packages: android-system-core-
> > adbd
> >   android-system-core-liblog android-system-core-usb ap6212
> > avlcommd
> >   base-files base-passwd boot-config config-backup curl dnsmasq
> >   dropbear ethtool eventslog factory-restore firewall3 fsl-rc-
> > local
> >   gps-control gps-utils gpsd gpsd-conf gsmd hostapd iio-utils
> > iiod
> >   iproute2 iptables iputils iw kernel-modules libcutils0
> >   libglib-2.0-0 libnl-3-200 libstdc++6 libtlt-lua libxml2
> >   lsm6dsl-rebind lsqlite3 luci lucihttp mnf-info motion-monitor
> >   mtd-utils-ubifs netifd openssl os-release packagegroup-core-
> > boot
> >   perl ppp preinit procd qmuxd recgend rpcd run-postinsts
> > shadow
> >   sms-utilities sqlite3 storage sysntpd system sysup tlt-base-
> > files
> >   tlt-connection-manager tlt-eventslog-lua tzdata ubus uhttpd
> >   update-rc.d ustream-ssl
> > 
> >   NOTE:
> > /home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-
> > glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/recipe-sysroot-
> > native/usr/bin/opkg
> >   --volatile-cache -f
> > /home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-
> > glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/opkg.conf
> >   -t
> > /home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-
> > glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/temp/ipktemp/
> >   -o
> > /home/kristupas/projects/fml-linux-sdk-qtel/oe-core/build/tmp-
> > glibc/work/fml001-oe-linux-gnueabi/tlt-image/1.0-r0/rootfs 
> >   --force_postinstall --prefer-arch-to-version
> >   --no-install-recommends  --force-overwrite install
> >   android-system-core-adbd android-system-core-liblog
> >   android-system-core-usb ap6212 avlcommd base-files base-
> > passwd
> >   boot-config config-backup curl dnsmasq dropbear ethtool
> > eventslog
> >   factory-restore firewall3 fsl-rc-local gps-control gps-utils
> > gpsd
> >   gpsd-conf gsmd hostapd iio-utils iiod iproute2 iptables
> > iputils iw
> >   kernel-modules libcutils0 libglib-2.0-0 libnl-3-200
> > libstdc++6
> >   libtlt-lua libxml2 lsm6dsl-rebind lsqlite3 luci lucihttp mnf-
> > info
> >   motion-monitor mtd-utils-ubifs netifd openssl os-release
> >   packagegroup-core-boot perl ppp preinit procd qmuxd recgend
> > rpcd
> >   run-postinsts shadow sms-utilities sqlite3 storage sysntpd
> > system
> >   sysup tlt-base-files tlt-connection-manager tlt-eventslog-lua
> >   tzdata ubus uhttpd update-rc.d ustream-ssl
> > 
> >   ERROR: Unable to install packages. Command
> > 

Re: [yocto] [OE-core] OEDAM @ SCaLE 2019

[Trevor Woerner]

On Thu, Nov 1, 2018 at 3:32 PM akuster808  wrote:

> Trevor,
>
>
> On 11/1/18 7:04 AM, Trevor Woerner wrote:
> > Please see time indices: 12:13 and 16:45
> >
> https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk
>
> Could you please give us a day's notice the next time so we can properly
> set the perms for our minutes.
>
>
Will do, sorry!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] OEDAM @ SCaLE 2019

[akuster808]

Trevor,


On 11/1/18 7:04 AM, Trevor Woerner wrote:
> Hello Fellow YP/OE Enthusiasts!
>
> There were discussions at our recent OEDEM regarding:
> - our next developers meeting
> - SCaLE 2019
> - expanding/adding to the YP/OE presence at conferences (i.e. our own
>   miniconf?)
>
> Please see time indices: 12:13 and 16:45
> https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk

Could you please give us a day's notice the next time so we can properly
set the perms for our minutes.

- armin

>
> Unfortunately, although lots of opinions were expressed, nothing concrete was
> decided. Many people pointed out that their travel budgets are already
> strained or maxed out, so adding another conference would be difficult if not
> impossible. It's unclear how many "core" YP/OE people might show up at next
> year's SCaLE. Also, given that this year's ELC scheduling hiccup is a one-off,
> maybe it doesn't make as much sense to put in all the work required to run an
> OEDAM at SCaLE if it's only ever going to happen once. Therefore I think I can
> safely say the organizing committee for YP/OE Things at SCaLE 2019 is leaning
> towards not running an OEDAM.
>
> It's not too late to change our plans. If a large number of core people reply
> to this email saying they want and OEDAM in March and will be available in
> Pasadena, then we could accommodate it. It's just that we didn't leave
> Edinburgh with the feeling that an OEDAM at SCaLE was feasible. Also, at this
> point SCaLE isn't on the radars of many of the core YP/OE people, and
> currently the conference tends to attract users rather than developers (or so
> is my impression).
>
> Thoughts?
>
> Best regards,
>   Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] OEDAM @ SCaLE 2019

[Trevor Woerner]

Hello Fellow YP/OE Enthusiasts!

There were discussions at our recent OEDEM regarding:
- our next developers meeting
- SCaLE 2019
- expanding/adding to the YP/OE presence at conferences (i.e. our own
  miniconf?)

Please see time indices: 12:13 and 16:45
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk

Unfortunately, although lots of opinions were expressed, nothing concrete was
decided. Many people pointed out that their travel budgets are already
strained or maxed out, so adding another conference would be difficult if not
impossible. It's unclear how many "core" YP/OE people might show up at next
year's SCaLE. Also, given that this year's ELC scheduling hiccup is a one-off,
maybe it doesn't make as much sense to put in all the work required to run an
OEDAM at SCaLE if it's only ever going to happen once. Therefore I think I can
safely say the organizing committee for YP/OE Things at SCaLE 2019 is leaning
towards not running an OEDAM.

It's not too late to change our plans. If a large number of core people reply
to this email saying they want and OEDAM in March and will be available in
Pasadena, then we could accommodate it. It's just that we didn't leave
Edinburgh with the feeling that an OEDAM at SCaLE was feasible. Also, at this
point SCaLE isn't on the radars of many of the core YP/OE people, and
currently the conference tends to attract users rather than developers (or so
is my impression).

Thoughts?

Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Where to look when literally nothing happens?

[Outback Dingo]

On Thu, Nov 1, 2018 at 6:50 PM Outback Dingo  wrote:
>
> On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen
>  wrote:
> >
> > Hello,
> >
> > I’m rather new to embedded software and Yocto. I hope this is the right 
> > place to ask. If not I’d appreciate it if someone could point me the right 
> > way to do so.
> >
> > I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting 
> > and doing things on a regular plain vanilla Raspberry pi 3 board. It boots 
> > and over serial console I can log in and do things.
> > But the ultimate target is to run this image on my own board which is built 
> > around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ 
> > I’ve used so far) works fine on both boards without modification I assumed 
> > that this would be the case as well with this image I made myself. But it 
> > turns out I was wrong.
> >
> > When I take the image from the build and stick it in my compute module 
> > board, literally nothing happens. The boot sequence doesn’t seem to even 
> > begin, I get nothing on the serial console, and none of the peripherals 
> > like the ethernet ever come to life either.
> >
> > And since nothing happens I really have no idea where to look for a 
> > solution. I’m guessing this is a bit of a noob issue? It would be great if 
> > someone could point me in a direction to look at.
>
> you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit
>
> i believe the compute module 3 target is raspberrypi-cm3
>
> you could pretty muuchh do a diff uunder the meta-raspberryypi ffor
> the differences in whats built


Yupp see
The choices for MACHINE are

raspberrypi (BCM2835)
raspberrypi0 (BCM2835)
raspberrypi0-wifi (BCM2835)
raspberrypi2 (BCM2836 or BCM2837 v1.2+)
raspberrypi3 (BCM2837)
raspberrypi-cm (BCM2835)
raspberrypi-cm3 (BCM2837)


see https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html

its a good read on PIs


>
> >
> > Kind regards,
> > Erik Hoogeveen.
> > --
> > ___
> > 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] Where to look when literally nothing happens?

[Outback Dingo]

On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen
 wrote:
>
> Hello,
>
> I’m rather new to embedded software and Yocto. I hope this is the right place 
> to ask. If not I’d appreciate it if someone could point me the right way to 
> do so.
>
> I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting 
> and doing things on a regular plain vanilla Raspberry pi 3 board. It boots 
> and over serial console I can log in and do things.
> But the ultimate target is to run this image on my own board which is built 
> around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ 
> I’ve used so far) works fine on both boards without modification I assumed 
> that this would be the case as well with this image I made myself. But it 
> turns out I was wrong.
>
> When I take the image from the build and stick it in my compute module board, 
> literally nothing happens. The boot sequence doesn’t seem to even begin, I 
> get nothing on the serial console, and none of the peripherals like the 
> ethernet ever come to life either.
>
> And since nothing happens I really have no idea where to look for a solution. 
> I’m guessing this is a bit of a noob issue? It would be great if someone 
> could point me in a direction to look at.

you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit

i believe the compute module 3 target is raspberrypi-cm3

you could pretty muuchh do a diff uunder the meta-raspberryypi ffor
the differences in whats built

>
> Kind regards,
> Erik Hoogeveen.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Where to look when literally nothing happens?

[Erik Hoogeveen]

Hello,

I’m rather new to embedded software and Yocto. I hope this is the right place 
to ask. If not I’d appreciate it if someone could point me the right way to do 
so.

I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and 
doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over 
serial console I can log in and do things.
But the ultimate target is to run this image on my own board which is built 
around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve 
used so far) works fine on both boards without modification I assumed that this 
would be the case as well with this image I made myself. But it turns out I was 
wrong.

When I take the image from the build and stick it in my compute module board, 
literally nothing happens. The boot sequence doesn’t seem to even begin, I get 
nothing on the serial console, and none of the peripherals like the ethernet 
ever come to life either.

And since nothing happens I really have no idea where to look for a solution. 
I’m guessing this is a bit of a noob issue? It would be great if someone could 
point me in a direction to look at.

Kind regards,
Erik Hoogeveen.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Removing hostapd init file

[Uwe Geuder]

On Tue, Oct 23, 2018 at 9:14 AM Kristupas Savickas 
kristupas.savickas-at-teltonika.lt wrote:
>
> Greetings,
>
> I'm trying to remove the hostapd init file as I'll handle startup of it on my 
> own. I've created a .bbappend file in my layer to do this:
>
> do_install_append() {
> rm -rf ${D}${sysconfdir}/init.d
> }
>
> However, this results in a compilation warning when building my image
> and the ipk-postinst is still being run on my target:
[...]
> I tried setting INITSCRIPT_NAME to "" in my .bbappend, but it fails
> with an error during do_rootfs task of my image:
[...]

I guess the problem is that the recipe inherits update-rc.d class and
that class wants to work with the init script. Unfortunately
uninheriting a class in a bbappend is not possible AFAIK. I am not
familiar with the details of the class whether there is a way to tell it
to do nothing.
 
> Any pointers of how I could accomplish my goal?
>

What about 

  do_install_append() {
  (echo "#!/bin/sh" ; echo true) > ${D}${sysconfdir}/init.d/hostapd
  }


Just guessing. Untested and I have not worked with sysv init for
years... Maybe update-rc.d requires the typcial comment section at the
beginning. If so you just add it. 

Or actually if update-rc.d refers to the comment section in the
beginning of the script you could add a patch that changes the
Default-Start: value to empty (or some runlevel you do not use).

Regards,

Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder at neuroeventlabs.com (Bot check: fix one obvious typo)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto