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>
They contain the sha1s of the upstream poky, meta-fsl-arm and
meta-openembedded we are basing this drop on. These sha1s are also
included in the manifest file for the drop so they could safely be removed
from here once we are building release images on the Jenkins server.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Running:
bitbake -c cleanall packagegroup-machine-base
was failing due to those trailing backslashes.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-331
While on it, fix whitespace problems (mixed tabs + spaces) in the
bitbake recipe.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The previous "+=" format was doing a complete variable override instead
of an append. Features like usbhost or usbdevice were disappearing.
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>
Remove the machine rdepends and move to del-wireless which is only
included for the wifi machine feature.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* don't use a login shell to run the script. It overrides the
environment that comes from the caller script.
* optimize MAC address parsing
* enable 'P2P' and softmac on driver's load
https://jira.digi.com/browse/DEL-412
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This version of the driver can be redistributed, so remove the
build-from-objects part of the recipes.
https://jira.digi.com/browse/DEL-412
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- Merge SRCREVS
- Remove UBOOT_MAKE_TARGET_paltform as they already are in machine
configuration files.
- Merge DEPENDS_mxs_platform as they are equal.
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>
According to the Poky reference manual, SUMMARY inherits DESCRIPTION, so
it's better to have only a DESCRIPTION or both.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
INC_PR is used in include files to that the recipes that include them
can use it to increment the PR.
In this recipe what we need is to set the PR.
An example from the Yocto dev manual:
recipes-graphics/xorg-font/xorg-font-common.inc:INC_PR = "r2"
recipes-graphics/xorg-font/encodings_1.0.4.bb:PR = "${INC_PR}.1"
recipes-graphics/xorg-font/font-util_1.3.0.bb:PR = "${INC_PR}.0"
recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
All bbappend files will start as follows:
# Copyright (C) 2013 Digi International.
PRINC := "${@int(PRINC) + 1}"
PR_append = "+${DISTRO}"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This recipe install an init script that allows to set some alsa audio
parameters without having to touch the default alsa states.
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>
We can'se use the 1.3 Danny tag as it's broken, use the head.
Fixes https://jira.digi.com/browse/DEL-366
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Not yet finished as not all the cpx2 variants support wireless.
This has to be enabled per-variant.
https://jira.digi.com/browse/DEL-134
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was causing module loading issues on del-image-graphical.
Fixes https://jira.digi.com/browse/DEL-338
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Do not generate them until they are properly tested and working.
Fixes https://jira.digi.com/browse/DEL-192
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Following the guidelines in kernel documentation:
linux-tree/Documentation/kbuild/modules.txt
https://jira.digi.com/browse/DEL-134
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
kobs-ng is needed to be able to flash the bootloader from user space
in mxs platforms.
Fixes https://jira.digi.com/browse/DEL-340
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>
udev will attempt to load the atheros kernel modules because it defines
a modalias that matches an sdio bus event.
In a race condition with the script in if-pre-up, the module will crash.
Recent versions of udev have lost the ability to add an ignore_device
option to the rules, and mdev in del-image-minimal has no module
autoloading ability.
The commit adds a modprobe install rule that does nothing, and allows
the if-pre-up script to load the module as it used to.
Fixes https://jira.digi.com/browse/DEL-277
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit adds a Digi premirror to the DEL distribution file. This
premirror will be tried first. It default to build-linux.digi.conf but
will be customized for the layer public release.
This still allows for a project to be customizes with a
SOURCE_MIRROR_URL which will be tried before the premirrors.
Fixes https://jira.digi.com/browse/DEL-186
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The del-image-minimal will included the graphical acceleration libraries
if the machine supports accel-graphics.
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>
So they don't depend on the machine files from meta-fs-arm layer.
This allows to override some settings in project's local.conf file.
https://jira.digi.com/browse/DEL-219 #resolve
Signed-off-by: Javier Viguera <javier.viguera@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>
While on it, revert PROVIDES to its previous state, not depending on
DISTRO_FEATURES. This was tweaked to avoid a bitbake warning. Not it is
solved in a conditional BBMASK.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This fixes a bug in 'ccardxmx28js' where the wpa_supplicant was using
the wrong driver 'wext' instead of the 'nl80211' (for atheros)
https://jira.digi.com/browse/DEL-220 #resolve
Signed-off-by: Javier Viguera <javier.viguera@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>
The bootloader is passing the mac address and wdmode in the kernel command
line.
The driver startup script reads and and sets them.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The bootloader is passing the mac address in the kernel command line.
The driver startup script reads it and sets it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Seems that the options Yocto was using to generate the jffs flash image
are not correct for ccardxmx28js. Specially mkfs.jffs2's padding option
'-p' was making the rootfs corrupted on second boot (as explained in
JIRA DEL-218).
Finally i decided to use the same mkfs.jffs2 parameters we were using in
DEL and those seems to be working fine.
https://jira.digi.com/browse/DEL-218 #resolve
Signed-off-by: Javier Viguera <javier.viguera@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>
U-Boot has a set of pre-defined make targets per platform that allow
to configure u-boot for different variants (128sdram,4Kpage,dbg etc.)
This change allows to use a UBOOT_CONFIG_VARIANT variable in your
local.conf file to choose which variant to build.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The ConnectCard needs a bootstreamed (.sb) u-boot to boot from flash. This
is flashed using u-boot.
This changes compiles a bootstream u-boot image. The bootlets are compiled
separately and it's U-Boot's Makefile that calls elftosb to generate the
final bootstream.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Alex Gonzalez
Javier Viguera
Francis Sreeves
Hector Palacios