* without this tune-xscale and tune-arm926ejs were both creating
packages in armv5te feed, but each with different -mtune, with
OEBasicHash enabled it was causing each package to rebuild with new
-mtune after MACHINE switch, but that doesn't make sense with output
stored in the same armv5te feed
* this makes different feed for each -mtune, but more generic one to be
selected with DEFAULTTUNE
* tune-iwmmxt and tune-ep9312 were already using this, just move it
bellow AVAILTUNES and use ARMPKGARCH_tune-foo syntax
* tune-cortexr4 and tune-cortexm3 are using armv7r/armv7m as ARMPKGARCH
because there isn't another tune to use the same -march
(From OE-Core rev: cffda9a821a3b83a8529d643c567859e091c6846)
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* this is mostly for backwards compatibility and to share binary feed
like it was before, but now without missing different -mtune in it
* if you want to build some package with -mtune add something like this
to your distro config
DEFAULTTUNE_qemuarm_pn-openssl = "arm926ejs"
DEFAULTTUNE_qemuarmx_pn-openssl = "xscale"
be aware that if you do this you should do it also for all packages
which depends on openssl because if you dont and you build e.g. dhcp,
then dhcp build for arm926ejs (even with DEFAULTTUNE armv5te) will
depend on openssl with arm926ejs, so dhcp in armv5te feed will be
rebuild after each MACHINE switch.
* cortexm3, cortexr4, iwmmx and ep9312 are using own DEFAULTTUNE because
they define also different -march
* shared feeds are
armv4t: arm920t, arm9tdmi
armv5te: arm926ejs, xscale
armv7a-neon: cortexa8, cortexa9
(From OE-Core rev: a11bdc36a1be18cc5aa14682b2a2c9ee83141f51)
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
GPU_MEM
gpu_mem - GPU memory in megabyte. Sets the memory split between the ARM and
GPU. ARM gets the remaining memory. Min 16. Default 64
GPU_MEM_256
gpu_mem_256 -GPU memory in megabyte for the 256MB Raspberry Pi. Ignored by
the 512MB RP. Overrides gpu_mem. Max 192.
GPU_MEM_512
gpu_mem_512 -GPU memory in megabyte for the 512MB Raspberry Pi. Ignored by
the 256MB RP. Overrides gpu_mem. Max 448.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
config.txt allows several overclocking parameters to be tweakes. This makes
the most important ones overridable through local.conf.
Signed-off-by: Julian Scheel <julian@jusst.de>
Add a DISABLE_OVERSCAN variable that can be used in local.conf to overwrite
the overscan default setting.
Signed-off-by: Julian Scheel <julian@jusst.de>
Using DEPLOY_DIR_IMAGE bypasses the sstate cache. This causes a build
failure when the kernel is pulled from sstate.
Signed-off-by: Tyler Hall <tylerwhall@gmail.com>
This was done to avoid errors like:
| *** Error: Package name contains illegal characters, (other than [a-z0-9.+-])
while using ipk.
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
It makes no sense to have distro related configurations in a BSP
layer. So let's have these common parts (provides, version etc)
in machine directory instead.
[GITHUB #73]
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
The build-time kernel command line (as defined by the CONFIG_CMDLINE config
parameter) is not respected by the RPI bootloader, and instead any custom
command line must be suplied via the cmdline.txt file in the boot partition.
This patch modifies the linux-raspberrypi recipe to generate a cmdline.txt
file that corresponds to the build-time configured command line, and it
also modifies the sdcard_image-rpi.bbclass to include this file in the
generated SD card images.
[GITHUB #62]
Signed-off-by: Tomas Frydrych <tomas@sleepfive.com>
Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
