[linux-yocto] [PATCH 2/2] pwm: lpss: Prevent on_time_div overflow on lower frequencies

[eric . ernst]

From: Mika Westerberg 

If duty_ns is large enough multiplying it by 255 overflows and results
wrong duty cycle value being programmed. For example with 10ms duty when
period is 20ms (50%) we get

  255 * 1000 / 2000 = -87

because 255 * 1000 overlows int. Whereas correct value should be

  255 * 1000 / 2000 = 127

Fix this by using unsigned long long as type for on_time_div and changing
integer literals to use proper type annotation.

Signed-off-by: Mika Westerberg 
---
 drivers/pwm/pwm-lpss.c | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/pwm/pwm-lpss.c b/drivers/pwm/pwm-lpss.c
index 98dc8b80b79d..be4658b42882 100644
--- a/drivers/pwm/pwm-lpss.c
+++ b/drivers/pwm/pwm-lpss.c
@@ -91,7 +91,7 @@ static int pwm_lpss_config(struct pwm_chip *chip, struct 
pwm_device *pwm,
   int duty_ns, int period_ns)
 {
struct pwm_lpss_chip *lpwm = to_lpwm(chip);
-   u8 on_time_div;
+   unsigned long long on_time_div;
unsigned long c, base_unit_range;
unsigned long long base_unit, freq = NSEC_PER_SEC;
u32 ctrl;
@@ -113,7 +113,9 @@ static int pwm_lpss_config(struct pwm_chip *chip, struct 
pwm_device *pwm,
 
if (duty_ns <= 0)
duty_ns = 1;
-   on_time_div = 255 - (255 * duty_ns / period_ns);
+   on_time_div = 255ULL * duty_ns;
+   do_div(on_time_div, period_ns);
+   on_time_div = 255ULL - on_time_div;
 
pm_runtime_get_sync(chip->dev);
 
-- 
1.9.1

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

[linux-yocto] [PATCH 0/2] pwm backports

[eric . ernst]

From: Eric Ernst 

Attached are a couple of patches which I pulled from Mika Westerberg's pwm-4.4 
branch.
These are required to correct pwm behavior on the Broxton GT platform

Dan O'Donovan (1):
  pwm: lpss: fix base_unit calculation for PWM frequency

Mika Westerberg (1):
  pwm: lpss: Prevent on_time_div overflow on lower frequencies

 drivers/pwm/pwm-lpss.c | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

-- 
1.9.1

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

[linux-yocto] [PULL REQUEST] MEI drivers updates to linux-yocto-4.4

[Winkler, Tomas]

Please pull the upstream mei driver changes for linux-yocto-4.4 
This can merged ether standard/base or standard/intel/base 


The following changes since commit c49ed01a7e4c4fe9bfe4a4548480afd27d51088d:
Merge branch 'standard/base' into standard/intel/base (2016-07-05 11:00:40 
-0400)
are available in the git repository at:

  https://github.com/tomasbw/linux-yocto-4.4.git standard/intel/base-mei

for you to fetch changes up to d2de5bb3caeaca91022a01d2d86caaba7a15e21b:

  mei: don't use wake_up_interruptible for wr_ctrl (2016-07-07 13:40:16 +0300)


Alexander Usyskin (30):
  mei: prevent queuing new flow control credit.
  mei: always copy the read buffer if data is ready
  mei: wd: drop the watchdog code from the core mei driver
  watchdog: mei_wdt: register wd device only if required
  watchdog: mei_wdt: re-register device on event
  mei: debugfs: adjust active clients print buffer
  mei: debugfs: allow hbm features list dump in earlier stages
  mei: call stop on failed char device register
  mei: amthif: don't copy from an empty buffer
  mei: amthif: don't drop read packets on timeout
  mei: amthif: allow only one request at a time
  mei: amthif: use rx_wait queue also for amthif client
  mei: amthif: interrupt reader on link reset
  mei: drop superfluous closing bracket from write traces
  mei: wake blocked write on link reset
  mei: clean write queues and wake waiters on disconnect
  mei: discard replies from unconnected fixed address clients
  mei: fill file pointer in read cb for fixed address client
  mei: fixed address clients for the new platforms
  mei: hbm: warn about fw-initiated disconnect
  mei: drop reserved host client ids
  mei: bus: run rescan on me_clients list change
  mei: hbm: send immediate reply flag in enum request
  mei: split amthif client init from end of clients enumeration
  mei: fix double freeing of a cb during link reset
  mei: fix format string in debug prints
  mei: drop global me_client_index
  mei: don't clean control queues on notify request timeout
  mei: fix waiting for wr_ctrl for corner cases.
  mei: don't use wake_up_interruptible for wr_ctrl

Alexey Khoroshilov (1):
  mei: do not pin module if cldrv->probe() failed

Rasmus Villemoes (1):
  mei: bus: use scnprintf in *_show

Tomas Winkler (14):
  mei: bus: remove redundant uuid string in debug messages
  mei: drop nfc leftovers from the mei driver
  watchdog: mei_wdt: implement MEI iAMT watchdog driver
  watchdog: mei_wdt: add status debugfs entry
  mei: bus: whitelist the watchdog client
  mei: trace pci configuration space io
  mei: fix possible integer overflow issue
  mei: constify struct file pointer
  mei: rename variable names 'file_object' to fp
  mei: amthif: replace amthif_rd_complete_list with rd_completed
  mei: amthif: drop parameter validation from mei_amthif_write
  mei: bus: fix RX event scheduling
  mei: bus: fix notification event delivery
  mei: wd: drop AGAIN the watchdog code from the core mei driver

 Documentation/misc-devices/mei/mei.txt |  12 +-
 MAINTAINERS|   1 +
 drivers/misc/mei/Kconfig   |   6 +-
 drivers/misc/mei/Makefile  |   1 -
 drivers/misc/mei/amthif.c  | 130 ++---
 drivers/misc/mei/bus-fixup.c   |  41 +-
 drivers/misc/mei/bus.c |  75 ++
 drivers/misc/mei/client.c  | 215 ++-
 drivers/misc/mei/client.h  |  27 ++--
 drivers/misc/mei/debugfs.c |  65 +++--
 drivers/misc/mei/hbm.c |  47 +++---
 drivers/misc/mei/hw-me.c   |  10 +-
 drivers/misc/mei/hw-txe.c  |  10 +-
 drivers/misc/mei/hw.h  |  32 +++-
 drivers/misc/mei/init.c|  20 +--
 drivers/misc/mei/interrupt.c   |  94 +---
 drivers/misc/mei/main.c| 106 ++
 drivers/misc/mei/mei-trace.c   |   2 +
 drivers/misc/mei/mei-trace.h   |  40 -
 drivers/misc/mei/mei_dev.h | 120 +++
 drivers/misc/mei/pci-me.c  |   4 +-
 drivers/misc/mei/pci-txe.c |   4 +-
 drivers/misc/mei/wd.c  | 391 
-
 drivers/watchdog/Kconfig   |  15 ++
 drivers/watchdog/Makefile  |   1 +
 drivers/watchdog/mei_wdt.c | 746 
+
 26 files changed, 1294 insertions(+), 921 deletions(-)
 delete mode 100644 drivers/misc/mei/wd.c
 create mode 100644 drivers/watchdog/mei_wdt.c

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org

[yocto] what IMAGE_TYPES are valid to pass as "initrd" param to "bootm"?

[Robert P. J. Day]

  not at my dev machine right now, otherwise i'm sure i could figure
this out, but what possible values for IMAGE_FSTYPES are acceptable to
download to u-boot and pass to "bootm" directly as the second argument
for the initrd?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[linux-yocto] [PATCH] usb: typec: wcove: add missing MODULE_ALIAS()

[Pranav Tipnis]

From: Felipe Balbi 

Upstream-Status: Pending
 This is an incremental patch for
 "usb: typec: add driver for Intel
 Whiskey Cove PMIC USB Type-C PHY".

Without a proper MODULE_ALIAS() driver won't get
autoloaded. Let's add one.

Reported-by: Pranav Tipnis 
Signed-off-by: Felipe Balbi 
---
 drivers/usb/typec/typec_wcove.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/usb/typec/typec_wcove.c b/drivers/usb/typec/typec_wcove.c
index c7c2d28..0d9b58d 100644
--- a/drivers/usb/typec/typec_wcove.c
+++ b/drivers/usb/typec/typec_wcove.c
@@ -366,6 +366,7 @@ static struct platform_driver wcove_typec_driver = {
 
 module_platform_driver(wcove_typec_driver);
 
+MODULE_ALIAS("platform:bxt_wcove_usbc");
 MODULE_AUTHOR("Intel Corporation");
 MODULE_LICENSE("GPL v2");
 MODULE_DESCRIPTION("WhiskeyCove PMIC USB Type-C PHY driver");
-- 
1.9.1

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

Re: [linux-yocto] [[yocto-kernel-cache][PATCH] mei.cfg: mei driver is no longer in staging

[Bruce Ashfield]

On 2016-07-07 07:48 AM, Tomas Winkler wrote:

The mei driver was moved out of staging in kernel 3.15


merged.

Bruce



Signed-off-by: Tomas Winkler 
---
  features/amt/mei/mei.cfg | 1 -
  1 file changed, 1 deletion(-)

diff --git a/features/amt/mei/mei.cfg b/features/amt/mei/mei.cfg
index de6f6576871d..19aff024947a 100644
--- a/features/amt/mei/mei.cfg
+++ b/features/amt/mei/mei.cfg
@@ -1,4 +1,3 @@
-CONFIG_STAGING=y
  CONFIG_WATCHDOG_CORE=y
  CONFIG_INTEL_MEI=m
  CONFIG_INTEL_MEI_ME=m



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

Re: [linux-yocto] [PATCH] Update GPIO driver on linux-yocto-4.4 bxt-rebase branch

[Bruce Ashfield]

On 2016-07-06 06:12 PM, Nilesh Bacchewar wrote:

This is incremental patchset to backported Intel WhiskeyCove GPIO driver on
linux-yocto-4.4 from 4.7-rcX. This patch have been submitted upstream and
the approval is in progress, hence may not be final. Patch have been rebased
on bxt-rebase branch.



merged.

Bruce


Nilesh Bacchewar (1):
   gpio: update Intel WhiskeyCove GPIO driver

  drivers/gpio/Kconfig  |  2 +-
  drivers/gpio/gpio-wcove.c | 12 
  2 files changed, 5 insertions(+), 9 deletions(-)



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

Re: [yocto] is meta-mono layer actively supported?

[Khem Raj]

On Thu, Jul 7, 2016 at 12:50 AM, Robert P. J. Day  wrote:
>
>   out of nowhere, a client of mine wants to port from WEC7 to linux
> using YP; they already have a working app written in C# .NET and want
> to drag it with them, obviously using mono.
>
>   i see the YP wiki page on running .NET apps here:
>
> https://wiki.yoctoproject.org/wiki/Building_and_running_embedded_Linux_.NET_applications_from_first_principles
>
> which looks like it has the info they need, given that i know
> absolutely *zero* about C#/.NET/mono, but i might as well learn
> something about it.
>
>   the history of that page suggests it's actively supported, can
> anyone confirm that it really does walk one through how to incorporate
> a .NET app in a YP image? given some time this weekend, i'll try to
> follow how to add and run a simple example. thanks.

its supported. Try to add the layer to your bblayers.conf and add
mono-helloworld to IMAGE_INSTALL to get a sample app.

>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> ___
> 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] Confused on how to use native sdk correctly

[Khem Raj]

On Thu, Jul 7, 2016 at 12:40 AM, Alfonso Lima Astor
 wrote:
> Hello all,
>
> I am working on a project that creates applications for host and target
> architectures. The target SDK works fine, but I am struggling to understand
> how to use the host SDK. In my project, we have tools using QT libraries,
> OpenCV libraries and headers and libraries from other packages.
>
> How am I supposed to use these libraries for the host build? just installing
> them on my computer or adding them to the native sdk? What people do for other
> projects?
>
> Having a look to the SDK environment setup script, it seems to me that
> the native
> SDK is meant to hold tools to support the cross compilation but not supposed 
> to
> be used for the native build. Is this correct?

thats is correct

>
> Thank you
> --
> ___
> 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] USB cam device

[Khem Raj]

On Thu, Jul 7, 2016 at 2:59 AM, Peter Balazovic
 wrote:
> Dears,
>
> I want to have my USB cam device to start numbering from /dev/video5
> and not to assign an usual device (vide0) to the usb camera via UVC
> driver
>
> What  should I modify to change it out of default?

you might be able to do it with udev rules
>
> Thanks.
> --
> ___
> 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] [meta-selinux][PATCH] refpolicy: remove virtual prefix for runtime providers

[Joe MacDonald]

In keeping with the approach of only providing a single default policy at
runtime, we were originally using a virtual/refpolicy dependency and
filling it with one of our specific refpolicy implementations.  This works
well enough for some package systems, but fails for others (specifically
deb, possibly more).

Since the intent was to only have one present in the default image anyway,
we'll just throw out the 'virtual/' part of the RPROVIDES and related
dependencies across the board.

Signed-off-by: Joe MacDonald 
---

In terms of testing on this change, my primary approach was to compare
before/after manifests and ensure that what lands on the filesystem image
hasn't changed.  It is another subtle change to behaviour that I know
isn't unanimously embraced anyway, so I'm happy to discuss alternative
options.  My objective here was just to enable deb support (and to get my
autobuilder to stop complaining about it).

 recipes-security/packagegroups/packagegroup-core-selinux.bb| 2 +-
 recipes-security/packagegroups/packagegroup-selinux-minimal.bb | 2 +-
 recipes-security/refpolicy/refpolicy_common.inc| 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-security/packagegroups/packagegroup-core-selinux.bb 
b/recipes-security/packagegroups/packagegroup-core-selinux.bb
index c6d22b7..9c74458 100644
--- a/recipes-security/packagegroups/packagegroup-core-selinux.bb
+++ b/recipes-security/packagegroups/packagegroup-core-selinux.bb
@@ -25,6 +25,6 @@ RDEPENDS_${PN} = " \
selinux-autorelabel \
selinux-init \
selinux-labeldev \
-   virtual/refpolicy \
+   refpolicy \
coreutils \
"
diff --git a/recipes-security/packagegroups/packagegroup-selinux-minimal.bb 
b/recipes-security/packagegroups/packagegroup-selinux-minimal.bb
index 451ae8b..eac4b94 100644
--- a/recipes-security/packagegroups/packagegroup-selinux-minimal.bb
+++ b/recipes-security/packagegroups/packagegroup-selinux-minimal.bb
@@ -22,5 +22,5 @@ RDEPENDS_${PN} = "\
policycoreutils-sestatus \
policycoreutils-setfiles \
selinux-labeldev \
-   virtual/refpolicy \
+   refpolicy \
 "
diff --git a/recipes-security/refpolicy/refpolicy_common.inc 
b/recipes-security/refpolicy/refpolicy_common.inc
index 1d3b93f..e1eac50 100644
--- a/recipes-security/refpolicy/refpolicy_common.inc
+++ b/recipes-security/refpolicy/refpolicy_common.inc
@@ -6,7 +6,7 @@ LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://${S}/COPYING;md5=393a5ca445f6965873eca0259a17f833"
 
 PROVIDES += "virtual/refpolicy"
-RPROVIDES_${PN} += "virtual/refpolicy"
+RPROVIDES_${PN} += "refpolicy"
 
 # Specific config files for Poky
 SRC_URI += "file://customizable_types \
-- 
1.9.1

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

Re: [yocto] How to set the prefix of a (cmake) recipe?

[Burton, Ross]

On 7 July 2016 at 14:24,  wrote:

> I want to install my software packages to the usr/local/bin dir. That is
> why I need to change the prefix form usr to usr/local. How to archive that?
>
> The software is build through a cmake. Is there somethingt I need to think
> extra for setting the prefix?


This depends on the software sadly, cmake doesn't have a standard way of
setting the prefix.

cmake.bbclass sets CMAKE_INSTALL_PREFIX etc for you on the assumption that
the CMakeLists might be using the GNUInstallDirs macro, but if they are not
then you'll have to read the CMakeLists to identify how to set the prefix
(if you can).

That isn't an inconsistency you've found: autotools defaults to /usr/local
because the assumption is that hand-compiled software shouldn't replace the
operating system, so installs to /usr/local.  If you're building software
using OE then you *are building* the operating system, so prefix is set to
/usr.

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

[yocto] How to set the prefix of a (cmake) recipe?

[S . Jaritz]

Hej

I want to install my software packages to the usr/local/bin dir. That is 
why I need to change the prefix form usr to usr/local. How to archive 
that?

The software is build through a cmake. Is there somethingt I need to think 
extra for setting the prefix?

Maybe I found some inconsistency:
@: GNU(
https://www.gnu.org/prep/standards/html_node/Directory-Variables.html)
the prefix should be "usr/local"
@ config for Bitbake:(
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf?h=blinky
)
the prefix is set to "usr"

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


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 löschen Sie diese 
Nachricht. 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

[linux-yocto] [[yocto-kernel-cache][PATCH] mei.cfg: mei driver is no longer in staging

[Tomas Winkler]

The mei driver was moved out of staging in kernel 3.15

Signed-off-by: Tomas Winkler 
---
 features/amt/mei/mei.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/features/amt/mei/mei.cfg b/features/amt/mei/mei.cfg
index de6f6576871d..19aff024947a 100644
--- a/features/amt/mei/mei.cfg
+++ b/features/amt/mei/mei.cfg
@@ -1,4 +1,3 @@
-CONFIG_STAGING=y
 CONFIG_WATCHDOG_CORE=y
 CONFIG_INTEL_MEI=m
 CONFIG_INTEL_MEI_ME=m
-- 
2.5.5

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

Re: [yocto] yocto build cross toolchain issue

[Chandra Mishra (chanmish)]

Hi Khem Raj,

Sorry for the confusion. There is no such dependency that we can’t change the 
link order. What I meant was in reply, “Since with older gcc version library 
sequence was working, I didn’t doubt on that”. But resequencing the library is 
working for me.

Regards,
[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_01.png?ct=1443872971831]

Chandra Mishra
ENGINEER.DIAGNOSTIC ENGINEERING

chanm...@cisco.com
Phone: +91 80 4429 1490

Cisco Systems, Inc.
Cessna Business Park, Kadubeesanahalli Varthur Hobli, Sarjapur Marathalli ORR
BANGALORE
560 087
India
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.




From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: 05 July 2016 20:54
To: Chandra Mishra (chanmish) 
Cc: Burton, Ross ; yocto@yoctoproject.org
Subject: Re: [yocto] yocto build cross toolchain issue



On Tue, Jul 5, 2016 at 3:06 AM, Chandra Mishra (chanmish) 
> wrote:
Thanks Ross for your suggestion. It worked for me. But in the past it worked 
for me with old sequence but different gcc cross toolchain, so not thinking of 
changing the order.


why wont you change the order.​ Whats depending on it ?



Regards,
[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_01.png?ct=1443872971831]

Chandra Mishra
ENGINEER.DIAGNOSTIC ENGINEERING

chanm...@cisco.com
Phone: +91 80 4429 1490

Cisco Systems, Inc.
Cessna Business Park, Kadubeesanahalli Varthur Hobli, Sarjapur Marathalli ORR
BANGALORE
560 087
India
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.




From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: 05 July 2016 14:59
To: Chandra Mishra (chanmish) >
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] yocto build cross toolchain issue


On 5 July 2016 at 10:20, Chandra Mishra (chanmish) 
> wrote:

  -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -static -lnsl -lpthread -lm -lrt

/sysroots/corei7-64-poky-linux/usr/lib/../lib/librt.a(shm_open.o):
 In function `shm_open':

/build/tmp/work/corei7-64-poky-linux/glibc/2.22-r0/git/rt/../sysdeps/posix/shm_open.c:35:
 undefined reference to `__shm_directory'

At a guess this is due to --as-needed dropping symbols as unused which then are 
used, because --as-needed needs a sorted library list.  Either remove 
--as-needed, or try reordering the libraries so that dependencies are in order.

https://wiki.gentoo.org/wiki/Project:Quality_Assurance/As-needed#Importance_of_linking_order
 has more context.

In this case I'd start with moving -lpthread to the end of the link line.

Ross

--
___
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] USB cam device

[Peter Balazovic]

Dears,

I want to have my USB cam device to start numbering from /dev/video5
and not to assign an usual device (vide0) to the usb camera via UVC
driver

What  should I modify to change it out of default?

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

Re: [yocto] How do I select the kernel version in Dizzy ? ( 3.10 | 3.14 | 3.17 )

[Mark T]

Thanks - that's working.
Mark

On 6 July 2016 at 18:53, Khem Raj  wrote:

> On Wed, Jul 6, 2016 at 10:40 AM, Mark T  wrote:
> > Hi,
> >
> > The Dizzy revision looks to support 3 kernel versions ( 3.10 | 3.14 |
> 3.17
> > ).
> >
> > If I chose Dizzy 1.7.3 - how do I ensure  the 3.10 kernel is used for the
> > build ?
>
> usually you would set that in your machine conf file.
>
> PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
> PREFERRED_VERSION_linux-yocto ?= "3.10%"
>
> >
> > Thanks,
> >
> > Mark
> >
> > --
> > ___
> > 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] Toaster build fails on Master branch Yocto

[Sambaran Ghosh]

While creating a toaster project with the Master Yocto branch,  build
always fails. But if I select Krogoth or Jethro branch then builds
succeeds. The major problem with sub-branches like Krogoth is that there
few layers supported. Is everyone having similar problem? And do you have
any solution?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to tftp download a newer u-boot into RAM and simply execute it?

[Kevin Hao]

On Wed, Jul 06, 2016 at 03:37:04PM -0400, Bruce Ashfield wrote:
> > 
> >so, before i commit myself to this, who's the PPC/MPC8315E-RDB
> > expert on this list who can confirm a stock u-boot should flash to NOR
> > and just plain run?

The ramboot is not supported for this board in u-boot. There do have some
codes about ramboot in the startup code, but you can't expect it to work
without some tweaking.

Thanks,
Kevin


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] is meta-mono layer actively supported?

[Robert P. J. Day]

  out of nowhere, a client of mine wants to port from WEC7 to linux
using YP; they already have a working app written in C# .NET and want
to drag it with them, obviously using mono.

  i see the YP wiki page on running .NET apps here:

https://wiki.yoctoproject.org/wiki/Building_and_running_embedded_Linux_.NET_applications_from_first_principles

which looks like it has the info they need, given that i know
absolutely *zero* about C#/.NET/mono, but i might as well learn
something about it.

  the history of that page suggests it's actively supported, can
anyone confirm that it really does walk one through how to incorporate
a .NET app in a YP image? given some time this weekend, i'll try to
follow how to add and run a simple example. thanks.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

Re: [yocto] linux/limits.h: No such file or directory

[Clemens Lang]

Hi,

Takashi Matsuzawa  wrote:

> >configure: error: C preprocessor "x86_64-pokysdk-linux-gcc -E  
> --sysroot=/mnt/ssd2/>yocto/dev/tmp/x86-wk3/sysroots/x86_64-nativesdk-pokysdk-linux
>   
> " fails sanity check
> >| See `config.log' for more details.
>
> If I look into config.log  
> (gcc-4.9.2/build.x86_64-pokysdk-linux.x86_64-pokysdk-linux/libgcc/config.log) 
>  
> as suggested, I can see the following.
> It says linux/limits.h is not found.
>
> (in config.log)
> >usr/include/bits/local_lim.h:38:26: fatal error: linux/limits.h: No such  
> file or directory

This looks a lot like a problem we’ve seen a while ago. See
   https://lists.yoctoproject.org/pipermail/yocto/2015-July/025856.html
which is the mailing list post a colleague sent to the list back then.

Looking at our git history, the workaround we did back then was add a  
dependency from gcc-crosssdk-initial to nativesdk-linux-libc-headers if  
$TARGET_OS starts with “linux”.


HTH,
Clemens
-- 
BMW Car IT GmbH
Clemens Lang
Spezialist Entwicklung
Lise-Meitner-Straße 14
89081 Ulm

Tel: +49-731-37804182
Mail: clemens.l...@bmw-carit.de
Web: http://www.bmw-carit.de

BMW Car IT GmbH
Geschäftsführer: Michael Würtenberger und Alexis Trolin
Sitz und Registergericht: München HRB 134810

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

[yocto] Confused on how to use native sdk correctly

[Alfonso Lima Astor]

Hello all,

I am working on a project that creates applications for host and target
architectures. The target SDK works fine, but I am struggling to understand
how to use the host SDK. In my project, we have tools using QT libraries,
OpenCV libraries and headers and libraries from other packages.

How am I supposed to use these libraries for the host build? just installing
them on my computer or adding them to the native sdk? What people do for other
projects?

Having a look to the SDK environment setup script, it seems to me that
the native
SDK is meant to hold tools to support the cross compilation but not supposed to
be used for the native build. Is this correct?

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

Re: [yocto] how to tftp download a newer u-boot into RAM and simply execute it?

[Stefano Babic]

Hi Robert,

On 06/07/2016 21:14, Robert P. J. Day wrote:
> On Wed, 6 Jul 2016, Chris Hallinan wrote:
> 
>> Hi Robert,
>> That's not old, that's ancient in dog^HU-Boot years - LOL!
>>
>> It's been quite a while since I looked at a PPC U-Boot, but at a
>> minimum, you will need to link U-Boot to a RAM'able address.  By
>> default, I'm sure the recipe links it for the NOR addresses.  When
>> it boots from NOR it immediately relocates itself to a RAM address
>> from NOR, if memory serves.  Notice it's crashing right away, on the
>> second instruction.
> 
>   i came to that conclusion ... i looked at the u-boot.srec file that
> was generated and, sure enough:
> 
> S00E752D626F6F742E73726563C0
> S315FE0042424242424242420606060606060606AC
> S315FE10DC
> S315FE20A0A0A0A0A0A0A0A06060606060606060CC
> ... snip ...
> 
> so definitely linked for flashing to beginning of NOR flash at
> 0xFE00. so i suspect i could just flash it and reset and it would
> work just fine. and never mind, i found the answer i was after:
> 

U-Boot is linked at the address set with CONFIG_SYS_TEXT_BASE in
include/configs/MPC8315ERDB.h. You can try to change this.

It is not only a problem of the linker address. U-Boot sets the RAM
controller and this should be skipped with some other basic part (PLL,
and so on) if you run from RAM.

However, I see the board has already a setup.

#if CONFIG_SYS_MONITOR_BASE < CONFIG_SYS_FLASH_BASE && \
!defined(CONFIG_NAND_SPL)
#define CONFIG_SYS_RAMBOOT
#else
#undef CONFIG_SYS_RAMBOOT
#endif

You could set CONFIG_SYS_MONITOR_BASE in RAM and SYS_RAMBOOT should be
automatically set. This change the bootloader and the RAM controller is
not set up again.

However, as mentioned in the website, you are not exactly testing the
new boot loader, you are testing another bootloader. If the new
bootloader has issues by setting the RAM controller, for example, it
runs when you load from RAM and it will not run later...


> http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStartedInRAM
> 
> i was hoodwinked into thinking it would be easy because i found this
> page:
> 
> https://blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:tftp_loading_files
> 
> of course, that page is for the blackfin, precisely one of the
> platforms the denx page says it *can* work for. gr.
> 
>   so, before i commit myself to this, who's the PPC/MPC8315E-RDB
> expert on this list who can confirm a stock u-boot should flash to NOR
> and just plain run?

I have not the board and I cannot test it - if you have a JTAG debugger,
you are always able to restore the board in case something goes wrong.

Best regards,
Stefano Babic

-- 
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: How to create a directory for an SD-Card mount?

[S . Jaritz]

Problem solved! Thank you for the help.

It was solved by:

do_install () {
...
install -d ${D}/media/sd1
...
}

FILES_${PN} += "media/sd1"

@Mike:
I am using the meta-atmel. The mount dir is created. In my case I have a 
rule which mounts the sd card to mount/sd1, That's why I need to create 
sd1. But good idea, maybee I will change the rule, so it creates (if 
needed) the dir to mount.

Regards!

Stefan Jaritz


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


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 löschen Sie diese 
Nachricht. 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.



Von:Mike Looijmans 
An: 
Datum:  07.07.2016 08:04
Betreff:Re: [yocto] How to create a directory for an SD-Card 
mount?
Gesendet von:   yocto-boun...@yoctoproject.org



On many embedded systems, /media/ is volatile. So you probably need to 
create 
an entry for a volatile dir.

Better is to create/delete the directory in the mount script. That also 
avoids 
races, since creating a directory is an atomic operation. And it allos you 
to 
mount multiple devices.

I'm actually surprised that this isn't already in place. Maybe you're 
missing 
some obscure udev package in your image?

On 06-07-16 20:09, Daniel. wrote:
> install -d ${D}/media/sd1
> ???
>
> 2016-07-06 11:44 GMT-03:00  :
>> Hej
>>
>> I managed to create and install a rule that should mount a sd card to
>> "/media/sd1".  To finish it, I need to create the directory "sd1" in 
media.
>> My recipe for the rule looks like:
>> ###
>> SUMMARY = "the udev rules for the board"
>> SECTION = "rules"
>> LICENSE = "CLOSED"
>>
>> SRC_URI = "file://50-mmc.rules \
>>  "
>> S = "${WORKDIR}"
>>
>> do_install () {
>>  install -d ${D}${sysconfdir}/udev/rules.d
>>  install -m 0644 ${WORKDIR}/50-mmc.rules
>> ${D}${sysconfdir}/udev/rules.d/
>> }
>> ###
>> How to create a dir in do_install which goes to the package?
>>
>> By the way:
>> I was also appending fstab after this article
>>
>> https://communities.intel.com/thread/49251
>>
>> Is there an better way to uncomment/modify that one line in fstab?
>>
>> Regards!
>>
>> Stefan Jaritz
>>
>> 
>> ESA Elektroschaltanlagen Grimma GmbH
>> Broner Ring 30
>> 04668 Grimma
>> Telefon: +49 3437 9211 176
>> Telefax: +49 3437 9211 26
>> E-Mail: s.jar...@esa-grimma.de
>> Internet: www.esa-grimma.de
>>
>>
>> Geschäftsführer:
>> Dipl.-Ing. Jörg Gaitzsch
>> Jörg Reinker
>>
>> Sitz der Gesellschaft: Grimma
>> Ust.-ID: DE 141784437
>> Amtsgericht: Leipzig, HRB 5159
>> Steuernummer: 238/108/00755
>>
>>
>> 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 löschen Sie diese
>> Nachricht. 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.
>> --
>> 
 
Kind regards,
 
Mike Looijmans
System Expert
 



TOPIC Products
 
 

Materiaalweg 4
 
 

5681 RJ Best
T:
+31 (0) 499 33 69 69

Postbus 440
E:
mike.looijm...@topicproducts.com

5680 AK Best
W:
www.topicproducts.com

The Netherlands




Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!

___
>> 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] How to create a directory for an SD-Card mount?

[Mike Looijmans]

On many embedded systems, /media/ is volatile. So you probably need to create an entry for a volatile dir.Better is to create/delete the directory in the mount script. That also avoids races, since creating a directory is an atomic operation. And it allos you to mount multiple devices.I'm actually surprised that this isn't already in place. Maybe you're missing some obscure udev package in your image?On 06-07-16 20:09, Daniel. wrote:> install -d ${D}/media/sd1> ???>> 2016-07-06 11:44 GMT-03:00  :>> Hej I managed to create and install a rule that should mount a sd card to>> "/media/sd1".  To finish it, I need to create the directory "sd1" in media.>> My recipe for the rule looks like:>> ###>> SUMMARY = "the udev rules for the board">> SECTION = "rules">> LICENSE = "CLOSED" SRC_URI = "file://50-mmc.rules \>>  ">> S = "${WORKDIR}" do_install () {>>  install -d ${D}${sysconfdir}/udev/rules.d>>  install -m 0644 ${WORKDIR}/50-mmc.rules>> ${D}${sysconfdir}/udev/rules.d/>> }>> ###>> How to create a dir in do_install which goes to the package? By the way:>> I was also appending fstab after this article https://communities.intel.com/thread/49251 Is there an better way to uncomment/modify that one line in fstab? Regards! Stefan Jaritz >> ESA Elektroschaltanlagen Grimma GmbH>> Broner Ring 30>> 04668 Grimma>> Telefon: +49 3437 9211 176>> Telefax: +49 3437 9211 26>> E-Mail: s.jar...@esa-grimma.de>> Internet: www.esa-grimma.de>> Geschäftsführer:>> Dipl.-Ing. Jörg Gaitzsch>> Jörg Reinker Sitz der Gesellschaft: Grimma>> Ust.-ID: DE 141784437>> Amtsgericht: Leipzig, HRB 5159>> Steuernummer: 238/108/00755>> 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 löschen Sie diese>> Nachricht. 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.>> -->> 
 
Kind regards,
 
Mike Looijmans
System Expert
 





  
  

  TOPIC 
  Products

   

   
  

  Materiaalweg 
4

   

   
  

  5681 
  RJ Best

  T:

  +31 (0) 499 33 69 
  69
  

  Postbus 440

  E:

  mike.looijm...@topicproducts.com
  

  5680 AK 
Best

  W:

  www.topicproducts.com
  
The Netherlands



 Please consider the 
environment before printing this e-mailTopic zoekt gedreven (embedded) software specialisten!
___>> yocto mailing list>> yocto@yoctoproject.org>> https://lists.yoctoproject.org/listinfo/yocto>


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