Hello all,
I have also sent this email to iotivity list.
I am following the template of iotivity-simple-client inside recipes-apps in
order to bitbake my custom simple server and simple client.
The client succeeds in bitbaking but the server has the errors:
Log data follows:
| DEBUG: Executi
On Wed, 2017-07-12 at 05:23 +, Kenny Koller wrote:
> I'm trying to piece together the various load addresses used in the
> boot sequence. I have built core-image-minimal for a Beaglebone. How
> can I determine which load address and entry point is used when
> mkimage is called for the kernel? S
A release candidate build for yocto-2.3.1.rc1 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741fb9
Hi Michael
You sent the mail for rc1 and there is an rc2 available, according to RP rc2 is
the one that will be used for QA.
Regards,
José
-Original Message-
From: Michael Halstead [mailto:mhalst...@linuxfoundation.org]
Sent: Wednesday, July 12, 2017 11:38 AM
To: pi...@toganlabs.com;
The RC2 e-mail should arrive shortly. It was sent the normal way, directly
by the autobuilder.
On Wed, Jul 12, 2017 at 10:03 AM, Perez Carranza, Jose <
jose.perez.carra...@intel.com> wrote:
> Hi Michael
>
> You sent the mail for rc1 and there is an rc2 available, according to RP
> rc2 is the one
A release candidate build for yocto-2.3.1.rc2 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc2
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d
meta-qt4 : e120a2193be3982d55741
Hello Team ,
I want to set ACL and SMACK/SELinux rules to device files (line /dev/ipc2
/dev/galcore etc .. ) from the build system . But device files are
dynamically populated at runtime.
Do we have some way in "Yocto" to achieve the goal ?
Thanks & Regards
Shrawan
--
_
Hi,
On 2017-07-12 08:23, Kenny Koller wrote:
I'm trying to piece together the various load addresses used in the boot
sequence. I have built core-image-minimal for a Beaglebone. How can I
determine which load address and entry point is used when mkimage is
called for the kernel? Should I dig i
Hello All,Does anyone know if recipes are available for
gcc-arm-none-eabi & binutils-arm-none-eabi?
My build works okay when I use package_rpm and fails with package_deb.
My bblayers.conf & local.conf are at
https://github.com/develone/raspberrypi2_yocto/tree/master/poky2.2/raspberrypi2/conf_fil
Good morning,
I am trying to setup an automate Jenkins CI server to build an image.
To do this I need to automate the process of setting up the Yocto work
area completely. As part of this process I am trying to eliminate the
use of or automate the production of local.conf and bblayers.conf
files
Hello All ,
I want to ask if anyone managed to Run the PERF tool utilities that depends on
the "perf events" as i have problem
finding the path "/sys/kernel/debug/tracing/events" in my build even after
configuring all the necessary options and recipes and many tries.
some information about my
Hello All,
Could you help me in resolving the following issue in Yocto Morty for wifi
Enabled the drivers,
<*> Broadcom FullMAC wireless cards support │ │
│ │ [*] SDIO bus interface support
At the target getting following errors,
root@wandboard:~# dmesg | grep brcm
[ 1.739333] brcmfmac_sdi
12 matches
Mail list logo
