openembedded-core.git/meta/conf/machine, branch dylan

qemu*: restrict NFSD to linux-yocto only

2013-05-31T15:03:38+00:00

In the current releases, not all linux-yocto derived kernels have NFS
support, or NFS support fragments availble. To ensure that derived
kernels like linux-yocto-cutom continue to work against poky-lsb,
we can make the KERNEL_FEATURE append more specific to the linux-yocto
recipe.

(From OE-Core master rev: 799f53e8844748a930a9cbc7a4cf1056f19bb037)

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

qemu: Ensure kernel nfsd module is enabled

2013-05-20T15:06:21+00:00

This will ensure that qemu images that include the nfs-server package have the kernel
feature correctly enabled

(From OE-Core master rev: 57c718c6288f2a2538173cdd3d401d70f939a40a)

Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

conf/machine: use .= instead of += in TUNE_CCARGS

2013-05-20T15:06:12+00:00

* number of TUNE_CCARGS conditionals is important if we add
  extra space with each one in "else" branch

  I'm building for 2 MACHINEs one is cortexa9, second is cortexa8

  few months ago we added TUNE_CCARGS[vardepvalue] in bitbake.conf
  http://git.openembedded.org/openembedded-core/commit/?id=03f1e34ea3ce80931e9c3cd2ab22824f28a7233b

  which fixed some cases (like mentioned tune-xscale and tune-arm926ejs)
  where both had unused TUNE_CCARGS when common DEFAULTTUNE was used.

  with cortexa[89] it's different, because cortexa9 has one extra TUNE_CCARGS
  TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "cortexa9", "-mtune=cortex-a9", "", d)}"
  which adds extra *space* even when not used because of '+=' and as result:

  $ bitbake-diffsigs tmp-eglibc/sstate-diff/1366797730/*/armv7*/adapterbase/*do_configure*
  basehash changed from f986789fb8fb3579ed6a3492cc8a8d10 to c851b5f838d945ee13072e9ad6725dca
  Variable TUNE_CCARGS value changed from
  ' -march=armv7-a     -mthumb-interwork -mfloat-abi=softfp -mfpu=neon '
  to
  ' -march=armv7-a     -mthumb-interwork -mfloat-abi=softfp -mfpu=neon  '
  Hash for dependent task gcc-runtime_4.7.bb.do_populate_sysroot changed from bdeabf7a86958b9110b566344b7916de to 2be5618e6bc8c57ec9db5659bf217915
  Hash for dependent task eglibc_2.17.bb.do_populate_sysroot changed from b4f40fc62dde684acd0a574532a55360 to 97fcb426603d4a1c1099c0504d2ebf7d
  Hash for dependent task glib-2.0_2.34.3.bb.do_populate_sysroot changed from fd2f90b83098c34e88d649d70f6ea4f5 to ebd740bb94ea3eb0a914efda6fc82c4a

(From OE-Core master rev: b7430ff83760ac29079d20dc7c62f498a0a9d55d)

Signed-off-by: Martin Jansa 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

tune-thumb.inc: Remove, replaced by arm/feature-arm-thumb.inc

2013-05-20T15:06:12+00:00

(From OE-Core master rev: f4b451c8ad8f857b1789d75d68ce8ea8fc73542e)

Signed-off-by: Martin Jansa 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

qemux86*.conf: replace XSERVER weak assignment with a hard one

2013-03-27T11:05:31+00:00

Because the qemu.inc is now included before the XSERVER assignment, the
xf86-video-vmware and xf86-video-vmmouse are not built and the X for
qemux86 and qemux86-64 does not start.

[YOCTO #4124]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

conf/machine: Clean up MACHINEOVERRIDES handling

2013-03-25T17:39:36+00:00

OVERRIDES reads from left to right, least to most specific. We were
appending to MACHINEOVERRIDES when we should have been prepending so
the ordering of qemuall verses qemuxxx was incorrect, as was the x86
override and several of the arm overrides. This patch is a batch cleanup
of the various issues to correct the order from least to most specific.
The include order does matter and we needed to tweak some of that in this
patch too.

[YOCTO #4090]

Signed-off-by: Richard Purdie

mesa: rename mesa-dri recipe to just mesa

2013-03-22T17:03:09+00:00

Rename mesa-dri recipes to just mesa. Also, replace all references to
mesa-dri in all recipes/configs.

The reason for this renaming (quote from bugzilla):

"mesa-dri is a artefact of mesa-xlib existing, which doesn't anymore.
mesa-dri should be renamed to mesa."

[YOCTO #3385]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

tune-xscale: Drop unneeded optimisation overrides

2013-03-18T13:10:06+00:00

These hacks have been around for years and deal with old gcc issues.
They've been removed from the other use sites, we should clean up the
core tune file too.

Signed-off-by: Richard Purdie

tune-cortexa*: Fix TUNE_FEATURES and PACKAGE_EXTRA_ARCHS for thf-neon

2013-03-09T06:39:03+00:00

* all cortexa*thf-neon except cortexa8 were missing thumb feature from
  TUNE_FEATURES_tune-armv7athf-neon
* all cortexa*thf-neon except cortexa8 included cortexa9t2-vfp instead
  of cortexa9t2hf-vfp
* PACKAGE_EXTRA_ARCHS_tune-cortexa8thf-neon was including from armv7a
  -PACKAGE_EXTRA_ARCHS_tune-armv7ahf-neon
  +PACKAGE_EXTRA_ARCHS_tune-armv7athf-neon
* please do more testing for this, I'm sending this commit mostly
  because I've noticed that new a7 and a15 differ from a8 more then I've
  expected and I don't have any a7/a15 MACHINEs, feel free to extend
  http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune2-test
  to add and test fake a7/a15 configs

Signed-off-by: Martin Jansa 
Signed-off-by: Richard Purdie

soc-family: fix SOC_FAMILY override order

2013-03-09T06:10:16+00:00

* the current order has SOC_FAMILY settings, which are generic
  settings for a group of devices, overriding the machine specific
  settings.  For example:

  KERNEL_DEVICETREE_ti33x = "xxxx"
  KERNEL_DEVICETREE_beaglebone = "yyyy"

  Should yield "yyyy" when building for the beaglebone because
  that is a more specific device than ti33x.  However, without this
  change the result is that the value is set to "xxxx" meaning the
  more generic setting overrides the more specific setting.

Signed-off-by: Chase Maupin 
Signed-off-by: Richard Purdie