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>
Alex Gonzalez
Javier Viguera