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