[yocto] If developers want Ada support see this mail.
Hi, I've hit bit of a wall and I've placed a large comment in the meta-ada readme. See https://github.com/Lucretia/meta-ada/tree/jethro for more info on how you can help. Thanks, Luke. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] New message
I just started a new build and saw a message that's new to me: NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-libc.tar.bz2;md5sum=4b6fb2106c2f18b8f9c8ac67e1cf9e57 * What is this about? * Can this file be served by my local mirror? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.1_M3.rc1_M3.rc1 now available.
A release candidate build for yocto-2.1_M3.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M3.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 7965dc814964a30e54542b1d5ef2029d565240bd meta-fsl-arm : 37564e6801ce82fad979b4f57151c676d80e8a6c meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae meta-qt4 : 4058b0773381f894d915ea3dfac5fe052d82a9a7 meta-qt3 : 7d958b928a4a38a186746fabbc0d8169dd8bb3a6 meta-fsl-ppc : 2642cf5e8a6f8d11603acf016b8c075ebce00ec0 poky : 8debfea81e69d038bd2d56314b272cb74f5582ed This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Problems building live image
I'd like to to some testing that qemu just doesn't seem up to so I attempted to build a live ISO per the documentation. I added these lines to local.conf: IMAGE_FSTYPES_genericx86 += "live" NOISO_genericx86 = "0" When I try to build core-image-base I get this error: ERROR: INITRD_IMAGE_LIVE core-image-minimal-initramfs cannot use image live, hddimg or iso. ERROR: Check IMAGE_FSTYPES and INITRAMFS_FSTYPES settings. ERROR: Failed to parse recipe: /local/poky-cutting-edge/meta/recipes-core/images/core-image-minimal-initramfs.bb I'm using a recent Poky checkout (d53413d3a8444c38a83ea37867c8af7754d8e702) Am I just doing something wrong here? I was following this section of the mega-manual: 26.56. image-live.bbclass¶ The image-live class supports building "live" images. Normally, you do not use this class directly. Instead, you add "live" to IMAGE_FSTYPES. For example, if you were building an ISO image, you would add "live" to IMAGE_FSTYPES, set the NOISO variable to "0" and the build system would use the image-live class to build the ISO image. I don't have any available hardware for this testing, so I thought I'd use VirtualBox. Is this a reasonable approach? I want to use a live ISO so I get a writable file system. I tried just using the .hddimage but that doesn't boot with VirtualBox :-( To be clear, along with the additions above in local.conf, I tried: $ MACHINE=genericx86 bitbake core-image-base Thanks for any ideas -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-4.4: Add the pitft22 overlay from adafruit
Signed-off-by: Khem Raj
---
.../0001-dts-add-overlay-for-pitft22.patch | 106 +
recipes-kernel/linux/linux-raspberrypi_4.4.bb | 10 +-
2 files changed, 113 insertions(+), 3 deletions(-)
create mode 100644
recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
diff --git
a/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
new file mode 100644
index 000..7cb076f
--- /dev/null
+++
b/recipes-kernel/linux/linux-raspberrypi-4.4/0001-dts-add-overlay-for-pitft22.patch
@@ -0,0 +1,106 @@
+From a28bd410022b32a64e208f04b45add6326990332 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?=
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker
+---
+ arch/arm/boot/dts/overlays/Makefile| 1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+Index: kernel-source/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+===
+--- /dev/null
kernel-source/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+@@ -0,0 +1,69 @@
++/*
++ * Device Tree overlay for pitft by Adafruit
++ *
++ */
++
++/dts-v1/;
++/plugin/;
++
++/ {
++compatible = "brcm,bcm2835", "brcm,bcm2708", "brcm,bcm2709";
++
++fragment@0 {
++target = <&spi0>;
++__overlay__ {
++status = "okay";
++
++spidev@0{
++status = "disabled";
++};
++
++spidev@1{
++status = "disabled";
++};
++};
++};
++
++fragment@1 {
++target = <&gpio>;
++__overlay__ {
++pitft_pins: pitft_pins {
++brcm,pins = <25>;
++brcm,function = <1>; /* out */
++brcm,pull = <0>; /* none */
++};
++};
++};
++
++fragment@2 {
++target = <&spi0>;
++__overlay__ {
++/* needed to avoid dtc warning */
++#address-cells = <1>;
++#size-cells = <0>;
++
++pitft: pitft@0{
++compatible = "ilitek,ili9340";
++reg = <0>;
++pinctrl-names = "default";
++pinctrl-0 = <&pitft_pins>;
++
++spi-max-frequency = <3200>;
++rotate = <90>;
++fps = <25>;
++bgr;
++buswidth = <8>;
++dc-gpios = <&gpio 25 0>;
++debug = <0>;
++};
++
++};
++};
++
++__overrides__ {
++speed = <&pitft>,"spi-max-frequency:0";
++rotate = <&pitft>,"rotate:0";
++fps = <&pitft>,"fps:0";
++debug = <&pitft>,"debug:0";
++};
++};
+Index: kernel-source/arch/arm/boot/dts/overlays/Makefile
+===
+--- kernel-source.orig/arch/arm/boot/dts/overlays/Makefile
kernel-source/arch/arm/boot/dts/overlays/Makefile
+@@ -43,6 +43,7 @@ dtbo-$(RPI_DT_OVERLAYS) += pi3-disable-b
+ dtbo-$(RPI_DT_OVERLAYS) += pi3-miniuart-bt.dtbo
+ dtbo-$(RPI_DT_OVERLAYS) += piscreen.dtbo
+ dtbo-$(RPI_DT_OVERLAYS) += piscreen2r.dtbo
++dtbo-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtbo
+ dtbo-$(RPI_DT_OVERLAYS) += pitft28-capacitive.dtbo
+ dtbo-$(RPI_DT_OVERLAYS) += pitft28-resistive.dtbo
+ dtbo-$(RPI_DT_OVERLAYS) += pps-gpio.dtbo
diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index f7c5bfb..027d964 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,6 +1,10 @@
-LINUX_VERSION ?= "4.4.3"
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
-SRCREV = "36babd89241c85258acebe06616f1f1a58356f8e"
-SRC_URI =
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y"
+LINUX_VERSION ?= "4.4.5"
+
+SRCREV = "a2c8f5b320a7ca852551bb58a816
Re: [yocto] Problems building live image
just use IMAGE_FSTYPES = "vmdk" if you plan to use virtualbox and need a raw image. On Sun, Mar 13, 2016 at 10:16 PM, Gary Thomas wrote: > I'd like to to some testing that qemu just doesn't seem up to > so I attempted to build a live ISO per the documentation. I > added these lines to local.conf: > IMAGE_FSTYPES_genericx86 += "live" > NOISO_genericx86 = "0" > > When I try to build core-image-base I get this error: > ERROR: INITRD_IMAGE_LIVE core-image-minimal-initramfs cannot use image > live, hddimg or iso. > ERROR: Check IMAGE_FSTYPES and INITRAMFS_FSTYPES settings. > ERROR: Failed to parse recipe: > /local/poky-cutting-edge/meta/recipes-core/images/core-image-minimal-initramfs.bb > > I'm using a recent Poky checkout (d53413d3a8444c38a83ea37867c8af7754d8e702) > > Am I just doing something wrong here? I was following this section of the > mega-manual: > > 26.56. image-live.bbclass¶ > > The image-live class supports building "live" images. > > Normally, you do not use this class directly. Instead, you add "live" to > IMAGE_FSTYPES. > For example, if you were building an ISO image, you would add "live" to > IMAGE_FSTYPES, > set the NOISO variable to "0" and the build system would use the > image-live class to > build the ISO image. > > I don't have any available hardware for this testing, so I thought > I'd use VirtualBox. Is this a reasonable approach? I want to use > a live ISO so I get a writable file system. I tried just using the > .hddimage but that doesn't boot with VirtualBox :-( > > To be clear, along with the additions above in local.conf, I tried: > $ MACHINE=genericx86 bitbake core-image-base > > Thanks for any ideas > > -- > > Gary Thomas | Consulting for the > MLB Associates |Embedded world > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
