Commit Graph

17 Commits

Author SHA1 Message Date
Javier Viguera fb9ec7221a meta-digi: add variants table to config templates
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit db1782bd24c4347cb9f4db33210e0f3fd6e73298)
2015-02-05 16:29:29 +01:00
Javier Viguera adb4611710 meta-digi-arm: disable perf features only for kernel 2.6.35
Kernel 3.10 does not fail to build perf features (as kernel 2.6.35
does), so there is no need to disable them for platforms using that
kernel version.

https://jira.digi.com/browse/DEL-1418

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2015-01-19 18:28:00 +01:00
Javier Viguera e55fc16544 meta-digi-arm: migrate module_autoload to KERNEL_MODULE_AUTOLOAD
For MX5 platforms.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-12-02 16:49:45 +01:00
Javier Viguera 09e72aa0f4 meta-digi-arm: simplify flash images generation
We inherited from DEL the requirement to build more than one flash image
for the same rootfs contents depending on the EBS of the flash chip.

Yocto does not have support to generate more than one flash image so we
had to create functions in the image_types_digi bbclass to provide this
feature.

This commit removes that functionality and uses the standard yocto
support to generate ubifs and jffs2 flash images. The way to customize
the flash parameters is via EXTRA_IMAGECMD_jffs2 and MKUBIFS_ARGS
variables. In our case those variables are already set depending on the
different hardware variants.

https://jira.digi.com/browse/DEL-232

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-12-02 16:49:12 +01:00
Javier Viguera 1a54b81586 meta-digi-arm: add support for Digi platform families
Add platform family to SOC_FAMILY, so it's part of the MACHINEOVERRIDES
variable and it can be used to generalize bitbake recipes.

https://jira.digi.com/browse/DEL-1105

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-07-16 14:39:00 +02:00
Javier Viguera 2d2013e8da meta-digi: install mtd-utils-ubifs only in machines with flash memory
The ccimx6 does not have flash memory so there is no need to install
mtd-utils.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-03-14 12:50:31 +01:00
Alex Gonzalez 45f329b27a meta-digi-arm: add the ccimx6adpt machine
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-02-24 12:33:59 +01:00
Javier Viguera 1466a3ff79 meta-digi-arm: move UBOOT_SUFFIX to the machine config files
So it can be used out of the u-boot recipe (for example to create
bootable sdcard images).

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-01-16 10:37:04 +01:00
Javier Viguera 0dc6b44dee meta-digi: do not hardcode machine related utilities
nvram, ubootenv and update_flash are machine related utilities. They
need to be configured per-platform via MACHINE_EXTRA_RDEPENDS and thus
leaving packagegroup-dey-core as much platform-agnostic as possible.

This also allows to skip these utilities for platforms not using them.

https://jira.digi.com/browse/DEL-915

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-01-15 17:32:30 +01:00
Javier Viguera 0f34d4907d meta-digi-arm: fix UBOOT_ENTRYPOINT for all platforms
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2014-01-15 14:37:23 +01:00
Javier Viguera a554c7be17 meta-digi-arm: fix SOC_FAMILY for all platforms
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2013-10-17 10:35:26 +02:00
Javier Viguera 7ee47e607e meta-digi-arm: rework variants support
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>
2013-05-14 10:16:26 +02:00
Javier Viguera 3874c057e2 meta-dig-arm: fix variant names
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2013-05-10 17:56:03 +02:00
Javier Viguera e0fed036fa config templates: set default platform variants
https://jira.digi.com/browse/DEL-438

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2013-05-07 16:18:07 +02:00
Javier Viguera 0bc9f87e2f meta-digi: fix corner case broken build
Running:

bitbake -c cleanall packagegroup-machine-base

was failing due to those trailing backslashes.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2013-04-29 18:35:40 +02:00
Alex Gonzalez c83eed3126 meta-digi-arm: Use append format for variant override.
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>
2013-04-25 15:20:17 +02:00
Alex Gonzalez c3c816ec52 Add support for variants
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>
2013-04-22 17:28:44 +02:00