wmiconfig is Atheros proprietary code so the recipe builds from source
if DIGI_INTERNAL_GIT is defined or uses a prebuilt binary otherwise.
https://jira.digi.com/browse/DEL-640
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We are now using yocto kernel headers (3.x) in the toolchain so the
patches need to be applied regardless of the version of the running
kernel.
Signed-off-by: Javier Viguera <javier.viguera@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 machine variant is most specific than machine name.
Before: MACHINEOVERRIDES="armv5:mxs:wb:ccardimx28js"
After: MACHINEOVERRIDES="armv5:mxs:ccardimx28js:wb"
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If people are creating derivative machines in their layer, make
COMPATIBLE_MACHINE more flexible. Use SOC_FAMILY instead of specific
machine types. This allows users to more easily share these recipes.
https://jira.digi.com/browse/DEL-676
Signed-off-by: Seth Bollinger <sethb@digi.com>
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Modify the atheros and bluetooth init scripts to fetch the hwid details
from the device tree.
https://jira.digi.com/browse/DEL-572
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Similar commit was done in DEL.
Japanese law limits the maximum transmit power for Bluetooth to 3 mW.
The cert field in OTP will be set to 2 when units are manufactured
for Japan.
Updated the bluez init script to configure Bluetooth for class 2
operation if the cert field is set to 2, and to delete the class 1
configuration file since it would be illegal to use it in Japan.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In Linux 2.6.35, the kernel module accepting the parameters on load
was 'ath6kl_sdio' while in 3.10 is 'ath6kl_core'.
So we need to apply the load parameters to either module depending on
the kernel version.
This is solved by configuring the modprobe configuration file
'/etc/modprobe.d/atheros.conf' with the parameters to the correct
module instead of passing them in the command line.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With the old version of the kernel (2.6.35) we build an external atheros
kernel module, while with the new kernel (3.10) the atheros driver is
included with the kernel sources.
However, the new driver needs the firmware files and the driver load
scripts that are stored with the old driver.
So put a dependence on kernel-module-atheros regardless of the kernel
version and then rework the kernel-module-atheros recipe to build the
whole driver for the old kernel or only the firmware for the new kernel.
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>
move ccardimx28js specific patch under PN-PV subdirectory. Otherwise it
fails to find the patch (this version of yocto restricts the FILESPATH
where to look for files)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ERROR: Fetcher failure: Unable to find file file://atheros anywhere
The FILESPATH variable (used as the search path for files referred to
in SRC_URI) is now (dylan) more restrictive, so move the files where
they can be found.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The build was failing for any IMX platform because it was trying to
build a bootstream u-boot.
The u-boot variables (UBOOT_*) used by yocto were incorrectly set,
so I reworked and simplified them to fix the bug and ease maintenance.
https://jira.digi.com/browse/DEL-562
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
QA Issue: Variable ALLOW_EMPTY is set as not being package specific
QA Issue: Variable RPROVIDES is set as not being package specific
Signed-off-by: Javier Viguera <javier.viguera@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>
The 2.6.35.14 kernel calls the serial device ttyAM0 while the 3.10 which
uses a different driver calls it ttyAMA0.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
We need separate linux-libc-recipes if we want to support different
kernels.
On the 1.4 meta-fsl-arm layer this recipe will disappear, so review then.
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 public branches of those repositories have been cleaned up so
the external sha1s have changed.
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>
This lowers the maintenance of these layers. The manifest used with repo
deals with the specific sha1s.
https://jira.digi.com/browse/DEL-495
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is the FTP site where the release artifacts will be placed. It's
structure will be something like:
x.y.z/
source
images
toolchains
adt-installer
https://jira.digi.com/browse/DEL-473
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>
Otherwise a dev or sdk image which include the dev-pkgs image feature
will fail.
https://jira.digi.com/browse/DEL-488
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Another option would be to split it up in machine folders, but it is
similar enough in all platforms not to need this for the time being.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
Mostly cosmetic changes to clear it a bit so customers can use it as
documentation for what variant they need to configure in their projects.
Also a couple of minor fixes: 'ext-eth' typo and duplicated 'e' variant
for ccimx53js.
https://jira.digi.com/browse/DEL-460
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This manually reverts commit ecfdf6ae23.
Once mdev was removed as a dependency from del-image-graphical, we need
udev to load the firmware files for the wireless drivers. This job was
being done by mdev.
The reason for the commit in the first place was that both mdev and udev
were attempting to load the firmware files, so we changed the udev
rule to ignore the atheros driver. This was only needed when mdev and
udev were both running.
https://jira.digi.com/browse/DEL-450https://jira.digi.com/browse/DEL-450
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
If you don't want to use meta-digi-del and use only the BSP layer
(meta-digi-arm) to build a generic image (like core-image-minimal) you
need the DIGI_MIRROR variable in this layer because some of the BSP
recipes (kernel, u-boot) use it to get the source.
So this allows to build core-image-minimal for Digi platforms without
using meta-digi-del.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Alex Gonzalez
Seth Bollinger
Francis Sreeves