On Wed, Jul 6, 2016 at 7:05 PM, Takashi Matsuzawa
wrote:
> Hello Yocto.
>
> I am seeing this error recently, and wonder if it is a known issue that has
> a workaround.
>
> It does not go even if I delete DL_DIR or SSTATE_CACHE, etc. It started to
> happen, though
On Fri, 01 Jul 2016 09:55:38 Zhenhua Luo wrote:
> On Fri, 01 Jul 2016 09:11:47 Ottavio Campana wrote:
> > I would like to customize an image I am developing based on core image
> > minimal.
> >
> > Particularly, I'd like to customize the files /etc/network/interfaces and
> > /etc/inittab .
>
>
Hi Robert,
On Tue, 05 Jul 2016 12:02:11 Robert Berger wrote:
> According to the release notes it should be possible to build a
> baremetal (no glibc/Linux) cross compiler with the YP. I just can't find
> any information how this could be done.
>
> I would like to build a native compiler e.g. for
Hello Yocto.
I am seeing this error recently, and wonder if it is a known issue that has a
workaround.
It does not go even if I delete DL_DIR or SSTATE_CACHE, etc. It started to
happen, though previously the build ran well.
>configure: error: C preprocessor "x86_64-pokysdk-linux-gcc -E
This should deploy the file correctly.
do_install_append() {
install -d ${D}${sysconfdir}/init.d
install -m 0755 ${WORKDIR}/can_if
${D}${sysconfdir}/init.d/can_if
}
On Mi, 2016-07-06 at 11:20 +0200, s.jar...@esa-grimma.de wrote:
> Hej,
>
> I want to start a service that
On Sat, 18 Jun 2016 12:07:02 +0100
Paul Barker wrote:
> Following discussion on the Raspberry Pi tools bug tracker it was
> found that rpi-mkimage is no longer needed with recent firmware. It
> can therefore be dropped from the layer completely.
>
> Whilst looking into
Enable this for Intel PMIC with ADC channels monitoring system
temperature measurements and alerts.
Signed-off-by: Nilesh Bacchewar
---
features/power/intel_pmic.cfg | 6 ++
features/thermal/coretemp.cfg | 3 +++
2 files changed, 9 insertions(+)
diff --git
Hello Bruce,
This change enables PMIC thermal feature on broxton platform. Changes are added
in
coretemp.cfg and intel pmic. This change is targeted for yocto-4.4 branch.
Nilesh Bacchewar (1):
features/thermal: Enable Intel PMIC thermal feature
features/power/intel_pmic.cfg | 6 ++
Hello Bruce,
This is to enable USB type C feature on broxton platform. I have
created new config fragments for usb type c and intel pmic. This
should go in yocto-4.4 branch.
Pranav Tipnis (1):
broxton: Enable USB Type C feature for broxton
features/power/intel_pmic.cfg| 5 +
Incremental patch for Intel WhiskeyCove GPIO driver based on
updated patch version
Changes:
- Typo fix (Whsikey --> Whiskey).
- Removed the device id table and added MODULE_ALIAS()
Signed-off-by: Nilesh Bacchewar
---
drivers/gpio/Kconfig | 2 +-
Hi,
Gary what poky version you are using ?
It seems that you probably updated somehow local workspace recipe for
binutils from poky master upstream. 5 days ago binutils recipe was updated
with new patch.
Publish the wic images created by the nightly-wic build so they are
available for QA testing.
[YOCTO #9397]
Signed-off-by: Bill Randle
---
buildset-config.controller/nightly-wic.conf| 8 ++---
.../autobuilder/buildsteps/PublishArtifacts.py | 35
Previously all the md5sum files got put into the top level deploy directory.
This patch keeps the md5sum file in the same directory as the file it is
hashing. It also limits the traversal depth to five, to avoid hashing the
wic components that go into making the wic images.
Signed-off-by: Bill
QA started testing wic images in Yocto 2.1, but was building them
themselves. Have the autobuilder publish the wic images so they are
available for testing.
[YOCTO #9397]
Bill Randle (2):
PublishArtifacts.py: create md5sum files in same dir as artifacts
publish build artifacts for wic images
You also need to package it with FILES
On Jul 6, 2016 11:09 AM, "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
> >
On 2016-07-06 03:14 PM, 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
ok, one last dumb question before i throw caution to the winds. i'm
looking at the u-boot board defn file for this board,
include/configs/MPC8315ERDB.h, and i see the following in there:
#if !defined(CONFIG_SYS_RAMBOOT)
#define CONFIG_ENV_IS_IN_FLASH 1
#define
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
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
ok, i'm trying to do something on my MPC8315E-RDB that *should* be
really simple, and i'm getting nowhere.
currently on this machine, i have u-boot in NOR flash, and it's old
but it will still boot the other images also stored in NOR flash:
U-Boot 1.3.0-rc2 (Mar 21 2008 - 16:00:02)
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:
>
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
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 ?
Thanks,
Mark
--
___
yocto mailing list
yocto@yoctoproject.org
On 2016-07-05 11:26 PM, guojian.z...@windriver.com wrote:
From: Guojian Zhou
These patches will supply the fsl-ls10xx bsp scc/cfg kernel meta support
for the linux-yocto-4.1 kernel.
The FSL LS1021A-IOT platform will work well with this kernel.
merged
Bruce
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 =
On 2016-07-06 16:27, Burton, Ross wrote:
On 6 July 2016 at 15:23, Gary Thomas > wrote:
Dependency on checksum of file
MIPS-GAS-Fix-an-ISA-override-not-lifting-ABI-restrictions.patch was removed
As this show binutils changing its SRC_URI this
From: Guojian Zhou
These patches will supply the fsl-ls10xx bsp scc/cfg kernel meta support
for the linux-yocto-4.1 kernel.
The FSL LS1021A-IOT platform will work well with this kernel.
On 6 July 2016 at 15:23, Gary Thomas wrote:
> Dependency on checksum of file
> MIPS-GAS-Fix-an-ISA-override-not-lifting-ABI-restrictions.patch was removed
>
As this show binutils changing its SRC_URI this suggests that you did
something in between the two runs, or those
On 2016-07-06 13:51, Chris Z. wrote:
Hi,
Check:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#shared-state-cache
"... the build system detects changes in the "inputs" to a given task by
creating a checksum (or signature) of the
task's inputs. If the checksum changes, the
it's possible i'm just hopelessly misreading something, but i just
built (using pure defaults) an image for my MPC8315E-RDB dev kit, and
while the current board config header file
include/configs/MPC8315ERDB.h contains:
/*
* The reserved memory
*/
#define CONFIG_SYS_MONITOR_LEN (384 * 1024)
Doesn't the sysroots live on tmp/sysroots? Doesn't the crosscompiler
and toolchains live in sysroots? Doesn't you need crosscompilers and
toolchains to compile everything else?
2016-07-06 8:51 GMT-03:00 Chris Z. :
> Hi,
>
> Check:
>
Oohhh I see, socketcan is your recipe, excuse me for my mistake.
Andres and Burton are right, you need to install that file, eg:
do_install() {
install -d "${D}${sysconfdir}/init.d/"
install -m 600 "${S}/can_if" "${D}${sysconfdir}/init.d/can_if"
}
Change the second line to point to
Isn't "libsocketcan" instead of only "socketcan"!?
Regards,
2016-07-06 6:45 GMT-03:00 Burton, Ross :
>
> On 6 July 2016 at 10:39, Anders Darander wrote:
>>
>> > CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
>>
>> If this is the complete recipe,
Hi,
Check:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#shared-state-cache
"... the build system detects changes in the "inputs" to a given task by
creating a checksum (or signature) of the task's inputs. If the checksum
changes, the system assumes the inputs have changed
I just had a [nearly] complete build failed (building webkitgtk
after some 6000 tasks). I decided to try the 'rebuild from sstate'
by removing my 'tmp' directory and rebuild. Bitbake proceeded to
run 2200 setscene tasks and then [it seems] started over on the
build, rebuilding the target gcc,
On 6 July 2016 at 10:39, Anders Darander wrote:
> > CONFFILES_${PN} += "${sysconfdir}/init.d/can_if"
>
> If this is the complete recipe, you never install can_if...
>
Which means the package is empty, which means it doesn't get generated,
which explains why you can't add
* s.jar...@esa-grimma.de [160706 11:22]:
> I want to start a service that generates Sockets for the CAN Modules.
> Manually configuring the system is no problem, but I like to have it done
> by yocto. Below I give the code of my recipe (socketcan.bb):
> SUMMARY = "the
Hej,
I want to start a service that generates Sockets for the CAN Modules.
Manually configuring the system is no problem, but I like to have it done
by yocto. Below I give the code of my recipe (socketcan.bb):
#
SUMMARY = "the config for the can socket interface"
SECTION
Using precompiled headers may lead to errors in parallel builds:
| In file included from :0:0:
| /usr/include/stdc-predef.h:59:1: error: one or more PCH files were found, but
they were invalid
| #endif
| ^
| /usr/include/stdc-predef.h:59:1: error: use -Winvalid-pch for more information
|
39 matches
Mail list logo