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>
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>
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>
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>
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>
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>
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>
Javier Viguera
Seth Bollinger
Alex Gonzalez
Francis Sreeves