Re: [meta-freescale] add user in image recipe
I just tried to add a user in the same way the root password is changed : with
a ROOTFS_POSTPROCESS_COMMAND like this :
ROOTFS_POSTPROCESS_COMMAND += add_a_user;
add_a_user(){
useradd -p
'\$6\$53uYm/0Fnll\$Nc0RbHSvqRrd63Tw98TO3V1n25ORK9oR4QHqRIriXzLy0il/7.LIacX7mz7RJ1tdPIWiCJLNyQa7dKBNURqEg1'
fstuser;
}
When baking I get this (the last bit of the log.do_rootfs):
NOTE: Executing set_root_password ...
DEBUG: Executing shell function set_root_password
DEBUG: Shell function set_root_password finished
NOTE: Executing add_a_user ...
DEBUG: Executing shell function add_a_user
useradd: /etc/passwd.15710: Permission denied
useradd: cannot lock /etc/passwd; try again later.
WARNING: exit code 1 from a shell command.
DEBUG: Python function do_rootfs finished
ERROR: Function failed: add_a_user (log file is located at
/home/theuser/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/core-at-image-minimal/1.0-r0/temp/log.do_rootfs.9264)
Maybe the initial method with the EXTRA_USER_PARAMS failed because of the same
reason (but didn't break baking) ?
Any ideas to that ?
Thank you
-Ursprüngliche Nachricht-
Von: Heise, Matthias
Gesendet: Donnerstag, 27. November 2014 08:53
An: 'Uhl, Joe'; 'meta-freescale@yoctoproject.org'
Betreff: AW: [meta-freescale] add user in image recipe
Hi,
any more ideas regarding the useradd ? it is still not working from within
recipe
-Ursprüngliche Nachricht-
Von: Heise, Matthias
Gesendet: Dienstag, 18. November 2014 14:02
An: 'Uhl, Joe'; meta-freescale@yoctoproject.org
Betreff: AW: [meta-freescale] default root password or password request
Tried that, no difference
Try adding single quotes around the encrypted password like this:
EXTRA_USER_PARAMS = useradd -p
'\$6\$53uYm/0Fnll\$Nc0RbHSvqRrd63Tw98TO3V1n25ORK9oR4QHqRIriXzLy0il/7.LIacX7mz7RJ1tdPIWiCJLNyQa7dKBNURqEg1'
fstuser;
Confidentiality Requirement: This communication, including any attachment(s),
may contain confidential information and is for the sole use of the intended
recipient(s). If you are not the intended recipient, you are hereby notified
that you have received this communication in error and any unauthorized review,
use, disclosure, dissemination, distribution or copying of it or its contents
is strictly prohibited. If you have received this communication in error,
please notify the sender immediately by telephone or e-mail and destroy all
copies of this communication and any attachments.
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] save kernel configuration
Hi Mat, On 27 Nov 2014, at 07:46, matthias.he...@atlas-elektronik.com matthias.he...@atlas-elektronik.com wrote: Hi there, when I’m turning options on and off in menuconfig these changes are usually saved in the .config file, which resides (in my case)in /build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboardd/3.10.17-r0/git , right ? As this configuration is obviously downloaded from git, I’ve got a few questions: 1. Is this configuration integral part of (in this case) the linux-wandboard-3.10.17, so if I change the configuration the version must be changed ? 2. Which purpose does the defconfig file in /sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard-3.10.17 have ? 3. Or is the defconfig file copied, changed by recipe (linux-wandboard_3.10.17.bb, f.e. LOCALVERSION ) and if I change something and want to include this into the image recipe I copy the tweaked .config file into a new defconfig ? Or how would be the procedure ? 1. The version number is simply the kernel version that is being used - configuration just selects which features are exposed; 2. The defconfig is the default configuration that will be used as the .config when the kernel is built for the wandboard; 3. Any kernel changes that are requested else where (e.g. configuration fragments, below) modify what is in .config before the build takes place. Any changes you make using menuconfig will be lost as they are stored in the work area. If you want to be able to reapply changes you probably want to look at using configuration fragments. I would start by reading the section Creating Configuration Fragments in the documentation (www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html). Configuration fragments are much easier to manage and will apply to any kernel version that supports the option(s). -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm-extra][PATCH] broadcom-nvram-config: add cubox-i
Since I am not knowledgeable about the Broadcom hardware, I asked around. As a conclusion, it looks fine, except for two things: * ccode=CN should use =ALL instead. This is the parameter that specifies which frequency spectrum to scan. The spectrum in EU and US are different than in CN. Perhaps this should be configurable. * MACHINE_FIRMWARE_append_mx6 = linux-firmware-ath6k should be changed as well. Something like linux-firmware-brcmfmac would make more sense, if such a package exists. On 2014-11-13 19:53, Benjamin Cohen wrote: - add bcm4330 nvram config for cubox-i - add bcm4330-nvram-config to MACHINE_EXTRA_RRECOMMENDS for cubox-i Signed-off-by: Benjamin Cohen ben...@notk.org --- conf/machine/cubox-i.conf |4 ++ .../broadcom-nvram-config/bcm4330-nvram-config.bb |2 +- .../files/cubox-i/brcmfmac4330-sdio.txt| 40 3 files changed, 45 insertions(+), 1 deletion(-) create mode 100644 recipes-bsp/broadcom-nvram-config/files/cubox-i/brcmfmac4330-sdio.txt diff --git a/conf/machine/cubox-i.conf b/conf/machine/cubox-i.conf index 6c67c19..fa90d7c 100644 --- a/conf/machine/cubox-i.conf +++ b/conf/machine/cubox-i.conf @@ -33,4 +33,8 @@ KERNEL_DEVICETREE = imx6dl-cubox-i.dtb imx6q-cubox-i.dtb imx6dl-hummingboard.dt MACHINE_FEATURES += pci wifi bluetooth alsa bluetooth irda serial usbhost wifi MACHINE_FIRMWARE_append_mx6 = linux-firmware-ath6k +MACHINE_EXTRA_RRECOMMENDS += \ + bcm4330-nvram-config \ + + SERIAL_CONSOLE = 115200 ttymxc0 diff --git a/recipes-bsp/broadcom-nvram-config/bcm4330-nvram-config.bb b/recipes-bsp/broadcom-nvram-config/bcm4330-nvram-config.bb index 592cfc9..d5e7ebb 100644 --- a/recipes-bsp/broadcom-nvram-config/bcm4330-nvram-config.bb +++ b/recipes-bsp/broadcom-nvram-config/bcm4330-nvram-config.bb @@ -5,4 +5,4 @@ include broadcom-nvram-config.inc CHIP_MODEL = 4330 -COMPATIBLE_MACHINE = (nitrogen6x-lite|wandboard-dual|wandboard-quad) +COMPATIBLE_MACHINE = (nitrogen6x-lite|wandboard-dual|wandboard-quad|cubox-i) diff --git a/recipes-bsp/broadcom-nvram-config/files/cubox-i/brcmfmac4330-sdio.txt b/recipes-bsp/broadcom-nvram-config/files/cubox-i/brcmfmac4330-sdio.txt new file mode 100644 index 000..9546246 --- /dev/null +++ b/recipes-bsp/broadcom-nvram-config/files/cubox-i/brcmfmac4330-sdio.txt @@ -0,0 +1,40 @@ +# bcm94330wlsdgb.txt +manfid=0x2d0 +prodid=0x0552 +vendid=0x14e4 +devid=0x4360 +boardtype=0x0552 +boardrev=0x11 +# this design has 2.4GHz SP3T switch +boardflags=0x00080200 +nocrc=1 +xtalfreq=37400 +boardnum=22 +macaddr=00:90:4c:c5:12:38 +ag0=255 +aa2g=1 +ccode=CN +pa0b0=0x14d0 +pa0b1=0xfd98 +pa0b2=0xff78 +rssismf2g=0xa +rssismc2g=0x3 +rssisav2g=0x7 +maxp2ga0=0x50 +sromrev=3 +il0macaddr=00:90:4c:c5:12:38 +wl0id=0x431b +cckPwrOffset=5 +ofdm2gpo=0x +mcs2gpo0=0x +mcs2gpo1=0x +swctrlmap_2g=0x04040404,0x02020202,0x02020404,0x10202,0x1ff +swctrlmap_5g=0x00100010,0x00280020,0x00200010,0x14202,0x2f8 +rfreg033=0x19 +rfreg033_cck=0x1f +dacrate2g=160 +txalpfbyp2g=1 +bphyscale=17 +cckPwrIdxCorr=-15 +pacalidx2g=45 +txgaintbl=1 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Status of imx28evk recipes/images
On Tue, Nov 25, 2014 at 5:47 PM, Simone cjb.sw.nos...@gmail.com wrote: I mean, we work also on imx53qsb board and we know that the last working kernel is 2.6.35.3 So, let's redefine the question: which is the latest working kernel for this board? The latest working kernel for this board is linux-next from kernel.org. It´s not even supported in FSL Community BSP as we only include stable versions (but it´s a perfectly working kernel) The question you want to do is What is the latest release from Freescale for imx28evk. And for this question you must go to freescale.com: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MCIMX28EVKJfpsp=1tab=Design_Tools_Tab# And, only to make it clear: http://freescale.github.io/doc/release-notes/1.7/#what-the-project-name-is-not Thank you, but I'm still missing something.. I suppose that linux-imx is a patched version of the kernel.org one, that include the support the specific freescale (imx) boards. Isn't it? See the description of each kernel provider here: http://freescale.github.io/doc/release-notes/1.7/index.html#document-kernel-linux If yes, then I should prefer linux-imx because the freescale device drivers should not be included in fslc kernel... Another question, how I should compare the imx kernel with the fslc one using the evk board? I don´t know. It depends on your project. But, if you don´t know what to use or what you need, start with the default setup, which is virtual/kernel = linux-imx (see mxs-base.inc) Daiane -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] save kernel configuration
Hello Chris, thank you for your hints, I just read the part of the manual and I have doubts about the correct locations, the manual says : For example, suppose you had a set of configuration options in a file called myconfig.cfg. If you put that file inside a directory named linux-yocto that resides in the same directory as the kernel's append file and then add a SRC_URI statement such as the following to the kernel's append file, In my case I have in the folder /sources/meta-fsl-arm-extra/recipes-kernel the folder linux-wandboard-3.10.17 and also the files linux-wandboard-3.10.17.bb and linux-wandboard.inc, no append file So I added a folder linux-wandboard and put in the myconfig.cfg test-file. In the linux-wandboard.inc I added file://myconfig.cfgfile:///\\myconfig.cfg to the SRC_URI. Is that correct ? I can't test so quickly, as after making that last change and re-running bitbake it started fetching the linux source again (which goes very slow as I have a slow connection here)... is that re-fetching normal ? Thank you greetings, Mat Von: Chris Tapp [mailto:opensou...@keylevel.com] Gesendet: Donnerstag, 27. November 2014 09:20 An: Heise, Matthias Cc: meta-freescale@yoctoproject.org Betreff: Re: [meta-freescale] save kernel configuration Hi Mat, On 27 Nov 2014, at 07:46, matthias.he...@atlas-elektronik.commailto:matthias.he...@atlas-elektronik.com matthias.he...@atlas-elektronik.commailto:matthias.he...@atlas-elektronik.com wrote: Hi there, when I'm turning options on and off in menuconfig these changes are usually saved in the .config file, which resides (in my case)in /build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboardd/3.10.17-r0/git , right ? As this configuration is obviously downloaded from git, I've got a few questions: 1. Is this configuration integral part of (in this case) the linux-wandboard-3.10.17, so if I change the configuration the version must be changed ? 2. Which purpose does the defconfig file in /sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-wandboard-3.10.17 have ? 3. Or is the defconfig file copied, changed by recipe (linux-wandboard_3.10.17.bb, f.e. LOCALVERSION ) and if I change something and want to include this into the image recipe I copy the tweaked .config file into a new defconfig ? Or how would be the procedure ? 1. The version number is simply the kernel version that is being used - configuration just selects which features are exposed; 2. The defconfig is the default configuration that will be used as the .config when the kernel is built for the wandboard; 3. Any kernel changes that are requested else where (e.g. configuration fragments, below) modify what is in .config before the build takes place. Any changes you make using menuconfig will be lost as they are stored in the work area. If you want to be able to reapply changes you probably want to look at using configuration fragments. I would start by reading the section Creating Configuration Fragments in the documentation (www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.htmlhttp://www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html). Configuration fragments are much easier to manage and will apply to any kernel version that supports the option(s). -- Chris Tapp opensou...@keylevel.commailto:opensou...@keylevel.com www.keylevel.comhttp://www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] R: Status of imx28evk recipes/images
Hello Daiane, Thank you so much for your replies. I think I will start with linux-imx as you suggested. Thanks Simone -Messaggio originale- Da: angol...@gmail.com [mailto:angol...@gmail.com] Per conto di Daiane Angolini Inviato: giovedì 27 novembre 2014 12:55 A: Simone Cc: meta-freescale@yoctoproject.org; Otavio Salvador Oggetto: Re: [meta-freescale] Status of imx28evk recipes/images On Tue, Nov 25, 2014 at 5:47 PM, Simone cjb.sw.nos...@gmail.com wrote: I mean, we work also on imx53qsb board and we know that the last working kernel is 2.6.35.3 So, let's redefine the question: which is the latest working kernel for this board? The latest working kernel for this board is linux-next from kernel.org. It´s not even supported in FSL Community BSP as we only include stable versions (but it´s a perfectly working kernel) The question you want to do is What is the latest release from Freescale for imx28evk. And for this question you must go to freescale.com: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MCIMX28EVKJfpsp=1tab=Design_Tools_Tab# And, only to make it clear: http://freescale.github.io/doc/release-notes/1.7/#what-the-project-name-is-not Thank you, but I'm still missing something.. I suppose that linux-imx is a patched version of the kernel.org one, that include the support the specific freescale (imx) boards. Isn't it? See the description of each kernel provider here: http://freescale.github.io/doc/release-notes/1.7/index.html#document-kernel-linux If yes, then I should prefer linux-imx because the freescale device drivers should not be included in fslc kernel... Another question, how I should compare the imx kernel with the fslc one using the evk board? I don´t know. It depends on your project. But, if you don´t know what to use or what you need, start with the default setup, which is virtual/kernel = linux-imx (see mxs-base.inc) Daiane -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-demos][PATCH v2] packagegroup-fslc-gstreamer1.0-commercial: remove commercial recipe
On Wed, Nov 26, 2014 at 12:23 AM, Carlos Rafael Giani d...@pseudoterminal.org wrote: Sorry, typo. I meant gstreamer1.0-plugins-ugly-asf , not gstreamer1.0-plugins-ugly-asfdemux. The -asf package contains the libgstasf.so plugin, which in turn contains the asfdemux element. Could you point me on gstreamer1.0-plugins-ugly-asf package in layers? I have tried to search across poky/oe layers again, but have not found it. -- Regards, Alexander -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-demos][PATCH v2] packagegroup-fslc-gstreamer1.0-commercial: remove commercial recipe
On 2014-11-27 13:41, Alexander Shashkevych wrote: On Wed, Nov 26, 2014 at 12:23 AM, Carlos Rafael Giani d...@pseudoterminal.org wrote: Sorry, typo. I meant gstreamer1.0-plugins-ugly-asf , not gstreamer1.0-plugins-ugly-asfdemux. The -asf package contains the libgstasf.so plugin, which in turn contains the asfdemux element. Could you point me on gstreamer1.0-plugins-ugly-asf package in layers? I have tried to search across poky/oe layers again, but have not found it. I built the most recent state of the dizzy branch of poky and meta-fsl-arm. I built gstreamer1.0-plugins-ugly with bitbake, and got this file in tmp/deploy/ipk/cortexa9hf-vfp-neon/ : gstreamer1.0-plugins-ugly-asf_1.4.1-r0_cortexa9hf-vfp-neon.ipk Note that gstreamer1.0-plugins-ugly won't build unless commercial is added to LICENSE_FLAGS_WHITELIST. I add it in local.conf. -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] directFB and GTK + libvivante-dfb-mx6 build error
Hi, I'm supposed to run a WebkitGTK+ application with directFB output on an imx6 system. I read a lot of stuff and tried some things, but I still don't know whether it is possible or not... When I bitbake directfb-examples into a console-image with openembedded (daisy), some are working fine, while others crash with a segfault. When I include packagegroup-core-directfb in my image, libvivante-dfb-mx6 throws an error: Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-core-directfb: * libvivante-dfb-mx6 * * opkg_install_cmd: Cannot install package packagegroup-core-directfb. Earlier this year Otavio and Lauren stated that DFB wouldn't work with any newer version of DFB than 1.6.3, so my 1.6.3 should be ok for the moment, but maybe my recipes are simply too old. [1] Should I try to update to newer vivante binaries? I think 3.10.17-1.0.0 are used in my current setup. However I read here [2] that gtk support for directFB was dropped anyway, but I can't find a proper source to prove it. Could anybody please enlighten me with the current state of development and what's the matter with libvivante-dfb-mx6? Thanks in advance, Peter Fink [1]: https://lists.yoctoproject.org/pipermail/meta-freescale/2014-March/007722.html [2]: https://www.yoctoproject.org/irc/%23yocto.2014-09-25.log.html#t2014-09-25T17:45:48 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-demos][PATCH v2] packagegroup-fslc-gstreamer1.0-commercial: remove commercial recipe
Sorry, typo. I meant gstreamer1.0-plugins-ugly-asf , not gstreamer1.0-plugins-ugly-asfdemux. The -asf package contains the libgstasf.so plugin, which in turn contains the asfdemux element. Could you point me on gstreamer1.0-plugins-ugly-asf package in layers? I have tried to search across poky/oe layers again, but have not found it. I built the most recent state of the dizzy branch of poky and meta-fsl-arm. I built gstreamer1.0-plugins-ugly with bitbake, and got this file in tmp/deploy/ipk/cortexa9hf-vfp-neon/ : gstreamer1.0-plugins-ugly-asf_1.4.1-r0_cortexa9hf-vfp-neon.ipk Note that gstreamer1.0-plugins-ugly won't build unless commercial is added to LICENSE_FLAGS_WHITELIST. I add it in local.conf. I also have this package built, but I was unable to find particular recipe that creates it. Later I had found the reason why I was unable to find such recipe with asf plugin: gstreamer has recipe that declares packages dynamically depending on what gstreamer actually has. Therefore grepping for it was senseless. Today I'll send the final patch. -- Regards, Alexander -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-demos][PATCH v3] packagegroup-fslc-gstreamer1.0-commercial: update dependencies
Community has renamed following packages:
gstreamer1.0-plugins-ugly-asfdemuxer - gstreamer1.0-plugins-ugly-asf
gstreamer1.0-plugins-ugly-mpg123 - gstreamer1.0-plugins-bad-mpg123
This commit updates dependencies to reflect these changes and moves
packages gstreamer1.0-plugins-ugly-meta and gstreamer1.0-libav from
packagegroup-fslc-gstreamer1.0-full to
packagegroup-fslc-gstreamer1.0-commercial.
Signed-off-by: Alexander Shashkevich a...@stunpix.com
---
.../packagegroups/packagegroup-fslc-gstreamer1.0-commercial.bb | 5 +++--
.../packagegroups/packagegroup-fslc-gstreamer1.0-full.bb | 2 --
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git
a/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-commercial.bb
b/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-commercial.bb
index f33c3d8..f24b753 100644
---
a/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-commercial.bb
+++
b/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-commercial.bb
@@ -15,6 +15,7 @@ RDEPENDS_${PN} = \
# Plugins from the -ugly collection which require the commercial
flag in LICENSE_FLAGS_WHITELIST to be set
RDEPENDS_${PN} = \
-gstreamer1.0-plugins-ugly-mpg123 \
-gstreamer1.0-plugins-ugly-asfdemux \
+gstreamer1.0-plugins-ugly-meta \
+gstreamer1.0-plugins-ugly-asf \
+gstreamer1.0-libav \
diff --git
a/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-full.bb
b/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-full.bb
index 4dd3d77..8340332 100644
--- a/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-full.bb
+++ b/recipes-multimedia/packagegroups/packagegroup-fslc-gstreamer1.0-full.bb
@@ -14,6 +14,4 @@ RDEPENDS_${PN} = \
gstreamer1.0-plugins-base-meta \
gstreamer1.0-plugins-good-meta \
gstreamer1.0-plugins-bad-meta \
-${@base_contains('LICENSE_FLAGS_WHITELIST', 'commercial',
'gstreamer1.0-plugins-ugly-meta', '', d)} \
-${@base_contains('LICENSE_FLAGS_WHITELIST', 'commercial',
'gstreamer1.0-libav', '', d)} \
--
1.9.1
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] directFB and GTK + libvivante-dfb-mx6 build error
On Thu, Nov 27, 2014 at 11:08 AM, Peter ppf83...@freenet.de wrote: Hi, I'm supposed to run a WebkitGTK+ application with directFB output on an imx6 system. I read a lot of stuff and tried some things, but I still don't know whether it is possible or not... When I bitbake directfb-examples into a console-image with openembedded (daisy), some are working fine, while others crash with a segfault. When I include packagegroup-core-directfb in my image, libvivante-dfb-mx6 throws an error: Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-core-directfb: * libvivante-dfb-mx6 * * opkg_install_cmd: Cannot install package packagegroup-core-directfb. Only to be sure. Have you changed your DISTRO_FEATURES? Have you tried core-image-directfb? Daiane Earlier this year Otavio and Lauren stated that DFB wouldn't work with any newer version of DFB than 1.6.3, so my 1.6.3 should be ok for the moment, but maybe my recipes are simply too old. [1] Should I try to update to newer vivante binaries? I think 3.10.17-1.0.0 are used in my current setup. However I read here [2] that gtk support for directFB was dropped anyway, but I can't find a proper source to prove it. Could anybody please enlighten me with the current state of development and what's the matter with libvivante-dfb-mx6? Thanks in advance, Peter Fink [1]: https://lists.yoctoproject.org/pipermail/meta-freescale/2014-March/007722.html [2]: https://www.yoctoproject.org/irc/%23yocto.2014-09-25.log.html#t2014-09-25T17:45:48 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
