[meta-fsl-arm][PATCH 1/2] imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra

[meta-fsl-arm][PATCH 1/2] imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra

[Otavio Salvador]

The SabreLITE is much better supported by Boundary kernel as being not
fully supported by Freescale new BSPs it should be moved to the Extra
layer where we can properly support it.

Change-Id: Ie6465c35a243cb199c3499eb4336c9638c9ce6ab
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 conf/machine/imx6qsabrelite.conf | 16 ----------------
 1 file changed, 16 deletions(-)
 delete mode 100644 conf/machine/imx6qsabrelite.conf

diff --git a/conf/machine/imx6qsabrelite.conf b/conf/machine/imx6qsabrelite.conf
deleted file mode 100644
index 6a0cef9..0000000
--- a/conf/machine/imx6qsabrelite.conf
+++ /dev/null
@@ -1,16 +0,0 @@
-#@TYPE: Machine
-#@NAME: i.MX6Q SABRE Lite
-#@DESCRIPTION: Machine configuration for Freescale i.MX6Q SABRE Lite
-
-include conf/machine/include/imx-base.inc
-include conf/machine/include/tune-cortexa9.inc
-
-SOC_FAMILY = "mx6q:mx6"
-
-KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabrelite.dts"
-
-UBOOT_MACHINE = "mx6qsabrelite_config"
-
-SERIAL_CONSOLE = "115200 ttymxc1"
-
-MACHINE_FEATURES += " pci wifi bluetooth"
-- 
1.8.1

[meta-fsl-arm-extra][PATCH 1/3] linux-boundary: Add recipe for Boundary Devices kernel

[Otavio Salvador]

This provides a kernel for use with SabreLITE and Nitrogen6X boards.

Change-Id: I02477254b2986ffb05b81b264121527238800fcd
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 .../linux/linux-boundary-3.0.35/defconfig          | 278 +++++++++++++++++++++
 recipes-kernel/linux/linux-boundary_3.0.35.bb      |  16 ++
 2 files changed, 294 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-boundary-3.0.35/defconfig
 create mode 100644 recipes-kernel/linux/linux-boundary_3.0.35.bb

diff --git a/recipes-kernel/linux/linux-boundary-3.0.35/defconfig b/recipes-kernel/linux/linux-boundary-3.0.35/defconfig
new file mode 100644
index 0000000..a0eacb8
--- /dev/null
+++ b/recipes-kernel/linux/linux-boundary-3.0.35/defconfig
@@ -0,0 +1,278 @@
+CONFIG_EXPERIMENTAL=y
+CONFIG_SYSVIPC=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_LOG_BUF_SHIFT=14
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_EMBEDDED=y
+CONFIG_PERF_EVENTS=y
+CONFIG_MODULES=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_MODULE_FORCE_UNLOAD=y
+CONFIG_MODVERSIONS=y
+# CONFIG_BLK_DEV_BSG is not set
+CONFIG_ARCH_MXC=y
+CONFIG_GPIO_PCA953X=y
+CONFIG_ARCH_MX6=y
+CONFIG_FORCE_MAX_ZONEORDER=14
+CONFIG_MACH_MX6Q_SABRELITE=y
+CONFIG_IMX_PCIE=y
+CONFIG_USB_EHCI_ARC_H1=y
+CONFIG_USB_FSL_ARC_OTG=y
+CONFIG_MXC_PWM=y
+CONFIG_MXC_REBOOT_MFGMODE=y
+CONFIG_CLK_DEBUG=y
+CONFIG_DMA_ZONE_SIZE=184
+# CONFIG_SWP_EMULATE is not set
+CONFIG_ARM_ERRATA_743622=y
+CONFIG_ARM_ERRATA_751472=y
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_764369=y
+CONFIG_NO_HZ=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_SMP=y
+CONFIG_VMSPLIT_2G=y
+CONFIG_PREEMPT=y
+CONFIG_AEABI=y
+# CONFIG_OABI_COMPAT is not set
+CONFIG_HIGHMEM=y
+CONFIG_COMPACTION=y
+CONFIG_KSM=y
+CONFIG_ZBOOT_ROM_TEXT=0x0
+CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_CMDLINE="noinitrd console=ttymxc0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 ip=off"
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPU_FREQ_IMX=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
+CONFIG_SUSPEND_DEVICE_TIME_DEBUG=y
+CONFIG_PM_RUNTIME=y
+CONFIG_PM_DEBUG=y
+CONFIG_APM_EMULATION=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_MULTICAST=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_DHCP=y
+CONFIG_IP_PNP_BOOTP=y
+# CONFIG_INET_LRO is not set
+# CONFIG_IPV6 is not set
+CONFIG_NETFILTER=y
+CONFIG_LLC2=y
+CONFIG_CAN=y
+CONFIG_CAN_RAW=y
+CONFIG_CAN_BCM=y
+CONFIG_CAN_VCAN=y
+CONFIG_CAN_FLEXCAN=y
+CONFIG_BT=y
+CONFIG_BT_L2CAP=y
+CONFIG_BT_SCO=y
+CONFIG_BT_RFCOMM=y
+CONFIG_BT_RFCOMM_TTY=y
+CONFIG_BT_BNEP=y
+CONFIG_BT_BNEP_MC_FILTER=y
+CONFIG_BT_BNEP_PROTO_FILTER=y
+CONFIG_BT_HIDP=y
+CONFIG_BT_HCIUART=y
+CONFIG_BT_HCIUART_LL=y
+CONFIG_CFG80211=y
+CONFIG_MAC80211=y
+CONFIG_RFKILL=y
+CONFIG_RFKILL_INPUT=y
+CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+CONFIG_CONNECTOR=y
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_CHAR=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_M25P80=y
+CONFIG_MTD_NAND=y
+CONFIG_MTD_UBI=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_MISC_DEVICES=y
+CONFIG_MXS_PERFMON=m
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_MULTI_LUN=y
+CONFIG_ATA=y
+# CONFIG_SATA_PMP is not set
+CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_NETDEVICES=y
+CONFIG_TUN=y
+CONFIG_MII=y
+CONFIG_MICREL_PHY=y
+CONFIG_NET_ETHERNET=y
+CONFIG_FEC_NAPI=y
+# CONFIG_NETDEV_1000 is not set
+# CONFIG_NETDEV_10000 is not set
+CONFIG_HOSTAP=y
+CONFIG_WL12XX_MENU=y
+CONFIG_WL12XX=y
+CONFIG_WL12XX_SDIO=m
+CONFIG_INPUT_POLLDEV=y
+CONFIG_INPUT_EVDEV=y
+CONFIG_KEYBOARD_GPIO=y
+# CONFIG_INPUT_MOUSE is not set
+CONFIG_INPUT_TOUCHSCREEN=y
+CONFIG_TOUCHSCREEN_EGALAX=y
+CONFIG_TOUCHSCREEN_EGALAX_SINGLE_TOUCH=y
+CONFIG_TOUCHSCREEN_FT5X06=y
+CONFIG_TOUCHSCREEN_FT5X06_SINGLE_TOUCH=y
+CONFIG_TOUCHSCREEN_TSC2004=y
+CONFIG_INPUT_MISC=y
+CONFIG_INPUT_UINPUT=y
+CONFIG_INPUT_ISL29023=y
+CONFIG_VT_HW_CONSOLE_BINDING=y
+CONFIG_SERIAL_IMX=y
+CONFIG_SERIAL_IMX_CONSOLE=y
+CONFIG_FSL_OTP=y
+CONFIG_HW_RANDOM=y
+CONFIG_MXS_VIIM=y
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_IMX=y
+CONFIG_SPI=y
+CONFIG_SPI_IMX=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_SENSORS_MAX17135=y
+CONFIG_SENSORS_MAG3110=y
+# CONFIG_MXC_MMA8450 is not set
+CONFIG_WATCHDOG=y
+CONFIG_WATCHDOG_NOWAYOUT=y
+CONFIG_IMX2_WDT=y
+CONFIG_MFD_WM8994=y
+CONFIG_MFD_PFUZE=y
+CONFIG_MFD_MAX17135=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_PFUZE100=y
+CONFIG_REGULATOR_MAX17135=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_VIDEO_DEV=y
+# CONFIG_RC_CORE is not set
+# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
+CONFIG_VIDEO_MXC_CAMERA=m
+CONFIG_MXC_CAMERA_OV5642=m
+CONFIG_MXC_IPU_DEVICE_QUEUE_SDC=m
+CONFIG_USB_VIDEO_CLASS=m
+# CONFIG_RADIO_ADAPTERS is not set
+CONFIG_DRM=m
+CONFIG_DRM_VIVANTE=m
+CONFIG_FB=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+# CONFIG_LCD_CLASS_DEVICE is not set
+CONFIG_BACKLIGHT_CLASS_DEVICE=y
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_FB_MXC_LDB=y
+CONFIG_FB_MXC_BT656=y
+CONFIG_FB_MXC_MIPI_DSI=y
+CONFIG_FB_MXC_TRULY_WVGA_SYNC_PANEL=y
+CONFIG_FB_MXC_TVOUT_ADV739X=y
+CONFIG_FB_MXC_HDMI=y
+CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FONTS=y
+CONFIG_FONT_8x16=y
+CONFIG_LOGO=y
+CONFIG_SOUND=y
+CONFIG_SND=y
+CONFIG_SND_USB_AUDIO=y
+CONFIG_SND_SOC=y
+CONFIG_SND_IMX_SOC=y
+CONFIG_SND_SOC_IMX_SGTL5000=y
+CONFIG_SND_SOC_IMX_SPDIF=y
+CONFIG_SND_SOC_IMX_HDMI=y
+CONFIG_HIDRAW=y
+CONFIG_HID_QUANTA=y
+CONFIG_HID_SAMSUNG=m
+CONFIG_HID_SONY=m
+CONFIG_HID_SUNPLUS=m
+CONFIG_USB=y
+CONFIG_USB_DEVICEFS=y
+# CONFIG_USB_DEVICE_CLASS is not set
+CONFIG_USB_SUSPEND=y
+# CONFIG_USB_OTG_WHITELIST is not set
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_EHCI_ARC=y
+CONFIG_USB_EHCI_ROOT_HUB_TT=y
+# CONFIG_USB_EHCI_TT_NEWSCHED is not set
+CONFIG_USB_ACM=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_SERIAL=y
+CONFIG_USB_SERIAL_QUALCOMM=y
+CONFIG_USB_SERIAL_OPTION=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_ETH=m
+CONFIG_USB_FILE_STORAGE=m
+CONFIG_USB_G_SERIAL=m
+CONFIG_USB_CDC_COMPOSITE=m
+CONFIG_MXC_OTG=y
+CONFIG_MMC=y
+CONFIG_MMC_UNSAFE_RESUME=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_ESDHC_IMX=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_GPIO=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_INTF_DEV_UIE_EMUL=y
+CONFIG_RTC_DRV_SNVS=y
+CONFIG_DMADEVICES=y
+CONFIG_MXC_PXP_V2=y
+CONFIG_IMX_SDMA=y
+CONFIG_MXC_IPU=y
+# CONFIG_MXC_HMP4E is not set
+# CONFIG_MXC_HWEVENT is not set
+CONFIG_MXC_ASRC=y
+CONFIG_MXC_GPU_VIV=y
+CONFIG_MXC_MIPI_CSI2=y
+CONFIG_EXT2_FS=y
+CONFIG_EXT3_FS=y
+# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
+CONFIG_EXT4_FS=y
+CONFIG_AUTOFS4_FS=y
+CONFIG_MSDOS_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_JFFS2_FS=y
+CONFIG_UBIFS_FS=y
+CONFIG_CRAMFS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3=y
+CONFIG_ROOT_NFS=y
+CONFIG_PARTITION_ADVANCED=y
+CONFIG_EFI_PARTITION=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ASCII=m
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_UTF8=m
+CONFIG_MAGIC_SYSRQ=y
+CONFIG_DEBUG_FS=y
+CONFIG_SYSCTL_SYSCALL_CHECK=y
+# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
+CONFIG_CRYPTO_TEST=m
+CONFIG_CRYPTO_CCM=y
+CONFIG_CRYPTO_GCM=y
+CONFIG_CRYPTO_CBC=y
+CONFIG_CRYPTO_CTS=y
+CONFIG_CRYPTO_LRW=y
+CONFIG_CRYPTO_PCBC=y
+CONFIG_CRYPTO_XTS=y
+CONFIG_CRYPTO_DES=y
+# CONFIG_CRYPTO_ANSI_CPRNG is not set
+CONFIG_CRYPTO_DEV_FSL_CAAM=y
+# CONFIG_CRYPTO_DEV_FSL_CAAM_AHASH_API is not set
+CONFIG_CRC_CCITT=m
diff --git a/recipes-kernel/linux/linux-boundary_3.0.35.bb b/recipes-kernel/linux/linux-boundary_3.0.35.bb
new file mode 100644
index 0000000..196c3ba
--- /dev/null
+++ b/recipes-kernel/linux/linux-boundary_3.0.35.bb
@@ -0,0 +1,16 @@
+# Adapted from linux-imx.inc, copyright (C) 2013 O.S. Systems Software LTDA
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+require recipes-kernel/linux/linux-imx.inc
+
+DESCRIPTION = "Linux kernel for Boundary Devices boards"
+
+INC_PR = "r1"
+
+SRC_URI = "git://github.com/boundarydevices/linux-imx6.git \
+           file://defconfig"
+
+LOCALVERSION = "-1.1.0"
+SRCREV = "2dc5560fddb82b26c7010978361c28aad42fc023"
+
+COMPATIBLE_MACHINE = "(mx6)"
-- 
1.8.1

[meta-fsl-arm-extra][PATCH 2/3] imx6qsabrelite: Add Boundary Devices SabreLITE machine definition

[Otavio Salvador]

This adds the Boundary Devices SabreLITE machine which were maintained
in meta-fsl-arm. We did this change as the support of the board is not
done by Freescale officially and the kernel with better support is the
one done by Boundary Devices which we now have available.

Change-Id: Ie040b38e23885fa164bb4cd25d8c4b0b00471e5c
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 conf/machine/imx6qsabrelite.conf | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 conf/machine/imx6qsabrelite.conf

diff --git a/conf/machine/imx6qsabrelite.conf b/conf/machine/imx6qsabrelite.conf
new file mode 100644
index 0000000..46abdd3
--- /dev/null
+++ b/conf/machine/imx6qsabrelite.conf
@@ -0,0 +1,18 @@
+#@TYPE: Machine
+#@NAME: i.MX6Q SABRE Lite
+#@DESCRIPTION: Machine configuration for Boundary Devices i.MX6Q SABRE Lite
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa9.inc
+
+SOC_FAMILY = "mx6q:mx6"
+
+KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabrelite.dts"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-boundary"
+
+UBOOT_MACHINE = "mx6qsabrelite_config"
+
+SERIAL_CONSOLE = "115200 ttymxc1"
+
+MACHINE_FEATURES += " pci wifi bluetooth"
-- 
1.8.1

[meta-fsl-arm-extra][PATCH 3/3] nitrogen6x: Change machine to use linux-boundary kernel

[Otavio Salvador]

Change-Id: Ie815cf603657385e3220640c7773f2d3eaee7c8b
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 conf/machine/nitrogen6x.conf | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf
index d668eb2..dc61b63 100644
--- a/conf/machine/nitrogen6x.conf
+++ b/conf/machine/nitrogen6x.conf
@@ -2,15 +2,13 @@
 #@NAME: Nitrogen6X
 #@DESCRIPTION: Machine configuration for Boundary Devices Nitrogen6X
 
-# We need to override the default before everything
-MACHINEOVERRIDES = "${MACHINE}:imx6qsabrelite"
-
 include conf/machine/include/imx-base.inc
 include conf/machine/include/tune-cortexa9.inc
 
 SOC_FAMILY = "mx6q:mx6"
 
 PREFERRED_PROVIDER_u-boot = "u-boot-boundary"
+PREFERRED_PROVIDER_virtual/kernel = "linux-boundary"
 
 # Use SPI NOR U-Boot by default
 IMAGE_BOOTLOADER ?= ""
-- 
1.8.1

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

Hi Otavio,

On 04/06/2013 09:30 AM, Otavio Salvador wrote:
> The SabreLITE machine is now supported using the Boundary Devices
> kernel in meta-fsl-arm-extra, so we remove the patch and specific
> overrides of this recipe.
>
> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>   .../imx6qsabrelite/sync-boundary-changes.patch     | 7473 --------------------
>   recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>   3 files changed, 7748 deletions(-)
>   delete mode 100644 recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>   delete mode 100644 recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>

Are there dependencies on this patch?

It didn't apply cleanly based on Master+patch 1 of the series.

Please advise,


Eric

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> Hi Otavio,
>
>
> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>
>> The SabreLITE machine is now supported using the Boundary Devices
>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>> overrides of this recipe.
>>
>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>> ---
>>   .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>   .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>> --------------------
>>   recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>   3 files changed, 7748 deletions(-)
>>   delete mode 100644
>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>   delete mode 100644
>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>
>
> Are there dependencies on this patch?
>
> It didn't apply cleanly based on Master+patch 1 of the series.

My tree looks like:

5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
680c6a3 gst-plugins-gl: Avoid leaking memory

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

On 04/06/2013 10:13 AM, Otavio Salvador wrote:
> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi Otavio,
>>
>>
>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>
>>> The SabreLITE machine is now supported using the Boundary Devices
>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>> overrides of this recipe.
>>>
>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>> ---
>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>> --------------------
>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>    3 files changed, 7748 deletions(-)
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>
>>
>> Are there dependencies on this patch?
>>
>> It didn't apply cleanly based on Master+patch 1 of the series.
>
> My tree looks like:
>
> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
> 680c6a3 gst-plugins-gl: Avoid leaking memory
>
Thanks Otavio,

It looks like I had some leftover stuff in my local tree and
'repo init -b master' didn't fix it...

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>
>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> Hi Otavio,
>>>
>>>
>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>> overrides of this recipe.
>>>>
>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>> ---
>>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>>> --------------------
>>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>>    3 files changed, 7748 deletions(-)
>>>>    delete mode 100644
>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>>    delete mode 100644
>>>>
>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>>
>>>
>>> Are there dependencies on this patch?
>>>
>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>
>>
>> My tree looks like:
>>
>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>
> Thanks Otavio,
>
> It looks like I had some leftover stuff in my local tree and
> 'repo init -b master' didn't fix it...

You might use, next time:

repo sync
repo start test-otavio-patches --all

So it creates a new branch with current commited code.

Regards,

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]

On 04/06/2013 02:07 PM, Otavio Salvador wrote:
> On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>>
>>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>>
>>>> Hi Otavio,
>>>>
>>>>
>>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>>> overrides of this recipe.
>>>>>
>>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>> ---
>>>>
>>>> Are there dependencies on this patch?
>>>>
>>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>>
>>> My tree looks like:
>>>
>>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>>
>> Thanks Otavio,
>>
>> It looks like I had some leftover stuff in my local tree and
>> 'repo init -b master' didn't fix it...
>
> You might use, next time:
>
> repo sync
> repo start test-otavio-patches --all
>
> So it creates a new branch with current commited code.
>

Thanks for the tip Otavio.

I've validated build success and that the kernel boots properly
with this series.

I'm not having success getting X to start up though.

Is the master branch known to have issues with DRM?

I'm seeing this in /var/log/Xsession.log:
	/usr/bin/Xorg: symbol lookup error: 
/usr/lib/xorg/modules/drivers/vivante_drv.so: undefined symbol: 
gcoHAL_MapUserMemory



[-- Attachment #2: Xsession.log --]
[-- Type: text/x-log, Size: 1631 bytes --]


_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/nitrogen6x:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-40-generic x86_64 
Current Operating System: Linux nitrogen6x 3.0.35-1.1.0+g2dc5560 #1 SMP PREEMPT Sat Apr 6 12:30:39 MST 2013 armv7l
Kernel command line: enable_wait_mode=off video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 video=mxcfb1:off video=mxcfb2:off fbmem=28M console=ttymxc1,115200 vmalloc=400M root=/dev/mmcblk0p2 rootwait consoleblank=0
Build Date: 06 April 2013  01:24:27PM
 
Current version of pixman: 0.29.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr  8 14:34:00 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) Failed to load module "extmod" (module does not exist, 0)
(EE) Failed to load module "dbe" (module does not exist, 0)
(EE) Failed to load module "dri2" (module does not exist, 0)
/usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/vivante_drv.so: undefined symbol: gcoHAL_MapUserMemory
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Mon, Apr 8, 2013 at 12:01 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 04/06/2013 02:07 PM, Otavio Salvador wrote:
>>
>> On Sat, Apr 6, 2013 at 2:30 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> On 04/06/2013 10:13 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> On Sat, Apr 6, 2013 at 2:08 PM, Eric Nelson
>>>> <eric.nelson@boundarydevices.com> wrote:
>>>>>
>>>>>
>>>>> Hi Otavio,
>>>>>
>>>>>
>>>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>>>> overrides of this recipe.
>>>>>>
>>>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>>> ---
>>>>>
>>>>>
>>>>> Are there dependencies on this patch?
>>>>>
>>>>> It didn't apply cleanly based on Master+patch 1 of the series.
>>>>
>>>>
>>>> My tree looks like:
>>>>
>>>> 5928872 linux-imx: Cleanup recipe as SabreLITE machine has been moved
>>>> 1e6c433 imx6qsabrelite: Move to SabreLITE to meta-fsl-arm-extra
>>>> 680c6a3 gst-plugins-gl: Avoid leaking memory
>>>>
>>> Thanks Otavio,
>>>
>>> It looks like I had some leftover stuff in my local tree and
>>> 'repo init -b master' didn't fix it...
>>
>>
>> You might use, next time:
>>
>> repo sync
>> repo start test-otavio-patches --all
>>
>> So it creates a new branch with current commited code.
>>
>
> Thanks for the tip Otavio.

Great.

> I've validated build success and that the kernel boots properly
> with this series.

Good. I will apply this patch series.

> I'm not having success getting X to start up though.
>
> Is the master branch known to have issues with DRM?
>
> I'm seeing this in /var/log/Xsession.log:
>         /usr/bin/Xorg: symbol lookup error:
> /usr/lib/xorg/modules/drivers/vivante_drv.so: undefined symbol:
> gcoHAL_MapUserMemory

This does seem to be a regression and I will look at it later today.
Thanks for letting us know about it.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

Hi Otavio,

On 04/06/2013 09:30 AM, Otavio Salvador wrote:
> The SabreLITE machine is now supported using the Boundary Devices
> kernel in meta-fsl-arm-extra, so we remove the patch and specific
> overrides of this recipe.
>
> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>   .../imx6qsabrelite/sync-boundary-changes.patch     | 7473 --------------------
>   recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>   3 files changed, 7748 deletions(-)
>   delete mode 100644 recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>   delete mode 100644 recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>

It seems that this broke something. Machine-type "imx6qsabrelite" will
fail to fetch because of a missing defconfig file.

With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
doesn't know to search in "nitrogen6x/" as shown below.

Is there a way to fix this besides copying the directory?


ERROR: Fetcher failure: Unable to find file file://defconfig anywhere. 
The paths that were searched were:
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.0.35/
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary/
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/arm
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/armv7a
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/mx6
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/mx6q
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/imx6qsabrelite
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/poky
 
/home/ericn/yoctosl/sources/meta-fsl-arm-extra/recipes-kernel/linux/files/
     /home/ericn/yoctosl/downloads/

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> Hi Otavio,
>
> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>
>> The SabreLITE machine is now supported using the Boundary Devices
>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>> overrides of this recipe.
>>
>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>> ---
>>   .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>   .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>> --------------------
>>   recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>   3 files changed, 7748 deletions(-)
>>   delete mode 100644
>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>   delete mode 100644
>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>
>
> It seems that this broke something. Machine-type "imx6qsabrelite" will
> fail to fetch because of a missing defconfig file.
>
> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
> doesn't know to search in "nitrogen6x/" as shown below.
>
> Is there a way to fix this besides copying the directory?

Yes; you can add it to the MACHINEOVERRIDES.

You can add to imx6qsabrelite.conf:

MACHINEOVERRIDES =. "nitrogen6x"

This should do the trick.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

On 10/16/2013 10:04 AM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> Hi Otavio,
>>
>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>
>>> The SabreLITE machine is now supported using the Boundary Devices
>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>> overrides of this recipe.
>>>
>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>> ---
>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>> --------------------
>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>    3 files changed, 7748 deletions(-)
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>    delete mode 100644
>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>
>>
>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>> fail to fetch because of a missing defconfig file.
>>
>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>> doesn't know to search in "nitrogen6x/" as shown below.
>>
>> Is there a way to fix this besides copying the directory?
>
> Yes; you can add it to the MACHINEOVERRIDES.
>
> You can add to imx6qsabrelite.conf:
>
> MACHINEOVERRIDES =. "nitrogen6x"
>
> This should do the trick.
>
Thanks Otavio.

I had to use "=" instead of "=." or the fetch process would look
in a directory named "nitrogen6ximx6qsabrelite/".

A patch is forthcoming.

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>
>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> Hi Otavio,
>>>
>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>> overrides of this recipe.
>>>>
>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>> ---
>>>>    .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>>    .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>>> --------------------
>>>>    recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>>    3 files changed, 7748 deletions(-)
>>>>    delete mode 100644
>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>>    delete mode 100644
>>>>
>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>>
>>>
>>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>>> fail to fetch because of a missing defconfig file.
>>>
>>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>>> doesn't know to search in "nitrogen6x/" as shown below.
>>>
>>> Is there a way to fix this besides copying the directory?
>>
>>
>> Yes; you can add it to the MACHINEOVERRIDES.
>>
>> You can add to imx6qsabrelite.conf:
>>
>> MACHINEOVERRIDES =. "nitrogen6x"
>>
>> This should do the trick.
>>
> Thanks Otavio.
>
> I had to use "=" instead of "=." or the fetch process would look
> in a directory named "nitrogen6ximx6qsabrelite/".
>
> A patch is forthcoming.

MACHINEOVERRIDES =. "nitrogen6x:"

With the : it would work.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

On 10/16/2013 01:21 PM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>
>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>>
>>>> Hi Otavio,
>>>>
>>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>>> overrides of this recipe.
>>>>>
>>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>> ---
>>>>>     .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>>>     .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>>>> --------------------
>>>>>     recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>>>     3 files changed, 7748 deletions(-)
>>>>>     delete mode 100644
>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>>>     delete mode 100644
>>>>>
>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>>>
>>>>
>>>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>>>> fail to fetch because of a missing defconfig file.
>>>>
>>>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>>>> doesn't know to search in "nitrogen6x/" as shown below.
>>>>
>>>> Is there a way to fix this besides copying the directory?
>>>
>>>
>>> Yes; you can add it to the MACHINEOVERRIDES.
>>>
>>> You can add to imx6qsabrelite.conf:
>>>
>>> MACHINEOVERRIDES =. "nitrogen6x"
>>>
>>> This should do the trick.
>>>
>> Thanks Otavio.
>>
>> I had to use "=" instead of "=." or the fetch process would look
>> in a directory named "nitrogen6ximx6qsabrelite/".
>>
>> A patch is forthcoming.
>
> MACHINEOVERRIDES =. "nitrogen6x:"
>
> With the : it would work.
>

Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).

Any problem with just = "nitrogen6x"?

Since we don't have a proper imx6qsabrelite directory, this seems
a reasonable approach.

Please advise,


Eric

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Otavio Salvador]

On Wed, Oct 16, 2013 at 5:24 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 10/16/2013 01:21 PM, Otavio Salvador wrote:
>>
>> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
>> <eric.nelson@boundarydevices.com> wrote:
>>>
>>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>>
>>>>
>>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>>> <eric.nelson@boundarydevices.com> wrote:
>>>>>
>>>>>
>>>>> Hi Otavio,
>>>>>
>>>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>>>> overrides of this recipe.
>>>>>>
>>>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>>> ---
>>>>>>     .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>>>>     .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>>>>> --------------------
>>>>>>     recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>>>>     3 files changed, 7748 deletions(-)
>>>>>>     delete mode 100644
>>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>>>>     delete mode 100644
>>>>>>
>>>>>>
>>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>>>>
>>>>>
>>>>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>>>>> fail to fetch because of a missing defconfig file.
>>>>>
>>>>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>>>>> doesn't know to search in "nitrogen6x/" as shown below.
>>>>>
>>>>> Is there a way to fix this besides copying the directory?
>>>>
>>>>
>>>>
>>>> Yes; you can add it to the MACHINEOVERRIDES.
>>>>
>>>> You can add to imx6qsabrelite.conf:
>>>>
>>>> MACHINEOVERRIDES =. "nitrogen6x"
>>>>
>>>> This should do the trick.
>>>>
>>> Thanks Otavio.
>>>
>>> I had to use "=" instead of "=." or the fetch process would look
>>> in a directory named "nitrogen6ximx6qsabrelite/".
>>>
>>> A patch is forthcoming.
>>
>>
>> MACHINEOVERRIDES =. "nitrogen6x:"
>>
>> With the : it would work.
>>
>
> Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).
>
> Any problem with just = "nitrogen6x"?
>
> Since we don't have a proper imx6qsabrelite directory, this seems
> a reasonable approach.

Yes but if we need a SABRELite dir in future we'll need to change it again.

It is up to you.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-fsl-arm][PATCH 2/2] linux-imx: Cleanup recipe as SabreLITE machine has been moved

[Eric Nelson]

On 10/16/2013 01:30 PM, Otavio Salvador wrote:
> On Wed, Oct 16, 2013 at 5:24 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 10/16/2013 01:21 PM, Otavio Salvador wrote:
>>>
>>> On Wed, Oct 16, 2013 at 5:10 PM, Eric Nelson
>>> <eric.nelson@boundarydevices.com> wrote:
>>>>
>>>> On 10/16/2013 10:04 AM, Otavio Salvador wrote:
>>>>>
>>>>>
>>>>> On Wed, Oct 16, 2013 at 1:27 PM, Eric Nelson
>>>>> <eric.nelson@boundarydevices.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Otavio,
>>>>>>
>>>>>> On 04/06/2013 09:30 AM, Otavio Salvador wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The SabreLITE machine is now supported using the Boundary Devices
>>>>>>> kernel in meta-fsl-arm-extra, so we remove the patch and specific
>>>>>>> overrides of this recipe.
>>>>>>>
>>>>>>> Change-Id: I109226bf6fc5f5d9979430795b990dfe09b11421
>>>>>>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
>>>>>>> ---
>>>>>>>      .../linux-imx-3.0.35/imx6qsabrelite/defconfig      |  272 -
>>>>>>>      .../imx6qsabrelite/sync-boundary-changes.patch     | 7473
>>>>>>> --------------------
>>>>>>>      recipes-kernel/linux/linux-imx_3.0.35.bb           |    3 -
>>>>>>>      3 files changed, 7748 deletions(-)
>>>>>>>      delete mode 100644
>>>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/defconfig
>>>>>>>      delete mode 100644
>>>>>>>
>>>>>>>
>>>>>>> recipes-kernel/linux/linux-imx-3.0.35/imx6qsabrelite/sync-boundary-changes.patch
>>>>>>>
>>>>>>
>>>>>> It seems that this broke something. Machine-type "imx6qsabrelite" will
>>>>>> fail to fetch because of a missing defconfig file.
>>>>>>
>>>>>> With MACHINE="imx6qsabrelite", the fetch command for "linux-boundary"
>>>>>> doesn't know to search in "nitrogen6x/" as shown below.
>>>>>>
>>>>>> Is there a way to fix this besides copying the directory?
>>>>>
>>>>>
>>>>>
>>>>> Yes; you can add it to the MACHINEOVERRIDES.
>>>>>
>>>>> You can add to imx6qsabrelite.conf:
>>>>>
>>>>> MACHINEOVERRIDES =. "nitrogen6x"
>>>>>
>>>>> This should do the trick.
>>>>>
>>>> Thanks Otavio.
>>>>
>>>> I had to use "=" instead of "=." or the fetch process would look
>>>> in a directory named "nitrogen6ximx6qsabrelite/".
>>>>
>>>> A patch is forthcoming.
>>>
>>>
>>> MACHINEOVERRIDES =. "nitrogen6x:"
>>>
>>> With the : it would work.
>>>
>>
>> Rats! I tried ":nitrogen6x" and got the same thing (nitrogen6ximx6q...).
>>
>> Any problem with just = "nitrogen6x"?
>>
>> Since we don't have a proper imx6qsabrelite directory, this seems
>> a reasonable approach.
>
> Yes but if we need a SABRELite dir in future we'll need to change it again.
>

I hope we don't. The kernel takes care of all of that, and we should
be moving to consolidate via DT.

> It is up to you.
>

My preference is to use the patch as given and move forward.

Right now, the "imx6qsabrelite" machine type is simply broken.

Regards,


Eric