Platform defconfig corresponds to sha1 'e1506ff' in the kernel.
At this point linux-3.10 continues to be the default, some device-tree
files were renamed and the external atheros module does not compile with
linux-3.14, so to use this kernel with dey-1.8, following lines are
needed in the project's local.conf:
PREFERRED_VERSION_linux-dey = "3.14"
KERNEL_DEVICETREE = " \
imx6dl-ccimx6sbc-wb.dtb \
imx6dl-ccimx6sbc-w.dtb \
imx6q-ccimx6sbc.dtb \
imx6q-ccimx6sbc-wb.dtb \
imx6q-ccimx6sbc-wb-ldo-bypass.dtb \
imx6q-ccimx6sbc-w.dtb \
"
MACHINE_FEATURES_remove = "wifi"
https://jira.digi.com/browse/DEL-1748
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also remove kernel configuration fragments for kernel 3.10. This is not
needed for 3.10 as all the configuration is done via device-trees.
https://jira.digi.com/browse/DEL-1695
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit b0031915f1c7f3eeba680161827e78bbac9eebb4)
Also remove support for device tree variants as it's not needed. We will
only have different device tree for the different CPUs, but not for the
different variants of the same CPU.
https://jira.digi.com/browse/DEL-1569
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The way the kernel is built in yocto 1.8 has changed. Now the
build is done under ${WORKDIR}/build while the source code is at
STAGING_KERNEL_DIR, so we need to modify the '.config' in the build
directory instead of in the source directory.
This fixes:
kernel-source is not clean, please run 'make mrproper'
make[2]: *** [prepare3] Error 1
make[1]: *** [sub-make] Error 2
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This completes the support for ccimx6sbc variants:
* support device tree variants
* split variants '0x01,0x02,0x04' group in two different groups (with or
without kinetis)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 3f20015411f4e270b2e2c8faf292678c75ff2aff)
Notes:
* This version of u-boot does not support comments in scripts
* Enabled EXT4 in kernel config (for the SDCARD rootfs)
https://jira.digi.com/browse/DEL-197
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
User-space has been updated in meta-fsl-arm for the general availability
(GA) FSL release, so use the kernel branch with the GA support.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The 'v3.10/master' master branch has been updated with the latest
general availability (GA) release from FSL, but the user-space is not
ready yet, so using the new kernel the build is broken:
imx-lib: error: 'PXP_IOC_GET_CHAN' undeclared
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Needing to set the branch where a specific SHA1 revision is contained is
a unnecessary constraint that can be bypassed setting 'nobranch=1' in
the SRC_URI.
We do that for all the external repos (GitHub) plus the internal ones
for the im-xbootlets and the atheros kernel module (as those two repos
are stable enough and we are not developing actively on them).
For U-Boot and Linux we keep the SRCBRANCH framework for internal repos
as this is needed for the AUTOREV yocto feature.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Starting with Yocto 1.6 there is a need to configure in which branch a
specific SHA1 revision is included. We need a framework to set such
branches both for internal git repos and for external ones (Github).
If the branch is not specified in the SRC_URI, the do_fetch task may
fail even though the SHA1 revision exists in the repository.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This workaround is not needed anymore as the git fetcher bug is fixed in
poky's master branch.
This reverts commit 982af63902.
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
PR was based on meta-fsl-arm's 'linux-imx.inc' INC_PR, but this was
removed after Dora, so we need to remove PR from our kernel recipes to
avoid a bitbake parser error:
${INC_PR}.0/git')} exception SyntaxError: EOL while scanning string literal
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
linux-dey.inc is a copy of meta-fsl-arm's linux-imx recipe file, so
instead of copying the whole recipe just use that (including the file)
and code the differences.
While on it, add RDEPENDS_kernel-base="" to remove the dependence of the
rootfs image recipes on the linux image. We don't need/use the kernel
image in the rootfs as we load it from a different partition. This makes
rootfs images a bit smaller.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
change the directory (cd) and make the symbolic link in a subshell to
preserve the current working directory for any subsequent command.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
bitbake git's fetcher uses 'ls-remote' to get the branch revision to
checkout. If the repository has two branches ending equally the 'git
ls-remote' just picks the first one regardless of that being the correct
one.
In our case we were bitten by this bug because our git repo has:
...sha1-revision... refs/heads/android/v3.10/master
...sha1-revision... refs/heads/v3.10/master
and the fetcher was using the android branch instead of linux's
v3.10/master.
A patch has been sent upstream but while that gets applied to Dora
maintenance branch the workaround here is to set the absolute path in
the kernel's bitbake recipe.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The do_update_dts function was hardcoded for ccardimx28js. We need to
make it mxs specific so the recipe can be used for other platforms that
do not share the same device tree configuration (for example the
upcoming ccimx6js)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The Linux kernel revision was splitted from main bitbake recipe to its
own linux-dey-rev file so that file could be used for linux-headers
recipe to build the toolchain using custom kernel headers (from our
repository).
That is not the recommended way to build a toolchain:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=babbf7a46acaefd9b36031483cafce053f607e66
and we are not using our kernel headers to build the toolchain anymore,
so just melt the linux-dey-rev files into the linux-dey bitbake recipes
for cleanness and easier maintenance.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Committed a patch in linux-dey repo to fix perf build. At the same
time update linux-dey revision to get the perf fix.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
They conflict.
Warn the user about the problem and let they change the device tree
manually.
https://jira.digi.com/browse/DEL-840
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Those boolean helper variables can be used in different recipes so move
them to a common place.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also change the default ccardimx28js variant to 'web1' (wireless, second
ethernet, bluetooth and 1-wire)
https://jira.digi.com/browse/DEL-819
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Most SRC_URI defaults to DIGI_LOG_GIT. This patch sets a more generic
name (DIGI_GIT) that defaults to DIGI_LOG_GIT, but is configurable by
someone who might want to tune it (DIGI_MTK_GIT, etc.).
Signed-off-by: Seth Bollinger <sethb@digi.com>
To get the latest changes: logo, mac-address, wireless...
Also synchronize the defconfig with the one in the kernel tree.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT variables are only used in
the kernel recipe, so remove from the machine configuration files.
Also, use the defconfig from the kernel tree which compiles all the
support by default and expects the device tree to be configured with
the desired support. Hence, remove all the empty configuration fragments
files.
https://jira.digi.com/browse/DEL-577
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is to work as in previous kernels. For now the fragments are empty
and they will have to be individually included and tested.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Copy including folders. This was causing problems in kernel version 3.10
as the directory included folders that were omitted in the copy and caused
the do_install to fail.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Remove support that is to be added as a config fragment:
- FB support.
- LCD backlight.
- Sound.
Add configuration that was also enabled in previous kernels.
- Serial, ethernet and storage USB gadgets.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Placing all of the revision info in a common include we avoid the common
issue of forgetting to update the linux-libc-headers append recipe when
the kernel is updated.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The external repositories have been cleaned up and commits have been
squashed so the sha1s need to be updated.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
https://jira.digi.com/browse/DEL-472
While on it, fix minor bug: uImage-<platform> symbolic link was not
being created on deployment directory.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Fix the kernel wireless configuration fragment, and add a couple of kernel
patches to set up the mmc0 interface to be used with the wireless and
remove an incorrect pin configuration.
There are similar patched to this on the gateways/master branch related to
the vehicle bus adapter product.
meta-digi-arm/conf/machine/cpx2.conf
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
It is now based on the ConnectCard defconfig instead of the gateways
product one. This makes more sense in this layer, and upper layers
can overwrite it if needed.
https://jira.digi.com/browse/DEL-462
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
I have split the machine configuration in two:
-The module machine configuration include, for example ccimx53.inc
-The machine configuration (for example cimx53js.conf) which includes
the variant configuration.
This will allow for customers to create their own machine keeping the
module include file.
The variant can be configured in the local.conf file with a
MACHINE_VARIANT variable.
The variant names are made up of the interface initials as follows:
w: wifi
e: externel ethernel
b: bluetooth
1: 1-wire
a: accelerometer
g: GPU
v: VPU
128: 128MB RAM
4k: 1024MB NAND (only for MX51 JTAG flash)
For details regarding the supported variants, each machine configuration
file contains a comment with a variants table.
https://jira.digi.com/browse/DEL-330
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
They all have a copyright and the all do:
PR = "${DISTRO}.${INC_PR}.0"
Then recipes which include them include:
PR = "${DISTRO}.${INC_PR}.0"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
On a release, the kernel will not be built from a git repo but
from a source tarball.
Make the default to build from a tarball.
https://jira.digi.com/browse/DEL-362
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Create a symlink on the deploy folder that matches the standard uboot
name for the kernel.
Fixes partially https://jira.digi.com/browse/DEL-283
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The del-examples-sahara now depends on the kernel modules it needs to
work and these are autoloaded at boot.
Fixes DEL-274.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
For this the CCIMX51 and CCIMX53 kernels are configured to build the
mma7455l module and it is included as a dependency of the del-examples-
accelerometer application.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This conflicts with user led 2 used in the GPIO example add and with
other interfaces needed in the del-image-graphical image.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Wakeup interrupts were not happening upon USB stick plug
events during normal work. This had the effect of the
interrupt happenign when going to suspend and usually when
the driver is not able to handle it, causing a nobody cared
message from the kernel.
https://jira.digi.com/browse/CCIMX28-326
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Just a cosmetic name change for the merged wired and wireless platforms.
This and related commits fixes https://jira.digi.com/browse/DEL-188.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Also enable CONFIG_BRIDGE in kernel configs (which is required to use
brctl)
https://jira.digi.com/browse/DEL-156 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Enable RFKILL. Otherwise on boot we get an error message:
rfkill: Cannot open RFKILL control device
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need the kernel configuration file in /boot for some of the postint
scripts that aim to do smart things like autoconfigure the interfaces file.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
These new defconfigs are needed after merging the wireless and non wireless
products in the linux kernel source.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Alex Gonzalez
Javier Viguera
Seth Bollinger
Francis Sreeves
Hector Palacios