This commit re-adds the imx-gpu-g2d recipe that was removed
from the imx-gpu-viv v6 driver.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the GPU driver
to the latest version.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the Vivante GPU
driver to the latest version and refresh patches.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the defconfig for the platform ccimx6qpsbc
to the kernel v4.9 and modifies the recipe.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit modifies different recipes to support the new platform
ccimx6qpsbc and adapt it to maintain the support to ccimx6sbc.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit includes ccimx6qpsbc platform in the recipe and adds
U-Boot scripts for deploying and booting the system.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add initial support for Digi's ConnectCore 6 QuadPlus SBC.
The ccimx6qp platform has the QCA6564 chip instead of the
other Atheros chips and included the Atmel ECC508A cryptographic
chip.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The patch is needed to match the API kernel changes. This fixes:
zc.c:68:44: error: passing argument 7 of 'get_user_pages_remote' from incompatible pointer type [-Werror=incompatible-pointer-types]
(unsigned long)addr, pgcount, write, 0, pg, NULL);
^~
In file included from zc.c:28:0:
kernel-source/include/linux/mm.h:1276:6: note: expected 'struct vm_area_struct **' but argument is of type 'struct page **'
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
zc.c:63:8: error: too many arguments to function 'get_user_pages_remote'
ret = get_user_pages_remote(
^~~~~~~~~~~~~~~~~~~~~
In file included from zc.c:28:0:
kernel-source/include/linux/mm.h:1276:6: note: declared here
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
https://jira.digi.com/browse/DEL-5081
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
CC6 PS_ASIC_class_1.pst MD5SUM be8766069eed652449682d9006dd6ecd
https://jira.digi.com/browse/DEL-5057
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
The current value only allows partitions of up to 8 MiB, which is not
enough for the 0x04 variant (which uses a linux partition of 24 MiB by
default).
This new value allows for up to 32 MiB (assuming 128 KiB erase block size).
Also add comments explaining the -c value and maximum partition sizes
supported.
https://jira.digi.com/browse/DEL-4971
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
After the 'ccardimx28js' platform removal, these variables and machine
features are not used anymore, so remove them.
https://jira.digi.com/browse/DEL-4771
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need to pass different log levels depending on the message, so they
appear in the console, so generalize the 'log' function.
https://jira.digi.com/browse/DEL-4682
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the point this script is running from udev (the system log is not yet
available), so to avoid debug messages from qualcomm wireless module
reduce the console log level.
https://jira.digi.com/browse/DEL-4570
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This is required to be able to use the whole RootFS partition which is
512 MiB in the 0x04 CC6UL SOM variant.
The old value only allowed to manage partitions of up to 256 MiB, this new
value allows for up to 1 GiB (assuming 128 KiB erase block size).
https://jira.digi.com/browse/DEL-4567
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
At the point this script is run (from udev) the system log is not yet
available, so use the kernel log buffer instead.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the same udev script that loads the qualcomm wireless module to
create the 'wlan1' virtual interface.
https://jira.digi.com/browse/DEL-4453
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Udev comes with a bunch of generic rules for the hardware. One of them:
/lib/udev/rules.d/80-drivers.rules
is able to load the qualcomm wireless module.
At the same time our new rule is needed, so it prepares the firmware
before the module is loaded.
Both rules running collide with following error message:
udevd[181]: '/etc/udev/scripts/qualcomm.sh' [184] terminated by signal 1 (Hangup)
So to fix this, we rename the specific rule so it's parsed later, and
then we use the hard assignation '=' instead of '+=' to override the
values that come from the previous parsed rule.
Also clean-up a bit the 'qualcomm.sh' script and the modprobe file,
given that now we know the standard drivers rule won't run for this
interface.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
NetworkManager is not able to detect and manage the wireless interface
until is actually created, so let udev load the kernel module and create
the interface on boot.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
The new fw-4.bin (v3.4.0.236) with md5sum e2fc33daba2c35fe2c4f62492a44f8b6
was used to pass RED (Radio Equipment Directive) certification on the CC6
module.
https://jira.digi.com/browse/DEL-4512
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Arturo Buzarra
Jose Diaz de Grenu
Hector Palacios
Francisco Gil
Mike Engel
Javier Viguera
Sebastian Pastor
Alex Gonzalez