[meta-freescale] [3rdparty][PATCH] ventana: update UBI args for additional NAND devices

2019-04-25 Thread Tim Harvey 
Ventana boards now support 2GiB 2K page size flash devices with 16248 blocks

Signed-off-by: Tim Harvey 

Please backport all the way to jethro
---
 conf/machine/ventana.conf | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/machine/ventana.conf b/conf/machine/ventana.conf
index 7794c77..b7ed7ac 100644
--- a/conf/machine/ventana.conf
+++ b/conf/machine/ventana.conf
@@ -71,10 +71,10 @@ MULTIUBI_BUILD ?= "normal large"
 
 UBI_VOLNAME = "rootfs"
 
-# 256MB ('normal' flash layout)
-export MKUBIFS_ARGS_normal = "-F -m 2048 -e 124KiB -c 1912 -x zlib"
+# 2K page size ('normal' flash layout)
+export MKUBIFS_ARGS_normal = "-F -m 2048 -e 124KiB -c 16248 -x zlib"
 export UBINIZE_ARGS_normal = "-m 2048 -p 128KiB -s 2048"
 
-# 2GB ('large' flash layout)
+# 4K page size ('large' flash layout)
 export MKUBIFS_ARGS_large = "-F -m 4096 -e 248KiB -c 8124 -x zlib"
 export UBINIZE_ARGS_large = "-m 4096 -p 256KiB -s 4096"
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty] [PATCH] linux-gateworks-imx: update to latest Gateworks kernel

2017-05-22 Thread Tim Harvey 
An issue was resolved that caused certain kernel modules to have invalid
CRC's when built with GCC 5.4+ which would cause them to fail loading
if CONFIG_MODVERSIONS is enabled.

See Linux commit d9991ca46 genksyms: fix typeof() handling

Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 recipes-kernel/linux/linux-gateworks-imx_3.14.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-gateworks-imx_3.14.bb 
b/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
index d2190f4..a0f1e80 100644
--- a/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
+++ b/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
@@ -6,7 +6,7 @@ include recipes-kernel/linux/linux-dtb.inc
 
 DEPENDS += "lzop-native bc-native"
 
-SRCREV = "1032ddf66a1488b47f3ff72f944b4ceadcdd2e4e"
+SRCREV = "d9991ca465921e5ed120dd321e06a2d64eaa5099"
 LOCALVERSION = "-1.0.x-ga+yocto"
 SRC_URI = 
"git://github.com/Gateworks/linux-imx6.git;protocol=git;branch=gateworks_fslc_3.14_1.0.x_ga
 \
file://defconfig"
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] kernel modules failing to load because of missing symbols

2017-05-22 Thread Tim Harvey 
On Mon, May 15, 2017 at 11:00 AM, Tim Harvey <thar...@gateworks.com> wrote:
> Greetings,
>
> I've got a kernel recipe that builds several kernel modules which get
> build and packaged as kernel-module-. I'm finding that while
> most of these modules appear to load properly into the kernel at
> runtime, several of them do not because of missing symbols:
>
> # modprobe bluetooth
> [  782.848396] bluetooth: no symbol version for sock_register
> [  782.854315] bluetooth: Unknown symbol sock_register (err -22)
> # modprobe ip_tables
> [  893.675147] ip_tables: no symbol version for ns_capable
> [  893.680385] ip_tables: Unknown symbol ns_capable (err -22)
> modprobe: ERROR: could not insert 'ip_tables': Invalid argument
>
> The symbols do appear to be in the kernel's System.map:
> # grep " ns_capable" /boot/System.map*
> 80033cfc T ns_capable
> # grep sock_register /boot/System.map*
> 805337a8 T sock_register
> 8084fb0c R __ksymtab_sock_register
> 8085ab64 r __kcrctab_sock_register
> 8087abaf r __kstrtab_sock_register
>
> I'm seeing this on Yocto master, Yocto pyro 2.3, Yocto morty 2.2 but
> surprisingly not on Yocto krogoth 2.1.

In case anyone else runs into this I found that the issue was
occurring for a 3.14 kernel built with a GCC 5.4+ toolchain (GCC 5.2
is ok, GCC 5.3 was untested) due to a failure to calculate the CRC for
various modules by the kernel build tool scripts/genksysms. The kernel
build in this case 'will' show warnings such as:

WARNING: "ns_capable" [net/ipv6/netfilter/ip6_tables.ko] has no CRC!
WARNING: "ns_capable" [net/ipv4/netfilter/ip_tables.ko] has no CRC!
WARNING: "sock_register" [net/bluetooth/bluetooth.ko] has no CRC!
WARNING: "inode_add_bytes" [fs/udf/udf.ko] has no CRC!
WARNING: "current_fs_time" [fs/udf/udf.ko] has no CRC!
WARNING: "do_sync_read" [fs/udf/udf.ko] has no CRC!
WARNING: "d_tmpfile" [fs/udf/udf.ko] has no CRC!
WARNING: "vfs_fsync_range" [fs/udf/udf.ko] has no CRC!
WARNING: "in_group_p" [fs/configfs/configfs.ko] has no CRC!
WARNING: "current_fs_time" [fs/binfmt_misc.ko] has no CRC!
WARNING: "sys_close" [fs/binfmt_misc.ko] has no CRC!

The resulting modules with the warnings above will fail to load due to
those missing symbols. The issue is resolved by kernel commit
dc53324060f32 [1] which appears in Linux 3.15 and patches genksyms.

Tim

[1] - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/scripts/genksyms?id=dc53324060f324e8af6867f57bf4891c13c6ef18
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] kernel modules failing to load because of missing symbols

2017-05-15 Thread Tim Harvey 
Greetings,

I've got a kernel recipe that builds several kernel modules which get
build and packaged as kernel-module-. I'm finding that while
most of these modules appear to load properly into the kernel at
runtime, several of them do not because of missing symbols:

# modprobe bluetooth
[  782.848396] bluetooth: no symbol version for sock_register
[  782.854315] bluetooth: Unknown symbol sock_register (err -22)
# modprobe ip_tables
[  893.675147] ip_tables: no symbol version for ns_capable
[  893.680385] ip_tables: Unknown symbol ns_capable (err -22)
modprobe: ERROR: could not insert 'ip_tables': Invalid argument

The symbols do appear to be in the kernel's System.map:
# grep " ns_capable" /boot/System.map*
80033cfc T ns_capable
# grep sock_register /boot/System.map*
805337a8 T sock_register
8084fb0c R __ksymtab_sock_register
8085ab64 r __kcrctab_sock_register
8087abaf r __kstrtab_sock_register

I'm seeing this on Yocto master, Yocto pyro 2.3, Yocto morty 2.2 but
surprisingly not on Yocto krogoth 2.1.

Any ideas what could be going on here or how best to troubleshoot this?

Best Regards,

Tim

Tim Harvey - Principal Software Engineer
Gateworks Corporation - http://www.gateworks.com/
3026 S. Higuera St. San Luis Obispo CA 93401
805-781-2000
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] FSL Community BSP bblayer.conf invalid for 'bitbake-layers layerindex-fetch'

2017-05-08 Thread Tim Harvey 
On Sat, May 6, 2017 at 7:34 PM, Trevor Woerner  wrote:
>> This is a really nice tool but I find that the layout of the FSL
>> Community BSP doesn't work properly with it because of where
>> meta-oenemebedded gets placed. For this to work layers need to be
>> placed in BBLAYERS_FETCH_DIR which is set to COREBASE (sources/poky)
>> otherwise meta-openembedded gets duplicated.
>
> The layerindex-fetch tool makes assumptions that turn out to not be
> true if you start off (as you did) by using the fsl community repo.
> Two assumptions have, simply, collided :-)
>

Trevor,

Right - I realize this is an issue or invalid assumption about the fsl
community repo. I'm thinking that repo should be perhaps reworked to
move its layers within the poky dir to avoid this and allow using
'bitbake-layers layerindex-fetch' as its such a useful tool.

> You can override the definition of BBLAYERS_FETCH_DIR in your
> conf/local.conf (using an '='). If you set it to the full base
> location of where the fsl community repo has put your layers,
> layerindex-fetch should then work as expected?

Setting BBLAYERS_FETCH_DIR to my sources dir still ends up with
duplicates after a 'bitbake-layers layerindex-fetch meta-networking'
yet now there are no duplicate repos (just duplicate dirs in BBLAYERS)

BBLAYERS = " \
  ${BSPDIR}/sources/poky/meta \
  ${BSPDIR}/sources/poky/meta-poky \
  ${BSPDIR}/sources/meta-openembedded/meta-oe \
  ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
  ${BSPDIR}/sources/meta-freescale \
  ${BSPDIR}/sources/meta-freescale-3rdparty \
  ${BSPDIR}/sources/meta-freescale-distro \
  /tmp/yocto/sources/meta-openembedded/meta-oe \
 this one shouldn't be here and creates 'Duplicate inclusion'
warnings if it is
  /tmp/yocto/sources/meta-openembedded/meta-python \
  /tmp/yocto/sources/meta-openembedded/meta-networking \
  "

Perhaps bitbake-layers could be made smarter about avoiding duplicate
dirs in this case.

Regards,

Tim
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] FSL Community BSP bblayer.conf invalid for 'bitbake-layers layerindex-fetch'

2017-05-05 Thread Tim Harvey 
Greetings,

I've found that bitbake-layers has a nice subcommand
'layerindex-fetch' that will fetch layers from
https://layers.openembedded.org/ pulling in their dependencies and
adding them into your bblayers.conf.

This is a really nice tool but I find that the layout of the FSL
Community BSP doesn't work properly with it because of where
meta-oenemebedded gets placed. For this to work layers need to be
placed in BBLAYERS_FETCH_DIR which is set to COREBASE (sources/poky)
otherwise meta-openembedded gets duplicated.

Here's an example of what I'm talking about:

$ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master
$ repo sync
$ MACHINE=imx6qsabrelite DISTRO=poky source setup-environment build
$ bitbake-layers layerindex-fetch meta-networking # add meta-networking layer
Loading cache: 100% || Time: 0:00:00
Loaded 2320 entries from dependency cache.
LayerRequired by  Git repository
   Subdirectory
===
meta-networking  -
git://git.openembedded.org/meta-openembedded
meta-networking
openembedded-coremeta-networking
git://git.openembedded.org/openembedded-coremeta
meta-oe  meta-networking
git://git.openembedded.org/meta-openembeddedmeta-oe
meta-python  meta-networking
git://git.openembedded.org/meta-openembeddedmeta-python
Cloning into '/usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded'...
remote: Counting objects: 75951, done.
remote: Compressing objects: 100% (25800/25800), done.
remote: Total 75951 (delta 46633), reused 75600 (delta 46386)
Receiving objects: 100% (75951/75951), 26.05 MiB | 10.20 MiB/s, done.
Resolving deltas: 100% (46633/46633), done.
Checking connectivity... done.
Adding layer "meta-oe" to conf/bblayers.conf
Adding layer "meta-python" to conf/bblayers.conf
Adding layer "meta-networking" to conf/bblayers.conf
$ cat conf/bblayers.conf
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True))
+ '/../..')}"

BBFILES ?= ""
BBLAYERS = " \
  ${BSPDIR}/sources/poky/meta \
  ${BSPDIR}/sources/poky/meta-poky \
  ${BSPDIR}/sources/meta-openembedded/meta-oe \
  ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
  ${BSPDIR}/sources/meta-freescale \
  ${BSPDIR}/sources/meta-freescale-3rdparty \
  ${BSPDIR}/sources/meta-freescale-distro \
  /usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-oe \
  /usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-python \
  /usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-networking
\
  "
 note we now have two copies of meta-openembedded which causes
duplicate recipes/includes etc
$ bitbake core-image-console
WARNING: Duplicate inclusion for
/usr/src/ventana/yocto/pyro-2.3/sources/meta-openembedded/meta-oe/conf/distro/include/meta_oe_security_flags.inc
in 
/usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-oe/conf/layer.conf
WARNING: Duplicate inclusion for
/usr/src/ventana/yocto/pyro-2.3/sources/meta-openembedded/meta-oe/conf/distro/include/meta_oe_security_flags.inc
in 
/usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-oe/conf/layer.conf
WARNING: Duplicate inclusion for
/usr/src/ventana/yocto/pyro-2.3/sources/meta-openembedded/meta-oe/conf/distro/include/meta_oe_security_flags.inc
in 
/usr/src/ventana/yocto/pyro-2.3/sources/poky/meta-openembedded/meta-oe/conf/layer.conf
 caused by multiple copies of meta-openembedded

I'm not sure when the layerindex-fetch got added but I notice it also
doesn't work on morty for other reasons (python exceptions raised).

Any desire to fix this and anyone know the proper way to do so?

Regards,

Tim
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] Broken/missing bbappend?

2017-05-04 Thread Tim Harvey 
On Thu, Mar 30, 2017 at 8:16 AM, Tom Hochstein  wrote:
>
>
>> -Original Message-
>> From: Otavio Salvador [mailto:otavio.salva...@ossystems.com.br]
>> Sent: Thursday, March 30, 2017 8:20 AM
>>
>> On Thu, Mar 30, 2017 at 4:27 AM, Gary Thomas  wrote:
>> ...
>> > That said, it looks like this should be addressed.
>> >
>> > n.b. please don't ask me for a patch as I don't use wayland and
>> > am really not qualified to propose any such changes.
>> ...
>>
>> I agree and I am hoping for someone to step-in and propose a patch for
>> it. Tom? Carlos?
>>
>
> I'm working on it now.
>
> Tom

Tom,

I just stumbled across this myself. Are you still working on a fix?

Tim
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty][PATCH] linux-gateworks-imx: replace underscore with hyphen in LOCALVERSION

2017-05-03 Thread Tim Harvey 
fixes package-ipk

Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 recipes-kernel/linux/linux-gateworks-imx_3.14.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-gateworks-imx_3.14.bb 
b/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
index 781d96d..d2190f4 100644
--- a/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
+++ b/recipes-kernel/linux/linux-gateworks-imx_3.14.bb
@@ -7,7 +7,7 @@ include recipes-kernel/linux/linux-dtb.inc
 DEPENDS += "lzop-native bc-native"
 
 SRCREV = "1032ddf66a1488b47f3ff72f944b4ceadcdd2e4e"
-LOCALVERSION = "-1.0.x_ga+yocto"
+LOCALVERSION = "-1.0.x-ga+yocto"
 SRC_URI = 
"git://github.com/Gateworks/linux-imx6.git;protocol=git;branch=gateworks_fslc_3.14_1.0.x_ga
 \
file://defconfig"
 
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty][PATCH] ventana: add GW553x and GW560x support

2017-05-03 Thread Tim Harvey 
Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 conf/machine/ventana.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/conf/machine/ventana.conf b/conf/machine/ventana.conf
index b55185d..f3e111d 100644
--- a/conf/machine/ventana.conf
+++ b/conf/machine/ventana.conf
@@ -23,12 +23,16 @@ KERNEL_DEVICETREE  = " \
 imx6q-gw54xx.dtb \
 imx6q-gw551x.dtb \
 imx6q-gw552x.dtb \
+imx6q-gw553x.dtb \
+imx6q-gw560x.dtb \
 imx6dl-gw51xx.dtb \
 imx6dl-gw52xx.dtb \
 imx6dl-gw53xx.dtb \
 imx6dl-gw54xx.dtb \
 imx6dl-gw551x.dtb \
 imx6dl-gw552x.dtb \
+imx6dl-gw553x.dtb \
+imx6dl-gw560x.dtb \
 "
 
 KERNEL_IMAGETYPE = "uImage"
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty][PATCH] ventana: Add 'use-mainline-bsp' support

2017-04-19 Thread Tim Harvey 
The 'use-mainline-bsp' makes use of linux-fslc as kernel and removes
the not yet supported device-tree files from installation set.

Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 conf/machine/ventana.conf | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/conf/machine/ventana.conf b/conf/machine/ventana.conf
index e5abd3f..9cd1a55 100644
--- a/conf/machine/ventana.conf
+++ b/conf/machine/ventana.conf
@@ -12,8 +12,8 @@ require conf/machine/include/tune-cortexa9.inc
 PREFERRED_PROVIDER_virtual/bootloader = "u-boot-gateworks-imx"
 PREFERRED_PROVIDER_u-boot = "u-boot-gateworks-imx"
 
-PREFERRED_PROVIDER_virtual/kernel = "linux-gateworks-imx"
-PREFERRED_PROVIDER_kernel = "linux-gateworks-imx"
+PREFERRED_PROVIDER_virtual/kernel ??= "linux-gateworks-imx"
+PREFERRED_PROVIDER_virtual/kernel_use-mainline-bsp ??= "linux-fslc"
 
 KERNEL_DEVICETREE  = " \
 imx6q-gw5400-a.dtb \
@@ -37,6 +37,9 @@ KERNEL_DEVICETREE  = " \
 
 KERNEL_IMAGETYPE = "uImage"
 
+# Not yet supported by Linux mainline
+KERNEL_DEVICETREE_remove_use-mainline-bsp = "imx6q-gw560x.dtb 
imx6dl-gw560x.dtb"
+
 MACHINE_FEATURES += "pci wifi bluetooth"
 
 # Add kernel modules
@@ -56,6 +59,7 @@ MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "\
 # Bootloader configs:
 UBOOT_CONFIG ??= "std"
 UBOOT_CONFIG[std] = "gwventana_config"
+UBOOT_ENTRYPOINT_use-mainline-bsp = "0x10008000"
 
 SERIAL_CONSOLE = "115200 ttymxc1"
 
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty][PATCH] u-boot-script-gateworks-imx: bump to v1.07

2017-04-17 Thread Tim Harvey 
Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 .../6x_bootscript-yocto.txt| 197 +++--
 1 file changed, 100 insertions(+), 97 deletions(-)

diff --git 
a/recipes-bsp/u-boot/u-boot-script-gateworks-imx/6x_bootscript-yocto.txt 
b/recipes-bsp/u-boot/u-boot-script-gateworks-imx/6x_bootscript-yocto.txt
index b7478f0..df6f621 100644
--- a/recipes-bsp/u-boot/u-boot-script-gateworks-imx/6x_bootscript-yocto.txt
+++ b/recipes-bsp/u-boot/u-boot-script-gateworks-imx/6x_bootscript-yocto.txt
@@ -1,4 +1,4 @@
-setenv _bscriptver "v1.01"
+setenv _bscriptver "v1.07"
 
 echo "## Gateworks Ventana Yocto Bootscript ${_bscriptver} 
"
 
@@ -10,18 +10,11 @@ if test -z "${mem}" ; then
 # it using following formula (please customize mem to your own req's):
 #  cma=min(((${mem_mb}/2) - round(${mem_mb}*.125))M, 384M)
 if itest.s "x${mem_mb}" == "x256" ; then
-setenv mem "cma=96M"
+   setenv mem "cma=96M"
 elif itest.s "x${mem_mb}" == "x512" ; then
-setenv mem "cma=192M"
-elif itest.s "x${mem_mb}" == "x1024" ; then
-setenv mem "cma=384M"
-elif itest.s "x${mem_mb}" == "x2048" ; then
-setenv mem "cma=384M"
-elif itest.s "x${mem_mb}" == "x4096" ; then
-setenv mem "cma=384M"
+   setenv mem "cma=192M"
 else
-echo "Unable to pigeonhole memory. Defaulting CMA to 96M."
-setenv mem "cma=96M"
+   setenv mem "cma=384M"
 fi
 fi
 
@@ -41,101 +34,111 @@ if test -z "${video}" ; then
 setenv cvbs_flag
 setenv max_disp 3 # 0-3 displays
 
-# Detect displays if req'd (HDMI->LVDS->CVBS)
-if test -z "$display" ; then
-if test -z "$panel" ; then
-# Start detection scheme
-i2c dev 2
-if hdmidet ; then # HDMI
-setenv display "$display" "HDMI"
-echo "HDMI Detected"
-fi
-if i2c probe 0x04 ; then # Freescale MXC-LVDS1
-setenv display "$display" "LVDS"
-echo "LVDS Detected"
-fi
-if i2c probe 0x14 ; then # DLC800FIGT3
-setenv display "$display" "LVDS"
-echo "LVDS Detected"
-fi
-if i2c probe 0x38 ; then # DLC700JMGT4
-setenv display "$display" "LVDS"
-echo "LVDS Detected"
-fi
-fi
+# Default displays to display if displays is empty
+if test -z "${displays}"; then
+   setenv displays "${display}"
 fi
 
-echo "Display(s) to configure: ${display}"
+# Detect HDMI if displays is empty (HDMI)
+if test -z "${displays}" ; then
+   i2c dev 2
+   if hdmidet ; then # HDMI
+   setenv displays "HDMI"
+   echo "HDMI Detected"
+   fi
+fi
+
+echo "Display(s) to configure: ${displays}"
 
 # Configure displays
-for disp in ${display} ; do
-if itest.s "x${disp}" == "xHDMI" ; then
-if test -z "$hdmi_flag" ; then # Only allow one HDMI display
-setenv hdmi_flag 1
-test -n "$hdmi" || hdmi=1080p
-if itest.s "x${hdmi}" == "x1080p" ; then
-setenv hdmi "1920x1080M@60"
-elif itest.s "x${hdmi}" == "x720p" ; then
-setenv hdmi "1280x720M@60"
-elif itest.s "x${hdmi}" == "x480p" ; then
-setenv hdmi "720x480M@60"
-fi
-setenv video "$video" 
"video=mxcfb${fb_num}:dev=hdmi,${hdmi},if=RGB24,bpp=32"
-
-echo "Setting HDMI Display to mxcfb${fb_num}"
-setexpr fb_num $fb_num + 1
-fi
-elif itest.s "x${disp}" == "xLVDS" ; then
-if test -z "$lvds_flag" ; then # Only allow one LVDS display
-setenv lvds_flag 1
-setenv video "$video" 
"video=mxcfb${fb_num}:dev=ldb,bpp=32,if=RGB666"
-
-echo "Setting LVDS Display to mxcfb${fb_num}"
-setexpr fb_num $fb_num + 1
-fi
-elif itest.s "x${disp}" == "xCVBS" ; then
-if test -z "$cvbs_flag" ; then # Only allow one CVBS display
-setenv cvbs_flag 1
-

[meta-freescale] [3rdparty][PATCH] u-boot-gateworks-imx: bump to 040377

2017-04-17 Thread Tim Harvey 
Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb 
b/recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb
index 4570b03..c508326 100644
--- a/recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb
+++ b/recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb
@@ -7,7 +7,7 @@ DEPENDS = "u-boot-mkimage-native"
 
 PV = "v2015.04+git${SRCPV}"
 
-SRCREV = "1399f2225965bfc8f1d288cd57e677ca21a7a591"
+SRCREV = "040377aefd06c8eef41763868fc9c6df2cbf9b1c"
 SRC_URI = 
"git://github.com/Gateworks/u-boot-imx6.git;branch=gateworks_v2015.04"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
2.7.4

-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [3rdparty][PATCH] linux-gateworks-imx_3.14: bump to 1032ddf6

2017-04-17 Thread Tim Harvey 
Signed-off-by: Tim Harvey <thar...@gateworks.com>
---
 .../linux/linux-gateworks-imx-3.14/defconfig   | 144 -
 recipes-kernel/linux/linux-gateworks-imx_3.14.bb   |   2 +-
 2 files changed, 139 insertions(+), 7 deletions(-)

diff --git a/recipes-kernel/linux/linux-gateworks-imx-3.14/defconfig 
b/recipes-kernel/linux/linux-gateworks-imx-3.14/defconfig
index 40d527c..559bbb7 100644
--- a/recipes-kernel/linux/linux-gateworks-imx-3.14/defconfig
+++ b/recipes-kernel/linux/linux-gateworks-imx-3.14/defconfig
@@ -162,10 +162,23 @@ CONFIG_BRIDGE=y
 CONFIG_VLAN_8021Q=y
 CONFIG_CAN=y
 CONFIG_CAN_FLEXCAN=y
+CONFIG_BT=m
+CONFIG_BT_RFCOMM=m
+CONFIG_BT_RFCOMM_TTY=y
+CONFIG_BT_BNEP=m
+CONFIG_BT_BNEP_MC_FILTER=y
+CONFIG_BT_BNEP_PROTO_FILTER=y
+CONFIG_BT_HIDP=m
+CONFIG_BT_HCIBTUSB=m
+CONFIG_BT_HCIUART=m
+CONFIG_BT_HCIUART_H4=y
+CONFIG_BT_HCIUART_3WIRE=y
+CONFIG_BT_ATH3K=m
 CONFIG_RFKILL=y
 CONFIG_DEVTMPFS=y
 CONFIG_DEVTMPFS_MOUNT=y
 # CONFIG_STANDALONE is not set
+CONFIG_DMA_CMA=y
 CONFIG_IMX_WEIM=y
 CONFIG_CONNECTOR=y
 CONFIG_MTD=y
@@ -178,10 +191,12 @@ CONFIG_MTD_CFI_AMDSTD=y
 CONFIG_MTD_CFI_STAA=y
 CONFIG_MTD_PHYSMAP_OF=y
 CONFIG_MTD_DATAFLASH=y
+CONFIG_MTD_M25P80=y
 CONFIG_MTD_SST25L=y
 CONFIG_MTD_NAND=y
 CONFIG_MTD_NAND_GPMI_NAND=y
 CONFIG_MTD_NAND_MXC=y
+CONFIG_MTD_SPI_NOR=y
 CONFIG_MTD_UBI=y
 CONFIG_PROC_DEVICETREE=y
 CONFIG_BLK_DEV_LOOP=y
@@ -202,6 +217,7 @@ CONFIG_SATA_AHCI_PLATFORM=y
 CONFIG_AHCI_IMX=y
 # CONFIG_ATA_SFF is not set
 CONFIG_NETDEVICES=y
+CONFIG_TUN=y
 CONFIG_NET_DSA_MV88E6352=y
 # CONFIG_NET_VENDOR_ARC is not set
 # CONFIG_NET_VENDOR_BROADCOM is not set
@@ -220,13 +236,43 @@ CONFIG_SMC91X=y
 CONFIG_SMC911X=y
 CONFIG_SMSC911X=y
 # CONFIG_NET_VENDOR_STMICRO is not set
+CONFIG_MARVELL_PHY=y
 CONFIG_GATEWORKS_GW16083=y
-CONFIG_USB_USBNET=y
-CONFIG_INPUT_MATRIXKMAP=y
+CONFIG_USB_CATC=m
+CONFIG_USB_KAWETH=m
+CONFIG_USB_PEGASUS=m
+CONFIG_USB_RTL8150=m
+CONFIG_USB_RTL8152=m
+CONFIG_USB_USBNET=m
+CONFIG_USB_NET_CDC_EEM=m
+CONFIG_USB_NET_HUAWEI_CDC_NCM=m
+CONFIG_USB_NET_CDC_MBIM=m
+CONFIG_USB_NET_DM9601=m
+CONFIG_USB_NET_SR9700=m
+CONFIG_USB_NET_SR9800=m
+CONFIG_USB_NET_SMSC75XX=m
+CONFIG_USB_NET_SMSC95XX=m
+CONFIG_USB_NET_GL620A=m
+CONFIG_USB_NET_PLUSB=m
+CONFIG_USB_NET_MCS7830=m
+CONFIG_USB_NET_RNDIS_HOST=m
+CONFIG_USB_ALI_M5632=y
+CONFIG_USB_AN2720=y
+CONFIG_USB_EPSON2888=y
+CONFIG_USB_KC2190=y
+CONFIG_USB_NET_CX82310_ETH=m
+CONFIG_USB_NET_KALMIA=m
+CONFIG_USB_NET_QMI_WWAN=m
+CONFIG_USB_HSO=m
+CONFIG_USB_NET_INT51X1=m
+CONFIG_USB_IPHETH=m
+CONFIG_USB_SIERRA_NET=m
+CONFIG_USB_VL600=m
 # CONFIG_INPUT_MOUSEDEV_PSAUX is not set
 CONFIG_INPUT_EVDEV=y
 # CONFIG_KEYBOARD_ATKBD is not set
 CONFIG_KEYBOARD_GPIO=y
+CONFIG_KEYBOARD_TCA8418=y
 # CONFIG_MOUSE_PS2 is not set
 CONFIG_INPUT_TOUCHSCREEN=y
 CONFIG_TOUCHSCREEN_EGALAX=y
@@ -237,6 +283,7 @@ CONFIG_TOUCHSCREEN_TSC2007=y
 CONFIG_INPUT_MISC=y
 CONFIG_INPUT_GSC=y
 CONFIG_INPUT_MMA8450=y
+CONFIG_INPUT_LSM9DS1=m
 # CONFIG_SERIO is not set
 CONFIG_VT_HW_CONSOLE_BINDING=y
 # CONFIG_LEGACY_PTYS is not set
@@ -255,6 +302,7 @@ CONFIG_I2C_ALGOPCA=m
 CONFIG_I2C_IMX=y
 CONFIG_SPI=y
 CONFIG_SPI_IMX=y
+CONFIG_SPI_SPIDEV=y
 CONFIG_PPS_CLIENT_GPIO=y
 CONFIG_GPIO_SYSFS=y
 CONFIG_GPIO_PCA953X_IRQ=y
@@ -294,10 +342,9 @@ CONFIG_VIDEO_MXC_CSI_CAMERA=y
 CONFIG_SOC_CAMERA=y
 CONFIG_VIDEO_MX3=y
 CONFIG_DRM=y
-CONFIG_DRM_VIVANTE=y
+CONFIG_DRM_VIVANTE=m
 CONFIG_FB=y
 CONFIG_FB_MXS=y
-CONFIG_BACKLIGHT_LCD_SUPPORT=y
 CONFIG_LCD_CLASS_DEVICE=y
 CONFIG_LCD_L4F00242T03=y
 CONFIG_LCD_PLATFORM=y
@@ -326,11 +373,96 @@ CONFIG_SND_SOC_IMX_TDA1997X=y
 CONFIG_HID_MULTITOUCH=y
 CONFIG_USB=y
 CONFIG_USB_EHCI_HCD=y
-CONFIG_USB_ACM=m
 CONFIG_USB_STORAGE=y
 CONFIG_USB_CHIPIDEA=y
 CONFIG_USB_CHIPIDEA_UDC=y
 CONFIG_USB_CHIPIDEA_HOST=y
+CONFIG_USB_SERIAL=m
+CONFIG_USB_SERIAL_GENERIC=y
+CONFIG_USB_SERIAL_SIMPLE=m
+CONFIG_USB_SERIAL_AIRCABLE=m
+CONFIG_USB_SERIAL_ARK3116=m
+CONFIG_USB_SERIAL_BELKIN=m
+CONFIG_USB_SERIAL_CH341=m
+CONFIG_USB_SERIAL_WHITEHEAT=m
+CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
+CONFIG_USB_SERIAL_CP210X=m
+CONFIG_USB_SERIAL_CYPRESS_M8=m
+CONFIG_USB_SERIAL_EMPEG=m
+CONFIG_USB_SERIAL_FTDI_SIO=m
+CONFIG_USB_SERIAL_VISOR=m
+CONFIG_USB_SERIAL_IPAQ=m
+CONFIG_USB_SERIAL_IR=m
+CONFIG_USB_SERIAL_EDGEPORT=m
+CONFIG_USB_SERIAL_EDGEPORT_TI=m
+CONFIG_USB_SERIAL_F81232=m
+CONFIG_USB_SERIAL_GARMIN=m
+CONFIG_USB_SERIAL_IPW=m
+CONFIG_USB_SERIAL_IUU=m
+CONFIG_USB_SERIAL_KEYSPAN_PDA=m
+CONFIG_USB_SERIAL_KEYSPAN=m
+CONFIG_USB_SERIAL_KEYSPAN_MPR=y
+CONFIG_USB_SERIAL_KEYSPAN_USA28=y
+CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
+CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
+CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
+CONFIG_USB_SERIAL_KEYSPAN_USA19=y
+CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
+CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
+CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
+CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
+CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
+CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
+CONFIG_USB_SERIAL_KLSI=m
+CONFIG_USB_SERIAL_KOBIL_SCT=m
+CONFIG_USB_SERIAL_MCT_U232=m
+CONFIG_USB_SERIAL_METRO=m
+CONFIG_USB_SERIAL_MOS

Re: [meta-freescale] gstreamer1.0 element conflicts

2015-04-15 Thread Tim Harvey 
On Wed, Apr 8, 2015 at 12:40 PM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
 I don't think so. I however can rename the gstreamer-imx one to
 imxv4l2videosrc . Is this acceptable?


Carlos,

I think this would be a fine approach - it would also help differ
gstreamer-imx from the other closed-development plugins.

Tim


 Am 2015-04-08 um 21:01 schrieb Pushpal Sidhu:

 Hi all,

 There is conflict in imxv4l2src as it's provided both by gstreamer-imx
 and gst1.0-fsl-plugins. I renamed the element in gst1.0-fsl-plugins,
 but gstreamer complains that: (gst-plugin-scanner:652):
 GLib-GObject-WARNING **: cannot register existing type
 'GstImxV4l2Src'

 I am currently using the master branch in meta-fsl-arm. Ideally, I
 would like to keep both elements with a rename on the
 gst1.0-fsl-plugins variety. Is there any (simple) method of
 accomplishing this?

 Thanks,
 - Pushpal
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] VPU_EncGetVersionInfo failed

2014-07-16 Thread Tim Harvey 
On Mon, Jul 14, 2014 at 10:11 AM, Allan Matthew amatt...@3drobotics.com wrote:
 I believe I found the issue.  In my device tree I had the VPU supply set to
 pu_dummy when it should have been set to a regulator.  Seems to have fixed
 the issue.

 Allan Matthew
 Embedded Software Engineer, 3DRx
 3D Robotics
 (858) 225-1414
 website | facebook | instagram

Alan,

This info was extremely helpful - I ran into this as well after
recently moving my boards to the 3.10.17_1.0.0-ga kernel. Note that I
also had to set system_rev based on the SOC type so that the imx-vpu
could determine the vpu firmware name... not clear where this was ever
set in Freescale's vendor kernel and thus if VPU even works on the
references boards with the 3.10.17 kernel.

Perhaps Freescale can shed some light on the subject? I'm wondering if
I'm completely misunderstanding the comments in the dts files or if
they are just plain wrong:

imx6qdl-sabresd.dtsi:
vpu {
pu-supply = pu_dummy; /* ldo-bypass:use pu_dummy if VDDSOC
share with VDDPU */
};

The comment above seems to indicate that if you are using LDO-bypass
mode you would set this to pu-dummy. I think this comment is
backwards, and if you are bypassing the LDO you need to set to to
reg_pu (which is what I needed to do on my board to get the VPU
initialized properly).

imx6q-sabresd-ldo.dts:
vpu {
pu-supply = reg_pu; /* ldo-bypass:use pu_dummy if VDDSOC
share with VDDPU */
};

Same comment, different choice. Is 'imx6q-sabresd-ldo.dts' the dtb for
sabresd 'using' the internal LDO or 'bypassing' the internal LDO's? We
are talking about multiple LDO's correct? (LDO_ARM on VDDARM*_CAP*
pins and LDO_SOC on VDDSOC_CAP* pins and LDO_PU on VDDPU_CAP* pins).
On our boards we provide our own VDD_ARM and VDD_SOC to VDDARM*_IN*
and VDDSOC_IN* pins to support the higher freq IMX6Q parts so I have
always assumed I am using 'ldo bypass' mode.

Please advise,

Regards,

Tim



 On Mon, Jul 14, 2014 at 7:36 AM, Lauren Post lauren.p...@freescale.com
 wrote:

 Sorry I was wrong on my part numbers – that is a solo which does have a
 VPU.  The DTS for solo and dual lite are the same.



 From: meta-freescale-boun...@yoctoproject.org
 [mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Lauren Post
 Sent: Monday, July 14, 2014 9:28 AM
 To: Allan Matthew
 Cc: meta-freescale@yoctoproject.org
 Subject: Re: [meta-freescale] VPU_EncGetVersionInfo failed



 On Fri, Jul 11, 2014 at 3:41 PM, Otavio Salvador ota...@ossystems.com.br
 wrote:

 On Fri, Jul 11, 2014 at 6:08 PM, Allan Matthew amatt...@3drobotics.com
 wrote:
  I'm using a custom MCIMX6S5EVM10AC board and am having an issue with the
  vpuenc gstreamer plugin.  I'm able to otherwise use gstreamer plugins
  like
  mfw_v4lsink, tvsrc, mfw_isink etc but the vpu does not seem to be
  working.
  When invoking vpuenc with the h.264 codec, I get the following debug
  error
  from gst-launch:
 
   0:00:02.613795334  1154   0x389920 ERROR vpuenc
  vpuenc.c:441:vpuenc_core_init: func VPU_EncGetVersionInfo failed!! with
  ret



 This part you are using is a i.MX 6 Solo Lite chip which does not have a
 VPU.  That is why you are getting this failure.









 --
 ___
 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