From: Zongchun Yu <Zongchun.Yu(a)freescale.com>
Signed-off-by: Zongchun Yu <Zongchun.Yu(a)freescale.com>
---
.../conf/distro/include/tcmode-external-linaro.inc | 27 ++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/meta-linaro-toolchain/conf/distro/include/tcmode-external-linaro.inc b/meta-linaro-toolchain/conf/distro/include/tcmode-external-linaro.inc
index ed00a00..e1098c0 100644
--- a/meta-linaro-toolchain/conf/distro/include/tcmode-external-linaro.inc
+++ b/meta-linaro-toolchain/conf/distro/include/tcmode-external-linaro.inc
@@ -46,6 +46,33 @@ DISTRO_FEATURES_LIBC = "ipv4 ipv6 libc-backtrace libc-big-macros libc-bsd libc-c
ENABLE_BINARY_LOCALE_GENERATION = "0"
GLIBC_INTERNAL_USE_BINARY_LOCALE = "precompiled"
+ERROR_QA[type] ?= "list"
+python toolchain_metadata_setup () {
+ import subprocess
+ if not isinstance(e, bb.event.ConfigParsed):
+ return
+
+ d = e.data
+ l = d.createCopy()
+ l.finalize()
+ oe_import(l)
+
+ external_toolchain = l.getVar('EXTERNAL_TOOLCHAIN', True)
+ if not external_toolchain or external_toolchain == 'UNDEFINED':
+ bb.fatal("Error: EXTERNAL_TOOLCHAIN must be set to the path to your linaro toolchain")
+
+ if not os.path.exists(external_toolchain):
+ bb.fatal("Error: EXTERNAL_TOOLCHAIN path '%s' does not exist" % external_toolchain)
+
+ # The external toolchain may not have been built with the yocto preferred
+ # gnu hash setting, so ensure that the corresponding sanity check is not an error.
+ error_qa = oe.data.typed_value('ERROR_QA', l)
+ if 'ldflags' in error_qa:
+ error_qa.remove('ldflags')
+ d.setVar('ERROR_QA', ' '.join(error_qa))
+}
+addhandler toolchain_metadata_setup
+
def populate_toolchain_links(d):
import errno
import os
--
1.7.0.4
Are there any tools for validating device tree files?
I'm getting a device tree header not valid error in rtsm err:-9 but
obviously that doesn't give any hints about what line it might be.
Thanks!
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Tech Lead, Graphics Working Group | Linaro.org │ Open source software
for ARM SoCs
w) tom.gall att linaro.org
h) tom_gall att mac.com
Hi,
So I'm trying to boot an aarch64 kernel with the FVP simulator.
Specifically I'm using the latest open embedded hwpack:
hwpack_linaro-vexpress64-rtsm_20131216-560_arm64_supported.tar.gz
and then an experimental OE image that I put together myself.
The kernel however doesn't even start. Last thing I get after the count down is
ERROR : Did not find Linux kernel and it dumps me into the boot manager menu.
I used linaro-media-create to make the image.
linaro-media-create --dev fastmodel --output-directory .
--image_size=2000M --hwpack
./hwpack_linaro-vexpress64-rtsm_20131216-560_arm64_supported.tar.gz
--binary ./linaro-image-xfce-genericarmv8-20140115214956.rootfs.tar.gz
Thoughts?
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Tech Lead, Graphics Working Group | Linaro.org │ Open source software
for ARM SoCs
w) tom.gall att linaro.org
h) tom_gall att mac.com
The first test rebuild of Trusty Tahr was started last week for all
architectures (main component only). It is still running for arm64, all other
architectures did finish the test rebuild.
Results can be seen at
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201401…
The archive for the test rebuild is
https://launchpad.net/ubuntu/+archive/test-rebuild-20140108/
The test rebuild was done with a change which is not yet in the archive,
changing the default Python3 to use the not yet released Python 3.4.
These packages can be found in a ppa [1]. Please ask on IRC (#ubuntu-devel) if
you are in doubt that a build failure is caused by the changed Python3 default.
Additional build failures for packages in trusty-proposed (not yet in trusty)
can be found at http://qa.ubuntuwire.com/ftbfs/
Please help fixing the build failures for the final release.
Planning the next test rebuild for amd64, i386 and armhf for all components for
the next week.
Matthias
[1] https://launchpad.net/~ubuntu-toolchain-r/+archive/python3
Hello,
I used the merge-gnexus-blobs script to flash the prebuilt image. The
script worked smoothly except the make_ext4fs gave me a segmentation
fault. So instead I just downloaded a prebuilt binary of make_ext4fs
from here: https://code.google.com/p/archlive/downloads/detail?name=make_ext4fs.7z
Then the script ran to the end and the phone rebooted. But it freezed
at the boot splash of "google".
My host is running ubuntu 12.04 64bit.
I couldn't think of anyway to debug this problem and google doesn't
help much. So any suggestion is appreciated. Thanks!
--
Regards,
Chao Xu
I am seeing a behaviour where the load variations are very frequency
between 1ghz and 300mhz in a very short interval of time giving the
ping-pong effect. \
Is there a way of avoiding this Also, is it possible to find out which
task is causing this behaviour.
All this happens in a couple of sampling periods of ondemand.
--
Regards,
Sriram
Hello,
I'm trying to fire up an ARM fastmodel using a virtio block device rather
than the emulated MMC block device.
UEFI is reading the kernel & DTB off the virtio device, so I know the
device is present.
I added this to my kernel config:
diff --git a/linaro/configs/vexpress.conf b/linaro/configs/vexpress.conf
index 83acca8..2582450 100644
--- a/linaro/configs/vexpress.conf
+++ b/linaro/configs/vexpress.conf
@@ -58,3 +58,12 @@ CONFIG_LEDS_GPIO=y
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_CPU=y
+CONFIG_NET_9P=y
+CONFIG_NET_9P_VIRTIO=y
+CONFIG_VIRTIO_BLK=y
+CONFIG_VIRTIO_NET=y
+CONFIG_VIRTIO_CONSOLE=y
+CONFIG_VIRTIO=y
+CONFIG_VIRTIO_BALLOON=y
+CONFIG_VIRTIO_MMIO=y
+CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
So far, I don't see any vda devices being enumerated (or any other virtio
messages) and it rootwaits for /dev/vda2.
I'm launching the model like this:
FVP_VE_Cortex-A15x1 -C motherboard.flashloader0.fname=$UEFI -C
motherboard.flashloader1.fname=uefi-vars.fd -C
motherboard.flashloader1.fnameWrite=uefi-vars.fd -C
motherboard.pl011_uart0.unbuffered_output=true -C
motherboard.smsc_91c111.enabled=1 -C
motherboard.hostbridge.userNetworking=1 -C
motherboard.virtioblockdevice.image_path=linaro.img
My kernel boot log is here:
https://pastebin.linaro.org/view/97165b9e
Model version:
Fast Models [8.3.44 (Nov 20 2013)]
Anyone had better luck using virtio on armv7 models and have any insights?
Cheers,
Ryan.