The defaults were taken from linux-fslc
| commit 75de4ee0c2
| Author: Pierre-Jean Texier <pjtexier@koncepto.io>
| Date: Sat Feb 23 17:28:39 2019 +0100
|
| imx7s-warp: Add bcm43430 nvram config
|
| Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
With the next commit
| commit 5d88f226ed
| Author: Alex Gonzalez <alex.gonzalez@digi.com>
| Date: Tue Feb 26 10:29:15 2019 +0100
|
| linux-fslc: ccimx6ul: Adapt to v4.20
|
| * Adapt patches to v4.20
| * Remove patches that are already included in the v4.20 kernel
|
| Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
linux-fslc moved to 4.20 and patches were adjusted.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
The ConnectCore 6UL SBC Pro has a Wi-Fi interface with support for both
station and softAP modes.
This commit adds an interfaces file that defines a wlan0 interface for the
station mode, a wlan1 interface for the softAP mode.
Note that for softAP functionality to work, MAC addresses for the virtual
wireless interfaces need to be programmed in the uboot environment with:
env set wlan1addr aa:cc:cc:xx:yy:zz
env set wlan2addr aa:cc:cc:xx:yy:zz
env set wlan3addr aa:cc:cc:xx:yy:zz
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL SBC Express has a Wi-Fi interface with both station
and softAP functionality. This interfaces file adds the wlan0 interface for
station and wlan1 interface for softAP.
Note that for softAP functionality to work, MAC addresses for the virtual
wireless interfaces need to be programmed in the uboot environment with:
env set wlan1addr aa:cc:cc:xx:yy:zz
env set wlan2addr aa:cc:cc:xx:yy:zz
env set wlan3addr aa:cc:cc:xx:yy:zz
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL System-On-Module comes on different hardware
variants. This commit adds support for the wireless variant with
Qualcomm's QCA6564 WiFi / Bluetooth chipset.
* Modifies the device tree to add the SDIO wireless interface
* Patches the Linux kernel with QCA6564 specific feature additions
* Adds the unused HOSTAP module to the configuration so that the WEXT
config option is selected, even though the module won't be added to
to the target. Out-of-tree drivers have no way of selecting the legacy
WEXT support needed for the QCA6564.
* Removes the probe locking feature from the configuration as the
QCA6564 driver is not as well designed and it oops with warnings:
* Configure Bluetooth RFCOMM support in the kernel
* Sets the quality of the RNG so that it can be used by the kernel
[ 19.479089] ============================================
[ 19.484423] WARNING: possible recursive locking detected
[ 19.489761] 4.19.5-fslc+g093a10401c15 #1 Tainted: G O
[ 19.496135] --------------------------------------------
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This new package contains udev rules for the Digi International SOMs and
SBCs.
It initially contains only rules for the qca6564 Wi-Fi and BT and for the
ccimx6ul SOM, but it will get extended to cover other interfaces and
SOMs.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL SOM contains a Qualcomm QCA6564A wireless and Bluetooth
chipset with the following features:
* Dual band 5GHz 802.11ac or 2.4/5GHz 802.11n support
* Open, WPA and WPA2 personal and enterprise authentication
* AES/TKIP encryption
* Station, softAP and Wi-Fi direct modes
* FCC compliant US regulatory domain support
* Bluetooth 4.2, backwards compatible with older standard revisions
This commit builds an out-of-tree driver for it as well as installs
firmware files for both Wi-Fi and Bluetooth.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The project now expects contributions being made through
GitHub's pull-request feature. Reflect that in the README.
Text mostly taken from the README in meta-qt5.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
The ConnectCore 6UL SBC Pro has two wired ethernet interfaces. This commit
adds an interfaces file with both eth0 and eth1 interfaces.
Note that the ethernet interface that is enabled in U-Boot is the eth1
interface in the Linux kernel.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL Single Board Computer (SBC) Pro contains the
ConnectCore 6UL System-On-Module.
Its hardware specifications are:
* 256MB DDR3 memory
* On module 256MB NAND flash
* Dual 10/100 Ethernet
* USB Host and USB OTG
* Parallel RGB display header
* LVDS display header
* CSI camera
* GPIO header
* I2C, SPI, CAN headers
* PCIe mini card and micro SIM slot
* MicroSD external storage
* On board 4GB eMMC flash
* Audio headphone, line in/out, microphone lines
The build artifacts are:
U-Boot images: u-boot.imx
Linux partition image: <image name>.boot.ubifs
Root filesystem image: <image name>.ubifs
Root filesystem tarball (for network booting): <image name>.tar.bz2
To program a board from the U-boot prompt, copy the U-Boot, Linux and
root filesystem partition images to your TFTP server root and do:
env set ipaddr <target ip address>
env set serverip <TFTP server ip address>
update uboot tftp u-boot.imx
update linux tftp <image name>.boot.ubifs
update rootfs tftp <image name>.ubifs
More details about the SBC can be found at:
https://www.digi.com/products/embedded-systems/single-board-computers/connectcore-for-i-mx6ul-sbc-pro
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Generalize the boot script used to boot Linux so that it can be shared
by multiple ConnectCore 6UL SOM based boards.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Adapt the interfaces file to the single wired ethernet available on the
ConnectCore 6UL SBC Express board.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit prepares for the introduction of a second ConnectCore 6UL
System-On-Module based board by grouping the SOM configuration into its
own file avoiding code redundancy.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCore 6UL SOM and SBC Express are already included in upstream
v4.19.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The ConnectCore 6UL Single Board Computer (SBC) Express contains the
ConnectCore 6UL System-On-Module.
Its hardware specifications are:
* 256MB DDR3 memory
* 256MB NAND flash
* Single Ethernet
* USB Host and USB-OTG
* MicroSD external storage
* Groove connectors and Raspberry Pi Hat compatible expansion heade
The build artifacts are:
U-Boot images: u-boot.imx
Linux partition image: <image name>.boot.ubifs
Root filesystem image: <image name>.ubifs
Root filesystem tarball (for network booting): <image name>.tar.bz2
To program a board from the U-boot prompt, copy the U-Boot, Linux and
root filesystem partition images to your TFTP server root and do:
env set ipaddr <target ip address>
env set serverip <TFTP server ip address>
update uboot tftp u-boot.imx
update linux tftp <image name>.boot.ubifs
update rootfs tftp <image name>.ubifs
More details about the SBC can be found at:
https://www.digi.com/products/embedded-systems/single-board-computers/connectcore-for-i-mx6ul-sbc-express
The ConnectCore 6UL SBC Express includes a ConnectCore 6UL
System-On-Module with the following specification:
* Based on a NXP i.MX6UL SoC
* Industrial temperature ranges (-40ºC to +85ºC)
* Up to 1GB DDR3 memory
* Up to 2GB NAND flash
* Dual Ethernet
* On module 802.11 WiFi and Bluetooth 4.2 (QCA6564)
* On module NXP Kinetis KL03
* On module Microchip ATECC508A crypto element
More details about the SOM can be found at:
https://www.digi.com/products/embedded-systems/system-on-modules/connectcore-for-i-mx6ul
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The support for the ConnectCore 6UL SOM and SBC Express is available in
v4.19 so it is added as patches here.
The GPMI BCH layout change is needed to match the kernel with the
NXP IMX vendor based U-Boot used in the ConnectCore 6UL SOM.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This vendor U-Boot is based on v2017.03 and currently supports two
ConnectCore 6UL memory variants, 256MB and 1GB.
To program this U-Boot from a running TFTP server
type the following at the U-Boot prompt:
env set ipaddr <target IP address>
env set serverip <TFTP server IP address>
update linux tftp <filename>
Where filename is:
* u-boot.imx-ccimx6ulstarter - for 256MB variants
* u-boot.imx-ccimx6ulstarter1GB - for 1GB variants
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This patch adds a new boot.ubifs image type that is programmed into the
boot partition of the NAND based ConnectCore modules.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
I observed a following build issue:
| ***
| *** Can't find default configuration "arch/../configs/colibri_imx7_emmc_defconfig"!
| ***
| scripts/kconfig/Makefile:128: recipe for target 'colibri_imx7_emmc_defconfig' failed
it's due to the colibri_imx7_emmc_defconfig does not exist in the
source, because u-boot-toradex and u-boot-fw-utils are not built from
same source. so the toradex machine specific uboot configs do not
present in the default u-boot-fw-utils source.
To fix it, a new u-boot-toradex-fw-utils recipe is added, it uses the
same source with u-boot-toradex, some common code is split out to
u-boot-toradex.inc, to be shared by both u-boot-toradex and
u-boot-toradex-fw-utils.
And we need set PREFERRED_PROVIDER and PREFERRED_RPROVIDER in machine
configs to u-boot-toradex-fw-utils.
Some files derive from u-boot-toradex-fw-utils recipe of:
git://git.toradex.com/meta-toradex-nxp.git
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Add the git repository in the recipe in order to build u-boot for
Gateworks imx6 boards.
Signed-off-by: Sandra Tobajas <sandra.tobajas@savoirfairelinux.com>
This adds the bcm4339 nvram configuration which allows the use of WiFi
connectivity out of box, using latest Linux FSLC release.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Now that the kernel headers are fixed to 4.9 in meta-freescale, 3rd
party kernel better match that same version.
We currently do not have the bandwidth to maintain such RT version so
remove it to avoid confusion.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Update with the ARMv7 defconfig to enable IPU and display
Signed-off-by: Ken Lin <ken.lin@advantech.com>
Signed-off-by: Ken Lin <yungching0725@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
It fails to build for non-arm machines anyway since it does not provide
the needed env file for anything other than arm and aarch64
Let cross version build too
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
From: Ian Coolidge <ian@boundarydevices.com>
Compatible with nitrogem8m board
Blog post: https://boundarydevices.com/u-boot-v2018-07/
Signed-off-by: Ian Coolidge <ian@boundarydevices.com>
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
