Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=1.4_M1.rc1 2012-10-24T11:50:44+00:00 2012-10-24T11:50:44+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-10-24T11:30:53+00:00 urn:sha1:fa471acc0030c77152c9b72e8f31f6c49f706f01 (From OE-Core rev: 0195a08f77fe0e01b2d7548ccffeaf89d2d780e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-09-10T12:01:50+00:00 Khem Raj raj.khem@gmail.com 2012-09-06T22:23:40+00:00 urn:sha1:5cf953b02ea6d103b7c09d6f36c198d550d06367 nptl and thereby tls are not optional anymore (From OE-Core rev: 1a4b277e47a8d624cde4c73713d036e230f3a523) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-08-19T09:45:57+00:00 Damien Lespiau damien.lespiau@intel.com 2012-07-30T13:51:14+00:00 urn:sha1:3ea5c742c825574b7e475d6d12060b1b6429ef6b Wihtout it, you have both mesa-dri and mesa-xlib as providers. Let's prefer the accelerated version. (From OE-Core rev: 9f83d93c65942f9ed1b25a24976f92ae06c425c8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-07-04T16:40:37+00:00 Tom Zanussi tom.zanussi@intel.com 2012-07-01T15:56:12+00:00 urn:sha1:fb8aaf6f8e180cb3fe4c2d02c041cb02be88ab46 qemu.inc does a straight assign to MACHINE_FEATURES so overwriting the preceding append to MACHINE_FEATURES, so the MACHINE_FEATURES append needs to be moved after the include. This situation came about as a result of commit 71a4bf386: qemumachines: Enable xserver-xorg as default xserver For qemux86 and qemux86-64 include qemu.inc after defining XSERVER which missed this side-effect (and maybe others). (From OE-Core rev: 4f336e5f416df382fdd2b405314741164d537b22) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-05-24T07:53:56+00:00 Khem Raj raj.khem@gmail.com 2012-05-01T05:01:24+00:00 urn:sha1:71a4bf386181b3fbc2dc723c781a456a0bbdb943 For qemux86 and qemux86-64 include qemu.inc after defining XSERVER XSERVER variable is also weakly defined in task-core-x11.bb which means we can not use ??= otherwise when building any qemu image that uses task-core-x11.bb will get the wrong definition So we define the XSERVER common set for qemu in qemu.inc and as we know x86 and x86-64 qemu overrides the default we include qemu.inc after that definition which means that qemux86 and qemux86-64 get their own definitions and other qemus get the definitions from qemu.inc. other non-qemu machine will get their defintion from task which points to kdrive as of now. (From OE-Core rev: 62dba36166bc5faa32ba3e0664ae98b168cde6b1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-03-30T16:20:24+00:00 Zhai Edwin edwin.zhai@intel.com 2012-03-30T03:43:10+00:00 urn:sha1:5cdb58f683d76e4008eae2f8afa2314824a74966 Still need mesa-xlib for emulation of GLX interface on qemuarm/mips/ppc, where mesa-dri doesn't work for pure qemu emulator. [YOCTO #2066] fixed. (From OE-Core rev: 22775b5f1d9c6d9860a579245bf7a48a982ab62f) Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-12-06T22:47:03+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-12-06T20:57:45+00:00 urn:sha1:edc546797da9f1b1611698c3bae0dc532bcb577a Machines shouldn't be poking around PREFERRED_PROVIDERS which aren't machine specific or at least machine safe. Kernels are machine specific and the xserver is selectable. libx11 and mesa are now really a distro choice and machine configurations shouldn't be poking around them as it just leads to corruption, conflicts and confusion. (From OE-Core rev: 97a57aca12437c24b628071bb189c9f3b94e27ca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-10-11T17:08:31+00:00 Martin Jansa Martin.Jansa@gmail.com 2011-10-07T14:37:10+00:00 urn:sha1:c09f0eb561a53b97a769dd0744076af7d904eafb * xserver-xorg is closer to upstream naming and that's how it's named in OE-classic and meta-oe? It would make meta-oe transition easier and better to do it now then convert meta-oe to xserver-xf86 and then rename it back later. (From OE-Core rev: 0b31c7200a368533df970f0efeb81e2e20c73593) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-07-25T11:06:30+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-07-22T13:15:20+00:00 urn:sha1:039a2d006b7349822509ae612f41e24b12b631a6 There is currently consideradble confusion over how the tune files operate and how these interact with the rest of the build system. This update/overhaul changes things so the tune files are primarily resonsible for setting: TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that represents the architecture we're targetting. TUNE_PKGARCH - The value that represents the tune confuration that this set of tune parameters results in. This allows the significant improvement that the core can now always determine the target architecture value, even when TARGET_ARCH needs to be reset to something different and likewise, there is one package architecture variable the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH and FEED_ARCH variables. (From OE-Core rev: a10de4cf8b424ee95c8e283e75d486be5b3b8eac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-05-11T14:26:16+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-05-10T13:33:58+00:00 urn:sha1:367a1394e2504b129bfe9ef6d0c9aebf2ffde0aa (From OE-Core rev: 617b8f2ae26a6b4ac57795fead39ef20b1f92ecc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>