Update the yocto hardware reference platform to use the
3.4 kernel by default.
This platform is supported in mainline, so no patch carry
forward or similar is required. Tested via NFS booting the
kernel on real hardware with 3.4.1 and things just work as-is.
(From meta-yocto rev: fbe1be490172993140db31472d14652d8ed45624)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Conditionally assign the PREFERRED_PROVIDER_virtual/kernel in the meta-yocto
machine configs to allow the user or other layers to override it. This is
required to use the linux-yocto-rt kernel, for example.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Now that we have a pristine copy of the variables available at launch time
we can use them when looking to inherit the OS's environment.
(Bitbake rev: 21c21fcc5871e81d8d497b6baed605cdd74c4571)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.
'SPE' floating point is what exists on the e500v2 core.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Paul Gortmaker
Tom Zanussi
Richard Purdie
Bruce Ashfield
Jingdong Lu
Darren Hart
Joshua Lock
Kumar Gala
Saul Wold