Re: [meta-freescale] [meta-fsl-arm][PATCH v2] gpu-viv-bin-mx6q: Add missing libffi dependency
On Thu, Jul 17, 2014 at 7:49 AM, Jacob Kroon jacob.kr...@mikrodidakt.se wrote: Running readelf --dynamic libgc_wayland_protocol.so | grep NEEDED shows that the library has a runtime dependency on libffi. Same thing applies to libwayland-viv.so. Add libffi to DEPENDS for wayland builds, so that packaging can properly detect the runtime dependency. For non-wayland builds, skip packaging the files, so that they don't cause unexpected changes in buildhistory. Finally looked up wayland, and it looks like libffi is already a dependency for wayland, so no need to add it again. I'll send a new patch that only skips packaging the wayland files when doing non-wayland builds. I think this was the idea initially proposed by Otavio. /Jacob -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm][PATCH] gpu-viv-bin-mx6q: Don't package wayland libraries in non-wayland builds
Running
readelf --dynamic libgc_wayland_protocol.so | grep NEEDED
shows that the library has a runtime dependency on libffi. Same thing
applies to libwayland-viv.so.
For non-wayland builds, where libffi may or may not be available during
package time, skip packaging them so that they don't cause unexpected
dependency changes in buildhistory.
Signed-off-by: Jacob Kroon jacob.kr...@mikrodidakt.se
---
recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc | 6 ++
1 file changed, 6 insertions(+)
diff --git a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
index 4106848..1437a37 100644
--- a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
+++ b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
@@ -174,6 +174,12 @@ do_install () {
ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so.2
ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so
+# skip packaging wayland libraries for non-wayland backends
+if [ ${backend} != wl ]; then
+rm ${D}${libdir}/libgc_wayland_protocol.*
+rm ${D}${libdir}/libwayland-viv.*
+fi
+
for backend in wl x11 fb dfb; do
find ${D}${libdir} -name *-$backend.so -exec rm '{}' ';'
done
--
1.9.3
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] mxs-auart and LED triggers
Hi Stuart, Le Thu, 17 Jul 2014 15:51:37 +1000, Stuart Longland stua...@vrt.com.au a écrit : Not sure if this is the place to ask or not, I'm currently in search for the upstream project that looks after the i.MX port of the mainline Linux kernel. We're busy building a device for polling energy meters over RS-485, and one of my colleagues asked if it were possible to use the activity LED on the unit to indicate RS-485 activity. Presently, I use it to indicate mmc0 activity. I'm not sure if there's an equivalent for serial ports. I did a bit of searching, both for general purpose serial triggers through to auart-related triggers, nothing seemed to show up. you're right and you will need to add a serial leg trigger and the right hooks in the driver or the serial core depending the information you want to show on the leds. On a related note, the FlexCAN driver supports turning on/off regulators when someone brings up or down a CAN interface. Is there an equivalent facility on mxs-auart that would turn on a regulator when someone opens a serial port? you need to add the right hooks in the serial driver similar to what is done in the CAN driver. Best regards, Eric -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm][PATCH v2] gpu-viv-bin-mx6q: Don't package wayland libraries in non-wayland builds
Running
readelf --dynamic libgc_wayland_protocol.so | grep NEEDED
shows that the library has a runtime dependency on libffi. Same thing
applies to libwayland-viv.so.
For non-wayland builds, where libffi may or may not be available during
package time, skip packaging them so that they don't cause unexpected
dependency changes in buildhistory.
Changes in V2:
- Check $USE_WL instead of $backend since future x11 support
may want to drag in wayland libraries
Signed-off-by: Jacob Kroon jacob.kr...@mikrodidakt.se
---
recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc | 6 ++
1 file changed, 6 insertions(+)
diff --git a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
index 4106848..0db37c3 100644
--- a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
+++ b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
@@ -174,6 +174,12 @@ do_install () {
ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so.2
ln -sf libGLESv2.so.2.0.0 ${D}${libdir}/libGLESv2.so
+# skip packaging wayland libraries if no support is requested
+if [ ${USE_WL} = no ]; then
+rm ${D}${libdir}/libgc_wayland_protocol.*
+rm ${D}${libdir}/libwayland-viv.*
+fi
+
for backend in wl x11 fb dfb; do
find ${D}${libdir} -name *-$backend.so -exec rm '{}' ';'
done
--
1.9.3
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] i.MX6 MarsBoard Unable to handle kernel paging request at virtual address 73627573
Hello. I tried to run simple image on MarsBoard development kit (from embest-tech). I tried to patch meta-fsl-arm-extra as described at http://patches.openembedded.org/patch/66003/, http://patches.openembedded.org/patch/66001/ and http://patches.openembedded.org/patch/65999/. So I make uBoot, uImage and core-image-minimal. After images were loaded to board I start it and have error message (short log bellow). Where is a problem may be? Bluetooth: SCO socket layer initialized cfg80211: Calling CRDA to update world regulatory domain i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method Switching to clocksource mxc_timer1 Unable to handle kernel paging request at virtual address 73627573 pgd = 80004000 [73627573] *pgd= Internal error: Oops: 5 [#1] PREEMPT SMP Modules linked in: CPU: 0Not tainted (3.0.15-marsboard+yocto+geeb0c0e #1) PC is at kmem_cache_alloc+0xa8/0x100 LR is at con_insert_unipair+0x74/0x104 pc : [800eac90]lr : [8027082c]psr: 6093 sp : b8049ed8 ip : 8003b5a0 fp : r10: 0001 r9 : 80a53cc0 r8 : 00d0 r7 : 0bfd r6 : b8048000 r5 : b8002300 r4 : 73627573 r3 : 80a53cc0 r2 : 8027082c r1 : 24fc r0 : 2013 Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c53c7d Table: 1000404a DAC: 0015 PC: 0x800eac10: ac10 e5961014 e595c000 e7930101 e08c1000 e5911004 e79c4000 e354 0a1f ac30 e10f f10c0080 e596c014 e595a000 e793710c e1a0c00a e79cb007 e154000b ac50 0a07 e3a0a000 e121f000 e35a 0aea e3180902 1a18 e1a4 ac70 e8bd8ff8 e28aa004 e79aa007 e151000a 1af3 e595b014 e2811004 e3a0a001 ac90 e794b00b e78cb007 e5967014 e595c000 e7997107 e28cc004 e78c1007 eae9 acb0 e1a5 e1a01008 eb0f8d0f e3180902 e1a04000 0ae8 e350 0ae6 acd0 e5951010 e351 0ae3 e1a4 eb04d11e eae0 e92d4070 e30442b8 acf0 e34840aa e1a06000 e1a05001 e594308c e3530003 0a0f e5940064 e350 LR: 0x802707ac: 07ac ebf9e8b4 e5875098 e8bd81f0 e92d40f8 e1a075a1 e1a05000 e1a04001 e7900107 07cc e1a06002 e350 0a0d e7e41354 e7903101 e0807101 e353 0a19 07ec e204203f e0844a06 e3a0 e1a02082 e18360b2 e5953084 e0834004 e5854084 080c e8bd80f8 e3043308 e34830aa e593001c e350 0a1c e3a010d0 ebf9e8ee 082c e350 e7850107 0a1e e3a03000 e1a01003 e7801003 e2833004 e3530080 084c 1afb eae0 e3043308 e34830aa e593001c e350 0a0f e3a010d0 086c ebf9e8dd e350 e1a03000 e587 0a0c e1a3 e3a010ff e3a02080 088c ebfeba03 e1a03000 ead4 e3a0c010 e785c107 e1ac eae3 e3a03010 SP: 0xb8049e58: 9e58 004c5310 0007 b8002300 0020 b8002300 9e78 040f 0005 b8048000 0bfd 00d0 8003f990 2013 24fc 9e98 8027082c 80a53cc0 73627573 b8002300 b8048000 0bfd 00d0 80a53cc0 9eb8 0001 8003b5a0 b8049ed8 8027082c 800eac90 6093 9ed8 80aa4308 f804 b80f4b40 005f 001f 80a70d52 80a70d4c 005f 9ef8 0003 8027082c 80a70eb0 0001 b80f4b40 005f 8027148c 9f18 80ab19c4 80a70eb0 80ab1ba4 b8004000 0001 0014 80ab1dc8 9f38 0002 0004 8001fee8 8001f404 80ab1ca4 IP: 0x8003b520: b520 ec410b11 e1a0f00e ec410b12 e1a0f00e ec410b13 e1a0f00e ec410b14 e1a0f00e b540 ec410b15 e1a0f00e ec410b16 e1a0f00e ec410b17 e1a0f00e ec410b18 e1a0f00e b560 ec410b19 e1a0f00e ec410b1a e1a0f00e ec410b1b e1a0f00e ec410b1c e1a0f00e b580 ec410b1d e1a0f00e ec410b1e e1a0f00e ec410b1f e1a0f00e ec410b30 e1a0f00e b5a0 ec410b31 e1a0f00e ec410b32 e1a0f00e ec410b33 e1a0f00e ec410b34 e1a0f00e b5c0 ec410b35 e1a0f00e ec410b36 e1a0f00e ec410b37 e1a0f00e ec410b38 e1a0f00e b5e0 ec410b39 e1a0f00e ec410b3a e1a0f00e ec410b3b e1a0f00e ec410b3c e1a0f00e b600 ec410b3d e1a0f00e ec410b3e e1a0f00e ec410b3f e1a0f00e e92d0030 e1a04000 R2: 0x802707ac: 07ac ebf9e8b4 e5875098 e8bd81f0 e92d40f8 e1a075a1 e1a05000 e1a04001 e7900107 07cc e1a06002 e350 0a0d e7e41354 e7903101 e0807101 e353 0a19 07ec e204203f e0844a06 e3a0 e1a02082 e18360b2 e5953084 e0834004 e5854084 080c e8bd80f8 e3043308 e34830aa e593001c e350 0a1c e3a010d0 ebf9e8ee 082c e350 e7850107 0a1e e3a03000 e1a01003 e7801003 e2833004 e3530080 084c 1afb eae0 e3043308 e34830aa e593001c e350 0a0f e3a010d0 086c ebf9e8dd e350 e1a03000 e587 0a0c e1a3 e3a010ff e3a02080 088c ebfeba03 e1a03000 ead4 e3a0c010 e785c107 e1ac eae3 e3a03010 R3: 0x80a53c40: 3c40 80a53c40 80a53c40 80a53c50 80a53c50 3c60 3c80 0064 8000 000f 8c017060 0008 0002 8c017040 8c017020 3ca0 8c008000 002c 8c00f000 8c017000 0001 1000 0001 3cc0 0bfd 0bfd8000
Re: [meta-freescale] i.MX6 MarsBoard Unable to handle kernel paging request at virtual address 73627573
Hi there, This looks very similar to a known issue that I also encountered a while ago. See https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html Regards, Dave C - Original Message - From: grommerin gromme...@gmail.com To: meta-freescale@yoctoproject.org Sent: Thursday, 17 July, 2014 11:05:05 AM Subject: [meta-freescale] i.MX6 MarsBoard Unable to handle kernel paging request at virtual address 73627573 Hello. I tried to run simple image on MarsBoard development kit (from embest-tech). I tried to patch meta-fsl-arm-extra as described at http://patches.openembedded.org/patch/66003/, http://patches.openembedded.org/patch/66001/ and http://patches.openembedded.org/patch/65999/. So I make uBoot, uImage and core-image-minimal. After images were loaded to board I start it and have error message (short log bellow). Where is a problem may be? Bluetooth: SCO socket layer initialized cfg80211: Calling CRDA to update world regulatory domain i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method Switching to clocksource mxc_timer1 Unable to handle kernel paging request at virtual address 73627573 pgd = 80004000 [73627573] *pgd= Internal error: Oops: 5 [#1] PREEMPT SMP Modules linked in: CPU: 0Not tainted (3.0.15-marsboard+yocto+geeb0c0e #1) PC is at kmem_cache_alloc+0xa8/0x100 LR is at con_insert_unipair+0x74/0x104 pc : [800eac90]lr : [8027082c]psr: 6093 sp : b8049ed8 ip : 8003b5a0 fp : r10: 0001 r9 : 80a53cc0 r8 : 00d0 r7 : 0bfd r6 : b8048000 r5 : b8002300 r4 : 73627573 r3 : 80a53cc0 r2 : 8027082c r1 : 24fc r0 : 2013 Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c53c7d Table: 1000404a DAC: 0015 PC: 0x800eac10: ac10 e5961014 e595c000 e7930101 e08c1000 e5911004 e79c4000 e354 0a1f ac30 e10f f10c0080 e596c014 e595a000 e793710c e1a0c00a e79cb007 e154000b ac50 0a07 e3a0a000 e121f000 e35a 0aea e3180902 1a18 e1a4 ac70 e8bd8ff8 e28aa004 e79aa007 e151000a 1af3 e595b014 e2811004 e3a0a001 ac90 e794b00b e78cb007 e5967014 e595c000 e7997107 e28cc004 e78c1007 eae9 acb0 e1a5 e1a01008 eb0f8d0f e3180902 e1a04000 0ae8 e350 0ae6 acd0 e5951010 e351 0ae3 e1a4 eb04d11e eae0 e92d4070 e30442b8 acf0 e34840aa e1a06000 e1a05001 e594308c e3530003 0a0f e5940064 e350 LR: 0x802707ac: 07ac ebf9e8b4 e5875098 e8bd81f0 e92d40f8 e1a075a1 e1a05000 e1a04001 e7900107 07cc e1a06002 e350 0a0d e7e41354 e7903101 e0807101 e353 0a19 07ec e204203f e0844a06 e3a0 e1a02082 e18360b2 e5953084 e0834004 e5854084 080c e8bd80f8 e3043308 e34830aa e593001c e350 0a1c e3a010d0 ebf9e8ee 082c e350 e7850107 0a1e e3a03000 e1a01003 e7801003 e2833004 e3530080 084c 1afb eae0 e3043308 e34830aa e593001c e350 0a0f e3a010d0 086c ebf9e8dd e350 e1a03000 e587 0a0c e1a3 e3a010ff e3a02080 088c ebfeba03 e1a03000 ead4 e3a0c010 e785c107 e1ac eae3 e3a03010 SP: 0xb8049e58: 9e58 004c5310 0007 b8002300 0020 b8002300 9e78 040f 0005 b8048000 0bfd 00d0 8003f990 2013 24fc 9e98 8027082c 80a53cc0 73627573 b8002300 b8048000 0bfd 00d0 80a53cc0 9eb8 0001 8003b5a0 b8049ed8 8027082c 800eac90 6093 9ed8 80aa4308 f804 b80f4b40 005f 001f 80a70d52 80a70d4c 005f 9ef8 0003 8027082c 80a70eb0 0001 b80f4b40 005f 8027148c 9f18 80ab19c4 80a70eb0 80ab1ba4 b8004000 0001 0014 80ab1dc8 9f38 0002 0004 8001fee8 8001f404 80ab1ca4 IP: 0x8003b520: b520 ec410b11 e1a0f00e ec410b12 e1a0f00e ec410b13 e1a0f00e ec410b14 e1a0f00e b540 ec410b15 e1a0f00e ec410b16 e1a0f00e ec410b17 e1a0f00e ec410b18 e1a0f00e b560 ec410b19 e1a0f00e ec410b1a e1a0f00e ec410b1b e1a0f00e ec410b1c e1a0f00e b580 ec410b1d e1a0f00e ec410b1e e1a0f00e ec410b1f e1a0f00e ec410b30 e1a0f00e b5a0 ec410b31 e1a0f00e ec410b32 e1a0f00e ec410b33 e1a0f00e ec410b34 e1a0f00e b5c0 ec410b35 e1a0f00e ec410b36 e1a0f00e ec410b37 e1a0f00e ec410b38 e1a0f00e b5e0 ec410b39 e1a0f00e ec410b3a e1a0f00e ec410b3b e1a0f00e ec410b3c e1a0f00e b600 ec410b3d e1a0f00e ec410b3e e1a0f00e ec410b3f e1a0f00e e92d0030 e1a04000 R2: 0x802707ac: 07ac ebf9e8b4 e5875098 e8bd81f0 e92d40f8 e1a075a1 e1a05000 e1a04001 e7900107 07cc e1a06002 e350 0a0d e7e41354 e7903101 e0807101 e353 0a19 07ec e204203f e0844a06 e3a0 e1a02082 e18360b2 e5953084 e0834004 e5854084 080c e8bd80f8 e3043308 e34830aa e593001c e350 0a1c e3a010d0 ebf9e8ee 082c e350 e7850107 0a1e e3a03000 e1a01003 e7801003 e2833004 e3530080 084c 1afb eae0 e3043308 e34830aa e593001c e350 0a0f e3a010d0 086c
[meta-freescale] for meta-fsl-arm image types, what means linux.sb?
just got a wandboard quad, ready to build a yocto image for it, and in the class file image_types_fsl.bbclass, i notice the string linux.sb. at the risk of sounding silly, what does sb stand for? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] HDMI out : Kernel hangs on boot when cable is plugged
Hi all,
I have a custom board, on which HDMI part is quite the same as the sabresd.
I added the HDMI support, and mxcfb support in my dts. Here is the issue :
Without the HDMI cable, it boots correctly. When plugging the HDMI
cable, it is detected, and it shows a console.
With the cable plugged before booting, kernel stops very early :
## Booting kernel from Legacy Image at 1080 ...
Image Name: Linux-3.10.17+yocto+gc657345
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:5504216 Bytes = 5.2 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 1800
Booting using the fdt blob at 0x1800
Loading Kernel Image ... OK
Using Device Tree in place at 1800, end 1800cd6e
Starting kernel ...
Here is the dts part for HDMI :
/ {
aliases {
mxcfb0 = mxcfb1;
};
mxcfb1: fb@0 {
compatible = fsl,mxc_sdc_fb;
disp_dev = hdmi;
interface_pix_fmt = RGB24;
mode_str =1920x1080M@60;
default_bpp = 24;
int_clk = 0;
late_init = 0;
status = disabled;
};
v4l2_out {
compatible = fsl,mxc_v4l2_output;
status = okay;
};
};
hdmi_audio {
status = okay;
};
hdmi_core {
ipu_id = 0;
disp_id = 0;
status = okay;
};
hdmi_video {
fsl,phy_reg_vlev = 0x0294;
fsl,phy_reg_cksymtx = 0x800d;
status = okay;
};
i2c2 {
clock-frequency = 10;
pinctrl-names = default;
pinctrl-0 = pinctrl_i2c2_2;
status = okay;
hdmi: edid@50 {
compatible = fsl,imx6-hdmi-i2c;
reg = 0x50;
};
};
Any help would be appreciated !
Thanks,
JM
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] HDMI out : Kernel hangs on boot when cable is plugged
Hi all,
I have a custom board, on which HDMI part is quite the same as the sabresd.
I added the HDMI support, and mxcfb support in my dts. Here is the issue :
I was able to reproduce the same for my imx6qsabresd and imx6dlsabresd
Daiane
Without the HDMI cable, it boots correctly. When plugging the HDMI cable,
it is detected, and it shows a console.
With the cable plugged before booting, kernel stops very early :
## Booting kernel from Legacy Image at 1080 ...
Image Name: Linux-3.10.17+yocto+gc657345
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size:5504216 Bytes = 5.2 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 1800
Booting using the fdt blob at 0x1800
Loading Kernel Image ... OK
Using Device Tree in place at 1800, end 1800cd6e
Starting kernel ...
Here is the dts part for HDMI :
/ {
aliases {
mxcfb0 = mxcfb1;
};
mxcfb1: fb@0 {
compatible = fsl,mxc_sdc_fb;
disp_dev = hdmi;
interface_pix_fmt = RGB24;
mode_str =1920x1080M@60;
default_bpp = 24;
int_clk = 0;
late_init = 0;
status = disabled;
};
v4l2_out {
compatible = fsl,mxc_v4l2_output;
status = okay;
};
};
hdmi_audio {
status = okay;
};
hdmi_core {
ipu_id = 0;
disp_id = 0;
status = okay;
};
hdmi_video {
fsl,phy_reg_vlev = 0x0294;
fsl,phy_reg_cksymtx = 0x800d;
status = okay;
};
i2c2 {
clock-frequency = 10;
pinctrl-names = default;
pinctrl-0 = pinctrl_i2c2_2;
status = okay;
hdmi: edid@50 {
compatible = fsl,imx6-hdmi-i2c;
reg = 0x50;
};
};
Any help would be appreciated !
Thanks,
JM
--
___
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
Re: [meta-freescale] HDMI out : Kernel hangs on boot when cable is plugged
2014-07-17 16:01 GMT+02:00 daiane.angol...@freescale.com daiane.angol...@freescale.com: Hi all, I have a custom board, on which HDMI part is quite the same as the sabresd. I added the HDMI support, and mxcfb support in my dts. Here is the issue : I was able to reproduce the same for my imx6qsabresd and imx6dlsabresd Interesting... but do you have a clue :) ? I can help, but I must say I don't have any idea of where the issue could be... JM -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] HDMI out : Kernel hangs on boot when cable is plugged
Hi Jean-Michel, Le Thu, 17 Jul 2014 16:16:18 +0200, Jean-Michel Hautbois jhautb...@gmail.com a écrit : 2014-07-17 16:01 GMT+02:00 daiane.angol...@freescale.com daiane.angol...@freescale.com: Hi all, I have a custom board, on which HDMI part is quite the same as the sabresd. I added the HDMI support, and mxcfb support in my dts. Here is the issue : I was able to reproduce the same for my imx6qsabresd and imx6dlsabresd Interesting... but do you have a clue :) ? I can help, but I must say I don't have any idea of where the issue could be... if you have HDMI enabled in u-boot : can you try to disable HDMI in u-boot and let Linux initialize it. Eric -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] HDMI out : Kernel hangs on boot when cable is plugged
2014-07-17 16:58 GMT+02:00 Eric Bénard e...@eukrea.com: Hi Jean-Michel, Le Thu, 17 Jul 2014 16:16:18 +0200, Jean-Michel Hautbois jhautb...@gmail.com a écrit : 2014-07-17 16:01 GMT+02:00 daiane.angol...@freescale.com daiane.angol...@freescale.com: Hi all, I have a custom board, on which HDMI part is quite the same as the sabresd. I added the HDMI support, and mxcfb support in my dts. Here is the issue : I was able to reproduce the same for my imx6qsabresd and imx6dlsabresd Interesting... but do you have a clue :) ? I can help, but I must say I don't have any idea of where the issue could be... if you have HDMI enabled in u-boot : can you try to disable HDMI in u-boot and let Linux initialize it. OK, it works when I disable HDMI from u-boot... JM -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH v2] gpu-viv-bin-mx6q: Don't package wayland libraries in non-wayland builds
On Thu, Jul 17, 2014 at 5:59 AM, Jacob Kroon jacob.kr...@mikrodidakt.se wrote: Running readelf --dynamic libgc_wayland_protocol.so | grep NEEDED shows that the library has a runtime dependency on libffi. Same thing applies to libwayland-viv.so. For non-wayland builds, where libffi may or may not be available during package time, skip packaging them so that they don't cause unexpected dependency changes in buildhistory. Changes in V2: - Check $USE_WL instead of $backend since future x11 support may want to drag in wayland libraries Signed-off-by: Jacob Kroon jacob.kr...@mikrodidakt.se I have added this to master-next and will run it in a full build for all backends; so we don't have bad surprises ;-) -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] for meta-fsl-arm image types, what means linux.sb?
Hello Robert, On Thu, Jul 17, 2014 at 8:57 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: just got a wandboard quad, ready to build a yocto image for it, and in the class file image_types_fsl.bbclass, i notice the string linux.sb. at the risk of sounding silly, what does sb stand for? This is MX23/MX28 specific. This stands for to Boot Stream and it is essentially a header which contents SoC specific code for initialization. I hope it helps. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
