Re: [yocto] [denzil-next BREAKAGE] Silent breakage in denzil-next --- uImage*.dts no longer generated
Hello,
On Wed, Aug 1, 2012 at 8:05 PM, McClintock Matthew-B29882 <
b29...@freescale.com> wrote:
> On Wed, Aug 1, 2012 at 11:56 AM, Scott Garman
> wrote:
> > On 08/01/2012 07:50 AM, Leon Woestenberg wrote:
> >> Disregard the breakage. Local user error; my KERNEL_DEVICETREE missed
> >> the "${S}" prefix.
> >>
>
To summarize the change of behaviour of the patch:
1. Previously (before this patch) the "dtc" compiler was run from the ${S}
directory (linux/git) rather than the ${WORKDIR} directory (linux/),
so a missing ${S} in the KERNEL_DEVICETREE did not break it from compiling.
2. OpenEmbedded did not require the ${S} in KERNEL_DEVICETREE, and custom
device layers (people converting from OE Classic to Core or Poky/Yocto) may
still use it.
3. With this patch, not finding the DTS becomes a silent warning, instead
of an error.
> >
> > The question in my mind right now is whether this change is too
> > risky/change-inducing for a point-release.
>
> I think the was made this way for people using different Linux tree's
> (and Linux versions) specifically which lacked specific device trees
> so switching between them causing problems for specific device tree
> definitions so with this we could just list them all. For example
> p1022ds -> (p1022ds_32b and p1022ds_36b). I could be convinced the
> make this an error or at the very least a bb.warn instead of just an
> echo since it does seem problematic.
>
> Any change should go through master -> denzil
>
>
OK, I get the rationale. My proposal is a solution where the build should
fail if KERNEL_DEVICETREE was specified, but no dts was compiled at all (in
the for loop).
Warn if the dts specified was not an exact match.
Error out if no dts was compiled at all (in the for loop).
Regards,
Leon.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] GLIBCTARGETOS ?= "linux-gnueabi" for PowerPC 440 targets
Hi, On Aug 2, 2012, at 10:09, Khem Raj wrote: > > On Aug 1, 2012, at 7:44 PM, Elvis Dowson wrote: > >> Hi Khem, >> >> On Aug 2, 2012, at 2:37 AM, Khem Raj wrote: >> >>> On Aug 1, 2012, at 9:18 AM, Elvis Dowson wrote: >>> Hi, Perhaps the reason none of my root file system binaries are not working or running is because there is no GLIBCTARGETOS ?= "linux-gnueabi" in my machine/virtex5.conf or local.conf file? >>> >>> you don't need to set it. it should be automatically computed based on libc >>> and arch >>> your problem seems more like console related. Probably you don't have >>> console params >>> set correctly or securetty does not know about your console device. >> >> You're right. After rebuilding it, with that variable set, it made no >> difference in the generated >> binaries, (e.g. generate a tool chain powerpc-poky-linux-gnueabi-gcc) nor >> did it >> change the situation with my having no console login or bash prompt. >> >> The serial port that I am using is ttyS0. There is an entry for ttyS0 under >> /dev in my ramdisk >> , and my /etc/device_table also has an entry for ttyS. >> >> I have also checked that my securetty has an entry for ttyS0. >> >> I have tried all possible option, e.g. try to get inittab running first with >> >> S:2345:respawn:/sbin/getty 9600 ttyS0 >> >> then with >> >> S:2345:respawn:/bin/sh 9600 ttyS0 > > well. When I look into virtext configuration then I see > > SERIAL_CONSOLE ?= "115200 ttyUL0" > > I wonder if you have tried that configuration for serial console. > > I'm working with my local repo so, I have made the changes locally to ttyS0. As soon as I get something working, I send it to Adrian to commit to the repo. The problem I have with ttyS0 also happens with ttyUL0. I've tried with both. Elvis ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] GLIBCTARGETOS ?= "linux-gnueabi" for PowerPC 440 targets
Hi, On Aug 2, 2012, at 10:21 AM, Khem Raj wrote: > > On Aug 1, 2012, at 8:50 PM, McClintock Matthew-B29882 > wrote: > >> Are you running with prelinking? You might try disabling that. It's in >> local.conf under IMAGE_CLASSES I believe. >> > > FWIW I have seen issues with prelink + ppc64 that said ppc32 + prelink has > worked well for me > I've commented out the original USER_CLASSES variable, and removed the image-prelink class, in my local.conf as follows: #USER_CLASSES ?= "buildstats image-mklibs image-prelink" USER_CLASSES ?= "buildstats image-mklibs" Will give it another go, and see what happens. Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 08/01/2012 02:59 PM, maniacbug wrote: Yup, I can verify that denzil builds and runs on Pandaboard with meta-ti 30fb40ebc13614a74c2e237927c60ac43e01d1bc. Haven't tried master, but don't see a need if denzil is going to work. BTW, I did not find it necessary to use meta-oe. Both core-image-base and core-image-sato are working swell, except for sound. Though the latest omap4 kernel has lots of improvements in that area, so I'm in the midst of upgrading it to see if thatfind helps. I got core-image-minimal to build and boot, but not core-image-sato. pulseaudio issues/ couln't build at all. Jim A Yes, this is a rather touch ball of twine with all these layers - they have to be properly aligned to get something that builds. Wow, try it WITHOUT Yocto/Poky. Yocto project seems to add stabilization and documentation to OE, which is about the only thing that makes it possible to get started at all :) Work arounds: * You could checkout meta-ti to something that matches denzil Revision 30fb40ebc13614a74c2e237927c60ac43e01d1bc works for me. I would actually call this the CORRECT solution, not just a workaround. meta-ti should create a denzil-tracking branch from this commit. How in the world you knew how to find that commit number is the part that amazes me This commit was identified and discussed on the meta-ti list as the point of departure from denzil, that's how I found it, myself. m.b ___ 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] [meta-baryon][PATCH 2/2] webmin: remove nfsd check from exports-lib.pl
Hi Kevin, Thanks for tracking this one down! A couple of minor stylistic issues though: On Wednesday 01 August 2012 14:25:02 Kevin Strasser wrote: > YOCTO #1719: Webmin expects the userspace version of nsfd and > attempts to find its pid when applying a new set of nfs exports. > This check fails because baryon is configured to install the > kernelspace version. In result the command that is assigned to > apply_cmd will never be executed, and the contents of /exports > are not successfully exported. The bug reference needs to be in square brackets i.e. [YOCTO #1719], and typically (at least the way I use it) appears after the main body of the commit message. > Signed-off-by: Kevin Strasser > --- > recipes-extended/webmin/files/exports-lib.pl.patch | 32 > recipes-extended/webmin/webmin_1.570.bb| > 3 +- > 2 files changed, 34 insertions(+), 1 deletion(-) > create mode 100644 recipes-extended/webmin/files/exports-lib.pl.patch > > diff --git a/recipes-extended/webmin/files/exports-lib.pl.patch > b/recipes-extended/webmin/files/exports-lib.pl.patch new file mode 100644 > index 000..cdee355 > --- /dev/null > +++ b/recipes-extended/webmin/files/exports-lib.pl.patch > @@ -0,0 +1,32 @@ > +From 7eba4c98c6953fa6ea76c1620d19524bcfa3a576 Mon Sep 17 00:00:00 2001 > +From: Kevin Strasser > +Date: Wed, 1 Aug 2012 11:51:26 -0700 > +Subject: [PATCH] nfs export: remove nfsd check > + > +nfsd runs as a kernel process and does not have a pid. This means > +that the command assigned to apply_cmd will never be executed when > +the user tries to apply changes to nfs exports. > + > +Upstream-Status: Not appropriate [config] Technically this should be "Inappropriate [config]". Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 08/02/2012 08:47 AM, Jim Abernathy wrote: On 08/01/2012 02:59 PM, maniacbug wrote: Yup, I can verify that denzil builds and runs on Pandaboard with meta-ti 30fb40ebc13614a74c2e237927c60ac43e01d1bc. Haven't tried master, but don't see a need if denzil is going to work. BTW, I did not find it necessary to use meta-oe. Both core-image-base and core-image-sato are working swell, except for sound. Though the latest omap4 kernel has lots of improvements in that area, so I'm in the midst of upgrading it to see if thatfind helps. I got core-image-minimal to build and boot, but not core-image-sato. pulseaudio issues/ couln't build at all. Jim A Got around this issue by checking out the denzil branch on meta-ti and poky. then my core-image-sato builds and boots. Anyone know how to get the wireless and HW accelerated video playback to work with the pandaboard and Yocto? maybe a different image? Jim A Yes, this is a rather touch ball of twine with all these layers - they have to be properly aligned to get something that builds. Wow, try it WITHOUT Yocto/Poky. Yocto project seems to add stabilization and documentation to OE, which is about the only thing that makes it possible to get started at all :) Work arounds: * You could checkout meta-ti to something that matches denzil Revision 30fb40ebc13614a74c2e237927c60ac43e01d1bc works for me. I would actually call this the CORRECT solution, not just a workaround. meta-ti should create a denzil-tracking branch from this commit. How in the world you knew how to find that commit number is the part that amazes me This commit was identified and discussed on the meta-ti list as the point of departure from denzil, that's how I found it, myself. m.b ___ 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] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
>-Original Message- >From: Darren Hart [mailto:dvh...@linux.intel.com] >Sent: Wednesday, August 01, 2012 3:58 PM >To: Bodke, Kishore K >Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com >Subject: Re: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine >Created. > >Hi Kishore, > >On 08/01/2012 12:15 PM, kishore.k.bo...@intel.com wrote: >> From: Kishore Bodke >> >> Initial checkin for the new Crystal Forest Machine Branch. >> >> Signed-off-by: Kishore Bodke >> --- >> .../bsp/crystalforest/crystalforest-preempt-rt.scc | 15 + >> .../bsp/crystalforest/crystalforest-standard.scc | 10 >> .../bsp/crystalforest/crystalforest.cfg| 63 >> >> .../bsp/crystalforest/crystalforest.scc| 14 + >> 4 files changed, 102 insertions(+) >> create mode 100644 meta/cfg/kernel- >cache/bsp/crystalforest/crystalforest-preempt-rt.scc >> create mode 100644 meta/cfg/kernel- >cache/bsp/crystalforest/crystalforest-standard.scc >> create mode 100644 meta/cfg/kernel- >cache/bsp/crystalforest/crystalforest.cfg >> create mode 100644 meta/cfg/kernel- >cache/bsp/crystalforest/crystalforest.scc >> >> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt- >rt.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt- >rt.scc >> new file mode 100644 >> index 000..6c250af >> --- /dev/null >> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt- >rt.scc >> @@ -0,0 +1,15 @@ >> +define KMACHINE crystalforest >> +define KTYPE preempt-rt >> +define KARCH x86_64 >> + >> +# no new branch required, re-use the ktypes/preempt-rt branch >> +include ktypes/preempt-rt >> +include bsp/common-pc-64/common-pc-64.scc >> + >> +include crystalforest.scc >> + >> +# default policy for preempt-rt kernels >> +include cfg/usb-mass-storage.scc >> +include cfg/boot-live.scc >> +include features/latencytop/latencytop.scc >> +include features/profiling/profiling.scc >> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest- >standard.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest- >standard.scc >> new file mode 100644 >> index 000..9d24c76 >> --- /dev/null >> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc >> @@ -0,0 +1,10 @@ >> +define KMACHINE crystalforest >> +define KTYPE standard >> +define KARCH x86_64 >> + >> +include bsp/common-pc-64/common-pc-64-standard >> +branch crystalforest >> + >> +include crystalforest.scc >> + >> +# default policy for standard kernels >> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg >b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg >> new file mode 100644 >> index 000..341cc20 >> --- /dev/null >> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg >> @@ -0,0 +1,63 @@ >> +CONFIG_PRINTK=y >> + >> +# Basic hardware support for the box - network, USB, PCI, sound >> +CONFIG_NETDEVICES=y >> +CONFIG_ATA=y >> +CONFIG_ATA_GENERIC=y >> +CONFIG_ATA_SFF=y >> +CONFIG_PCI=y >> +CONFIG_MMC=y >> +CONFIG_MMC_SDHCI=y >> +CONFIG_USB_SUPPORT=y >> +CONFIG_USB=y > >USB support should be pulled in using the various usb scc files Tom >created relatively recently. > >> +CONFIG_USB_ARCH_HAS_EHCI=y >> +CONFIG_R8169=y >> +CONFIG_PATA_SCH=y >> +CONFIG_MMC_SDHCI_PCI=y >> +CONFIG_USB_EHCI_HCD=y >> +CONFIG_PCIEPORTBUS=y >> +CONFIG_NET=y >> +CONFIG_USB_UHCI_HCD=y >> +CONFIG_BLK_DEV_SD=y >> +CONFIG_CHR_DEV_SG=y >> +CONFIG_SOUND=y >> +CONFIG_SND=y >> +CONFIG_SND_HDA_INTEL=y >> + >> +# Make sure these are on, otherwise the bootup won't be fun >> +CONFIG_UNIX=y >> +CONFIG_INET=y >> +CONFIG_MODULES=y >> +CONFIG_SHMEM=y >> +CONFIG_TMPFS=y >> +CONFIG_PACKET=y >> + >> +# These are needed for the Poulsbo kernel modules >> +CONFIG_I2C=y >> +CONFIG_AGP=y >> +CONFIG_VFAT_FS=y > >VFAT_FS is required for Poulsbo kernel modules? > >This would make more sense as a poulsbo.scc and .cfg file. > >> +CONFIG_PM=y >> +CONFIG_FB=y >> +CONFIG_BACKLIGHT_LCD_SUPPORT=y >> +CONFIG_BACKLIGHT_CLASS_DEVICE=y >> +CONFIG_INPUT=y >> +CONFIG_VIDEO_V4L2=y >> +CONFIG_VIDEO_IVTV=y >> +CONFIG_MEDIA_SUPPORT=y >> +CONFIG_VIDEO_CAPTURE_DRIVERS=y >> +CONFIG_VIDEO_DEV=y >> +CONFIG_VIDEO_V4L2_COMMON=y >> +CONFIG_I2C_ALGOBIT=y >> +CONFIG_FB_CFB_COPYAREA=y >> +CONFIG_FB_CFB_IMAGEBLIT=y >> +CONFIG_FB_CFB_FILLRECT=y >> +CONFIG_VIDEO_FB_IVTV=y >> + >> +# Needed for booting (and using) USB memory sticks >> +CONFIG_USB_STORAGE=y >> +CONFIG_BLK_DEV_RAM=y >> +CONFIG_BLK_DEV_LOOP=y >> +CONFIG_BLK_DEV_INITRD=y >> +CONFIG_RD_GZIP=y >> +CONFIG_NLS_CODEPAGE_437=y >> +CONFIG_NLS_ISO8859_1=y > >All this is taken care of with the: > >> +include cfg/usb-mass-storage.scc >> +include cfg/boot-live.scc > >lines which are missing from your non-preempt-rt bsp file. > >> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc >b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc >> new file mode 100644 >> index 000..ff45107 >> --- /dev/null >> +++ b/meta/cfg/kernel
[yocto] [PATCH 0/1] Fixes for meta-intel/denzil
From: Nitin A Kamble I found the emgd recipe was failing due to packaging QA errors on the denzil branch. this pull request fixes it. Thanks, Nitin The following changes since commit a1a32b20ee7677f05cc01ab7428f256127657e98: fri2: Update README (2012-07-30 16:24:01 -0700) are available in the git repository at: git://git.yoctoproject.org/meta-intel-contrib nitin/denzil http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/denzil Nitin A Kamble (1): emgd-driver-bin_1.14: avoid QA warnings .../xorg-xserver/emgd-driver-bin_1.14.bb | 92 1 files changed, 92 insertions(+), 0 deletions(-) create mode 100644 common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] emgd-driver-bin_1.14: avoid QA warnings
From: Nitin A Kamble
Avoid these warning/errors:
ERROR: QA Issue: non debug package contains .debug directory: emgd-driver-bin
path
/work/core2-poky-linux/emgd-driver-bin-1.14-r0/packages-split/emgd-driver-bin/usr/lib/gstreamer-0.10/.debug/libgstmixvideoplugin.so
ERROR: QA Issue: non debug package contains .debug directory: emgd-driver-bin
path
/work/core2-poky-linux/emgd-driver-bin-1.14-r0/packages-split/emgd-driver-bin/usr/lib/gstreamer-0.10/.debug/libgstvaplugin.so
Signed-off-by: Nitin A Kamble
---
.../xorg-xserver/emgd-driver-bin_1.14.bb | 92
1 files changed, 92 insertions(+), 0 deletions(-)
create mode 100644 common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
diff --git a/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
b/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
new file mode 100644
index 000..53d70dc
--- /dev/null
+++ b/common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb
@@ -0,0 +1,92 @@
+SUMMARY = "EMGD 1.10 xserver binaries"
+DESCRIPTION = "EMGD 1.10 includes some userspace binaries that use non-free \
+licensing, which are now available via a non-click-through downloadable \
+tarball, and is what this recipe now uses. Since it is a non-free license, \
+this recipe is marked as 'License_emgd-driver-bin_1.10' and you need to add \
+to LICENSE_FLAGS_WHITELIST += \"License_emgd-driver-bin_1.10\" to your \
+local.conf in order to enable it in a build."
+LICENSE = "Intel-binary-only"
+LICENSE_FLAGS = "license_${PN}_${PV}"
+PR = "r0"
+
+EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
+EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
+EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"
+
+LIC_FILES_CHKSUM =
"file://${WORKDIR}/${EMGD_LIC_DIR}/License.txt;md5=b54f01caaf8483b3cb60c0c40f2bf22d"
+
+DEPENDS = "rpm-native xz-native"
+
+SRC_URI =
"https://edc.intel.com/App_Shared/Downloads/LIN_IEMGD_1_14_GOLD_2443.tgz";
+
+SRC_URI[md5sum] = "e4a38d9efa0b086ae21b68145c4db4e9"
+SRC_URI[sha256sum] =
"acea5f0f93a31553553428623c007d7ed0c604cf715fd87dfe075751da4be548"
+
+# These are closed binaries generated elsewhere so don't check ldflags
+INSANE_SKIP_${PN} = "ldflags"
+
+FILES_${PN} += "${libdir}/dri ${libdir}/gstreamer-0.10
${libdir}/xorg/modules/drivers"
+FILES_${PN}-dev += "${libdir}/dri ${libdir}/xorg/modules/drivers"
+FILES_${PN}-dbg += "${libdir}/xorg/modules/drivers/.debug ${libdir}/dri/.debug
${libdir}/gstreamer-0.10/.debug"
+
+S = "${WORKDIR}/${EMGD_RPM_DIR}"
+
+do_install () {
+# A gstreamer VA buffer library
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-vabuffer*.rpm | cpio -id
+
+# MIX Common contains common classes, datatype, header files used by other
MIX components
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixcommon*.rpm | cpio -id
+
+# MIX Video Bitstream Parser is an user library interface for various
video format bitstream parsing
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvbp*.rpm | cpio -id
+
+# MIX Video is an user library interface for various video codecs
available on the platform.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/mixvideo*.rpm | cpio -id
+
+install -d -m 0755
${D}${libdir}/gstreamer-0.10
+install -m 0755 ${S}/usr/lib/*${D}${libdir}/
+
+# A gstreamer plugin that uses MIX Video for hardware accelerated video
decoding and rendering.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-mixvideo*.rpm | cpio -id
+
+# A collection of gstreamer plugins that uses VA libraries for hardware
accelerated video rendering and text overlay.
+rpm2cpio ${S}/${EMGD_VIDEO_PLUGIN_DIR}/gst-plugins-va*.rpm | cpio -id
+
+install -m 0755 ${S}/usr/lib/gstreamer-0.10/*
${D}${libdir}/gstreamer-0.10/
+
+# EMGD runtime graphics libraries
+rpm2cpio ${S}/emgd-bin*.rpm | xz -d | cpio -id
+
+install -d -m 0755${D}${libdir}/dri
+install -d -m 0755
${D}${libdir}/xorg/modules/drivers
+install -d -m 0755${D}${sysconfdir}
+install -d -m 0755${D}${mandir}/man4
+install -m 0755 ${S}/usr/lib/*.so.* ${D}${libdir}/
+install -m 0755 ${S}/usr/lib/dri/*${D}${libdir}/dri/
+install -m 0755 ${S}/usr/lib/xorg/modules/drivers/*
${D}${libdir}/xorg/modules/drivers/
+install -m 0755 ${S}/etc/*${D}${sysconfdir}/
+install -m 0755 ${S}/usr/share/man/man4/* ${D}${mandir}/man4/
+
+# Khronos development headers needed for EGL, OpenGL-ES, and OpenVG
development
+rpm2cpio ${S}/emgd-devel*.rpm | xz -d | cpio -id
+
+install -d -m 0755${D}${includedir}/EGL
+install -m 0755 ${S}/usr/include/EGL/*.h
${D}${includedir}/EGL/
+install -d -m 0755
${D}${includedir}/GLES
+
Re: [yocto] GLIBCTARGETOS ?= "linux-gnueabi" for PowerPC 440 targets
Hi, On Aug 2, 2012, at 10:21 AM, Khem Raj wrote: > > On Aug 1, 2012, at 8:50 PM, McClintock Matthew-B29882 > wrote: > >> Are you running with prelinking? You might try disabling that. It's in >> local.conf under IMAGE_CLASSES I believe. >> > > FWIW I have seen issues with prelink + ppc64 that said ppc32 + prelink has > worked well for me > I tried rebuilding the entire yocto build without image-prelink, and still no change, I still do not get a root login prompt. Any suggestions on what else I can try? zImage starting: loaded at 0x0080 (sp: 0x00d8afb0) Allocating 0x540e0c bytes for kernel ... gunzipping (0x <- 0x0080f000:0x00a17dd6)...done 0x4235c0 bytes Attached initrd image at 0x00a18000-0x00d89ddc initrd head: 0x1f8b0808 Linux/PowerPC load: console=ttyS0,9600n8 ip=off root=/dev/ram rw rootwait Finalizing device tree... flat tree at 0xd970e0 PM: Adding info for No Bus:ttyv9 [0.477306] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.482790] 83e0.serial: ttyS0 at MMIO 0x83e01003 (irq = 20) is a 16550 [0.678224] console [ttyS0] enabled [0.742215] brd: module loaded [0.789116] loop: module loaded [0.826377] xsysace 8360.sysace: Xilinx SystemACE revision 1.0.12 [0.903095] xsysace 8360.sysace: No CF in slot [0.962077] Xilinx SystemACE device driver, major=254 [1.023122] xilinx_emaclite 8100.ethernet: Device Tree Probing [1.096656] xilinx_emaclite 8100.ethernet: error registering MDIO bus [1.177745] xilinx_emaclite 8100.ethernet: MAC address is now 00:0a:35:b7:78:00 [1.271437] xilinx_emaclite 8100.ethernet: Xilinx EmacLite at 0x8100 mapped to 0xD10A7 [1.386354] xilinx_ps2 8148.ps2: Device Tree Probing 'ps2' [1.455652] xilinx_ps2 8148.ps2: Xilinx PS2 at 0x8148 mapped to 0xd1036000, irq=22 [1.555028] xilinx_ps2 81481000.ps2: Device Tree Probing 'ps2' [1.624704] xilinx_ps2 81481000.ps2: Xilinx PS2 at 0x81481000 mapped to 0xd1038000, irq=23 [1.725185] mousedev: PS/2 mouse device common for all mice [1.792535] i2c /dev entries driver [1.834242] Device Tree Probing 'i2c' [1.878524] xilinx-iic #0 at 0x8160 mapped to 0xD10C, irq=18 [1.956082] TCP cubic registered [1.993980] NET: Registered protocol family 17 [2.790410] atkbd serio0: keyboard reset failed on xilinxps2/serio at 8148 [3.274683] RAMDISK: gzip image found at block 0 [3.791700] atkbd serio1: Frame/parity error: 02 [3.858598] input: AT Raw Set 2 keyboard as /devices/plb.0/xps-ps2.1/81481000.ps2/serio1/input/in0 [4.234835] VFS: Mounted root (ext2 filesystem) on device 1:0. [4.305005] Freeing unused kernel memory: 152k freed Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] Fixes for meta-intel/denzil
On Wed, 2012-08-01 at 09:46 -0700, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble > > I found the emgd recipe was failing due to packaging QA errors on the denzil > branch. > this pull request fixes it. > Hmm, why are you upgrading denzil to emgd 1.14? Tom > Thanks, > Nitin > > The following changes since commit a1a32b20ee7677f05cc01ab7428f256127657e98: > > fri2: Update README (2012-07-30 16:24:01 -0700) > > are available in the git repository at: > git://git.yoctoproject.org/meta-intel-contrib nitin/denzil > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/denzil > > Nitin A Kamble (1): > emgd-driver-bin_1.14: avoid QA warnings > > .../xorg-xserver/emgd-driver-bin_1.14.bb | 92 > > 1 files changed, 92 insertions(+), 0 deletions(-) > create mode 100644 > common/recipes-graphics/xorg-xserver/emgd-driver-bin_1.14.bb > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
> Got around this issue by checking out the denzil branch on meta-ti and > poky. then my core-image-sato builds and boots. Right, that is what I was going to suggest. One of us should fix the pulseaudio issue on master and send in a patch. > Anyone know how to get the wireless and HW accelerated video playback to > work with the pandaboard and Yocto? maybe a different image? meta-ti list is probably going to be the place to find this out. Or at least find clues. Unfortunately, it seems that there is not a pandaboard expert in the Yocto house. The meta-ti layer has been extracted from Angstrom, so there seem to be plenty dependencies directly on OE. Often when building more hardware-specific recipies, these dependencies crop up. So Yocto on Pandaboard is definitely still a work in progress. I have gotten video to work by porting the libav recipe from OE. Happy to send it to you if you want to try. There is no evidence to suggest this is hardware-accellerated. HOWEVER, it does play 2Mbps video without stuttering. So from my perspective, whether it's hw accellerated is not important :) The downside is that AUDIO is working hardly at all. This is my current challenge, and I'll definitely report progress to the meta-ti list. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] webmin: remove nfsd check from exports-lib.pl
Webmin expects the userspace version of nsfd and attempts to
find its pid when applying a new set of nfs exports. This check
fails because baryon is configured to install the kernelspace
version. In result the command that is assigned to apply_cmd
will never be executed, and the contents of /exports are not
successfully exported.
Fixes [YOCTO #1719]
Signed-off-by: Kevin Strasser
---
recipes-extended/webmin/files/exports-lib.pl.patch | 32
recipes-extended/webmin/webmin_1.570.bb|3 +-
2 files changed, 34 insertions(+), 1 deletion(-)
create mode 100644 recipes-extended/webmin/files/exports-lib.pl.patch
diff --git a/recipes-extended/webmin/files/exports-lib.pl.patch
b/recipes-extended/webmin/files/exports-lib.pl.patch
new file mode 100644
index 000..140ae7e
--- /dev/null
+++ b/recipes-extended/webmin/files/exports-lib.pl.patch
@@ -0,0 +1,32 @@
+From 7eba4c98c6953fa6ea76c1620d19524bcfa3a576 Mon Sep 17 00:00:00 2001
+From: Kevin Strasser
+Date: Wed, 1 Aug 2012 11:51:26 -0700
+Subject: [PATCH] nfs export: remove nfsd check
+
+nfsd runs as a kernel process and does not have a pid. This means
+that the command assigned to apply_cmd will never be executed when
+the user tries to apply changes to nfs exports.
+
+Upstream-Status: Inappropriate [config]
+
+Signed-off-by: Kevin Strasser
+---
+ exports/exports-lib.pl |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/exports/exports-lib.pl b/exports/exports-lib.pl
+index 22891c0..1c67494 100755
+--- a/exports/exports-lib.pl
b/exports/exports-lib.pl
+@@ -273,7 +273,7 @@ return !&has_command("rpc.nfsd") && !&has_command("nfsd")
&&
+ sub restart_mountd
+ {
+ # Try exportfs -r first
+-if ($config{'apply_cmd'} && &find_byname("nfsd") && &find_byname("mountd")) {
++if ($config{'apply_cmd'} && &find_byname("mountd")) {
+ local $out = &backquote_logged("$config{'apply_cmd'} 2>&1 https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
On 08/02/2012 01:07 PM, maniacbug wrote: Got around this issue by checking out the denzil branch on meta-ti and poky. then my core-image-sato builds and boots. Right, that is what I was going to suggest. One of us should fix the pulseaudio issue on master and send in a patch. probably going to be you. that's a long ways away from my skill level. :-) Anyone know how to get the wireless and HW accelerated video playback to work with the pandaboard and Yocto? maybe a different image? meta-ti list is probably going to be the place to find this out. Or at least find clues. Unfortunately, it seems that there is not a pandaboard expert in the Yocto house. The meta-ti layer has been extracted from Angstrom, so there seem to be plenty dependencies directly on OE. Often when building more hardware-specific recipies, these dependencies crop up. So Yocto on Pandaboard is definitely still a work in progress. I have gotten video to work by porting the libav recipe from OE. Happy to send it to you if you want to try. There is no evidence to suggest this is hardware-accellerated. HOWEVER, it does play 2Mbps video without stuttering. So from my perspective, whether it's hw accellerated is not important :) I would say it's hardware accelerated because video under Ubuntu is like a slide show. 2-3 sections between frames. I don't think HW acceleration was working there either. The downside is that AUDIO is working hardly at all. This is my current challenge, and I'll definitely report progress to the meta-ti list. I need to test, but on Ubuntu 12.04 with the OMAP4 extras, I had audio only working via HDMI audio. I'll test to see what happens on Yocto. ___ 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] [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch
From: Kishore Bodke Hi, This is a revised patch set is for creating the new Crystal Forest Machine. Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset. This machine is based on standard/default/common-pc-64. Please create a new branch called standard/default/common-pc-64/crystalforest for linux-yocto-3.4 kernel and push this new meta branch. Thanks Kishore. The following changes since commit 459165c1dd61c4e843c36e6a1abeb30949a20ba7: kconf: add 8250 Kconfig to hardware listing audit (2012-07-26 16:23:26 -0400) are available in the git repository at: git://git.pokylinux.org/linux-yocto-2.6.37-contrib kishore/meta-crystalforest http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/meta-crystalforest Kishore Bodke (1): meta: Crystal Forest Machine Created. .../bsp/crystalforest/crystalforest-preempt-rt.scc |9 ++ .../bsp/crystalforest/crystalforest-standard.scc |8 + .../bsp/crystalforest/crystalforest.cfg| 32 .../bsp/crystalforest/crystalforest.scc| 23 ++ 4 files changed, 72 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
From: Kishore Bodke Initial checkin for the new Crystal Forest Machine Branch. This Machine is based on Sandybridge CPU and Cave Creek Chipset. Signed-off-by: Kishore Bodke --- .../bsp/crystalforest/crystalforest-preempt-rt.scc |9 ++ .../bsp/crystalforest/crystalforest-standard.scc |8 + .../bsp/crystalforest/crystalforest.cfg| 32 .../bsp/crystalforest/crystalforest.scc| 23 ++ 4 files changed, 72 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg create mode 100644 meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc new file mode 100644 index 000..88e9b1a --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc @@ -0,0 +1,9 @@ +define KMACHINE crystalforest +define KTYPE preempt-rt +define KARCH x86_64 + +# no new branch required, re-use the ktypes/preempt-rt branch +include ktypes/preempt-rt +include bsp/common-pc-64/common-pc-64.scc + +include crystalforest.scc diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc new file mode 100644 index 000..2935387 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE crystalforest +define KTYPE standard +define KARCH x86_64 + +include bsp/common-pc-64/common-pc-64-standard +branch crystalforest + +include crystalforest.scc diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg new file mode 100644 index 000..542f600 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg @@ -0,0 +1,32 @@ +CONFIG_PRINTK=y + +# Basic hardware support for the box - network, PCI, sound +CONFIG_NETDEVICES=y +CONFIG_ATA=y +CONFIG_ATA_GENERIC=y +CONFIG_ATA_SFF=y +CONFIG_PCI=y +CONFIG_MMC=y +CONFIG_MMC_SDHCI=y +CONFIG_R8169=y +CONFIG_PATA_SCH=y +CONFIG_MMC_SDHCI_PCI=y +CONFIG_PCIEPORTBUS=y +CONFIG_NET=y +CONFIG_CHR_DEV_SG=y +CONFIG_SOUND=y +CONFIG_SND=y +CONFIG_SND_HDA_INTEL=y + +# Make sure these are on, otherwise the bootup won't be fun +CONFIG_UNIX=y +CONFIG_INET=y +CONFIG_MODULES=y +CONFIG_SHMEM=y +CONFIG_TMPFS=y +CONFIG_PACKET=y + +CONFIG_I2C=y +CONFIG_AGP=y +CONFIG_PM=y +CONFIG_INPUT=y diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc new file mode 100644 index 000..140a4d5 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc @@ -0,0 +1,23 @@ +kconf hardware crystalforest.cfg + +include cfg/x86_64.scc +include cfg/8250.scc + +include features/i915/i915.scc +include features/power/intel.scc + +#These are required features for Intel DPDK Support + +include features/uio/uio.scc +include features/hugetlb/hugetlb.scc +include features/ixgbe/ixgbe.scc +include features/igb/igb.scc + + +include features/latencytop/latencytop.scc +include features/profiling/profiling.scc +include features/usb/xhci-hcd.scc +include features/usb/ehci-hcd.scc +include features/usb/ohci-hcd.scc +include cfg/usb-mass-storage.scc +include cfg/boot-live.scc -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
Looks a lot better. One question still pending from my previous review though: On 08/02/2012 11:35 AM, kishore.k.bo...@intel.com wrote: > diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc > b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc > new file mode 100644 > index 000..140a4d5 > --- /dev/null > +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc > @@ -0,0 +1,23 @@ > +kconf hardware crystalforest.cfg > + > +include cfg/x86_64.scc > +include cfg/8250.scc > + > +include features/i915/i915.scc Is this (i915) required for the Poulsbo graphics? -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error pandaboard on master
Hi, On Aug 2, 2012, at 9:21 PM, Jim Abernathy wrote: >> One of us should fix the pulseaudio issue on master and send in a patch. > probably going to be you. that's a long ways away from my skill level. :-) You can find information about the linux git repos for OMAP4 here: http://www.omappedia.com/wiki/LinuxOmapKernelGitTrees For audio they have a specific repo, along with the name of a maintainer Audio ASoCALSA tree https://gitorious.org/omap-audio git://gitorious.org/omap-audio/linux-audio.git ASoC DSP framework You can try to use the above repo, in conjunction with the following repo, to see if you can get things working: ARM Core kernel Core Kernel Linus' tree http://git.gitorious.org/omap-sw-develoment/linux-omap-dev.git git://gitorious.org/omap-sw-develoment/linux-omap-dev.git Please note that I have not tried the above repos, but just thought I'd dig out the information for you.You probably need to hunt around a bit to locate the right repo. The following gitorious project also contains some work on the Pandaboard x-loader, bootloader and kernel. Perhaps you might find some audio patches and support in it. http://gitorious.org/pandaboard I see one patch in x-loader for audio here http://gitorious.org/+pandaboard/x-loader/pandaboard-x-loader/commit/746f93150545c4d4f3ba359046a5c7249094309a So, with a bit of time, and patience, you should be able to build and try each git resource, till you find one that works, extract the audio related patches, and apply it to the yocto bsp or kernel recipes. I've got a Pandaboard with me, but I'm focussing on getting my Xilinx Virtex 5 FPGA up and running with yocto at the moment. It's been over a year or so since the Pandaboard has been released, so you should be able to extract the patch from one of the TI repos, or an Android kernel repository. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
>-Original Message- >From: Darren Hart [mailto:dvh...@linux.intel.com] >Sent: Thursday, August 02, 2012 1:00 PM >To: Bodke, Kishore K >Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com >Subject: Re: [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created. > >Looks a lot better. One question still pending from my previous review >though: > >On 08/02/2012 11:35 AM, kishore.k.bo...@intel.com wrote: > >> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc >b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc >> new file mode 100644 >> index 000..140a4d5 >> --- /dev/null >> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc >> @@ -0,0 +1,23 @@ >> +kconf hardware crystalforest.cfg >> + >> +include cfg/x86_64.scc >> +include cfg/8250.scc >> + >> +include features/i915/i915.scc > >Is this (i915) required for the Poulsbo graphics? I am not quite sure on this. Thanks Kishore. > >-- >Darren Hart >Intel Open Source Technology Center >Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] 1.3 Milestone 2 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Hello, We are pleased to announce the second milestone of the coming release of Yocto 1.3. This milestone release is available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/poky-yocto-1.3-m2.tar.bz2 or http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/poky-yocto-1.3-m2.tar.bz2 Additional tarballs for meta-qt3 and the eclipse plugin are available at: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/eclipse-poky-yocto-1.3-m2.tar.bz2 http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/meta-qt3-yocto-1.3-m2.tar.bz2 with mirror locations at: http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/eclipse-poky-yocto-1.3-m2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/meta-qt3-yocto-1.3-m2.tar.bz2 For information on 1.3 M2 test results see: http://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report Thank you everyone for all the hard work. Elizabeth Flanagan Yocto Build and Release - yocto-1.3-m2 Errata - Release Name: eclipse-poky-yocto-1.3-m2 Branch: 1.3_M2 Tag: 1.3_M2.final Hash: 4989ec8ba8760bf12def6990e91f3d8881af6e25 md5: e11c4dc68a124ee2af0aa7fc4260d376 eclipse-poky-yocto-1.3-m2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/eclipse-poky-yocto-1.3-m2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/eclipse-poky-yocto-1.3-m2.tar.bz2 Release Name: meta-qt3-yocto-1.3-m2 Branch: 1.3_M2 Tag: 1.3_M2.final Hash: f8475d5c5935695d4d1dfff1d7be30f49e162094 md5: c3bb68408016c996142b7bb8f49051f0 meta-qt3-yocto-1.3-m2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/meta-qt3-yocto-1.3-m2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/meta-qt3-yocto-1.3-m2.tar.bz2 Release Name: poky-yocto-1.3-m2 Branch: 1.3_M2 Tag: 1.3_M2.final Hash: 20dc7d276682defc29b3a64ccf9fb87b4cf4fb79 md5: 7ba1063aa612ec440bc8fa3ad93b2f9f poky-yocto-1.3-m2.tar.bz2 Download Locations: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.3-m2/poky-yocto-1.3-m2.tar.bz2 http://mirrors.kernel.org/yocto/yocto/milestones/yocto-1.3-m2/poky-yocto-1.3-m2.tar.bz2 - Known Issues - Bug 2646 Windows switching failure Bug 2415 connman doesn't provide a 3g configuration utility Bug 2559 [yocto-bsp]X can't start in sato image built by yocto-bsp tool Bug 2783 do_bootdirectdisk fail when build build-appliance-image on Ubuntu11.10 X86_64 platform Bug 2589 [yocto-kernel] fail to build core-image-sato when add patch into the kernel Bug 2590 [multilib]do_rootfs failed for lib32-connman-gnome with ipk Bug 2571 [multilib] no provider for lib32/lib64-lsbinitscripts Bug 2572 [multilib] failed dependency for util-linux with multilib build Bug 2780 btrfs format image build fails due to kernel do_patch failure Bug 1452 32bit kernel generated oprofile data file can not be read by remote 64bit operation Bug 1908 pkg.m4 is missing in package pkgconfig-nativesdk again Bug 2534 [Regression]Glxgears failed on qemuarm/mips/ppc on Ubuntu 11.10 64bit Bug 2577 Segmentation fault on qemuarm from /usr/lib/libust.so.0 Bug 2802 [Hob]Deploy image button not available Bug 2695 [HOB]Settings are not saved - Features - 1. ADT support for latest Eclipse Juno release. 2. Support for TCF after refactoring for TCF 1.0. 3. Enhancement to 'bitbake -g' to print all packages to be built. 4. Generating charts for build statistics and profiling. 5. HOB improvement such as image drop down list customization and many bug fixes. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iQEcBAEBAgAGBQJQGuTJAAoJEEyK+E/MEkQPOWwIAJ2lcZ4Q7hkTQBFTWsB4ynB1 dvPIODB/0/KdTH/6iCIe2zQhIDnkNZgMCCFYtmt4SoYrmKCRLyzmOvHDDneo+yPj OYpRDhFooXTHiyaz9qomPlEwiDDgme044mL01ZgovpW+4Rf6IwdqjFrnMRIaqFOP n64nCxAo0OFyQh6QdO2J2BvHQtHLkxH6eD3exHsBeTKEgPaJroDZL+d+jDt4Xt2z x8wGFI2DPNLrQQVmJySOy2I6vC/oGw6XC44e9JGGZhFLCB7vKXykFPUGuMnIZtlV gfryAB2N9hsN4D6Lx19CAobpoTytMRkWKp3SBZJImEEwwDXr52JVH/KkZ2HZqJk= =THyc -END PGP SIGNATURE- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Hey where is pythonnative.bbclass
Hey I am using yocto version 7, with cownbay bsp. I am adding layers from openembedded. Would anyone know here is the pythonnative.bbclass, some meta-oe depends on it. Thanks, Aditya ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Hey where is pythonnative.bbclass
On Thu, Aug 2, 2012 at 5:55 PM, Aditya Gandhi wrote: > I am adding layers from openembedded. Would anyone know here is the > pythonnative.bbclass, some meta-oe depends on it. oe-core. -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Pandaboard indeed does not boot on master
As discussed in a previous thread (https://lists.yoctoproject.org/pipermail/yocto/2012-July/010540.html), pandaboard images fail to boot now. I also verified this. Releases after denzil will drop support for pandaboard in the current state. I filed a bug, 2884 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=2884) against this issue. It would be great to see a fix. Looks like the suggestion is to use an earlier GCC version for this hardware. m.b ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Switching between stable gcc versions
Hi, In poky master, the current version of gcc is 4.7.2. If I have a situation, where I need to revert back to using gcc-4.5.1, how can I do this cleanly? Perhaps some of the issues that I'm facing with getting my root filesystem image booting on my Xilinx ML507 development board (Virtex 5 PowerPC 440 processor) might be related the new gcc-4.7.2 release. At the moment, I've had to delete my entire build, switch to the bernard-5.0.2 tag, and then attempt to try and build a new rootfilesystem. Others have successfully built and got linux running on my target board, with bernard-5.0, about a year ago. So, if it does indeed turn out that I need to use an older version of gcc, for my target, what should I do, to continue working with the poky master repo, but only use the older gcc-4.5.1 release? Some options that I can think of are: a. Reintroduce the older gcc-4.5.1 recipes in a local branch, but that would mean others would not be able to reproduce my work on their machines. b. Use bernard-5.0.2 to build the toolchain, and set things up so that it uses that as an external toolchain. I don't think both the options are elegant, so if someone could offer any suggestions it would be great. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
