A few atom-pc configuration files escaped the last purge of atom-pc.
Clean them up.
(From meta-yocto rev: f26d99ffb2c67b310d4c46627932dc3f8aefad96)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Duplicate the genericx86 machine, but select x86_64 tunables and use the
common-pc-64 linux-yocto KMACHINE and config.
This has been boot tested with core-image-sato on a Lenovo x220
(Core-i5) and a Supermicro MBD-X8DTL-iF-O (dual-socket Xeon 5680).
(From meta-yocto rev: 9b7db7ded0e6b7f5c0cd3ab7fbb0bce4112407da)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Ross Burton <ross.burton@intel.com>
Cc: Tom Zanussi <tom.zanussi@intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
genericx86 is a superset of atom-pc, so remove all references to
atom-pc.
Note that genericx86 only has 3.10 linux-yocto support, that leaves us
with no x86 BSP in meta-yocto-bsp for the 3.4 kernel. As a general rule,
new BSPs are targeted at the current kernel version, so this is normal,
but something worth noting.
(From meta-yocto rev: 7a8ce1a8ba5a74e16da054c5a04302f028118ce0)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This BSP aims to support "most" contemporary x86 hardware. It's a direct copy
of atom-pc initially.
(From meta-yocto rev: 1a73ef79e16d0cbcd60fa3ad9854dbc121e3282d)
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>
With the splite of netbase and init-ifupdown, the interfaces file needs to get
moved for the beagleboard
[YOCTO #4334]
(From meta-yocto rev: c7c25b7d964a2068414df90a1b961f6368d3bf59)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now we have settled on best practises and compliance criteria, bring meta-yocto
into compliance by separating out the hardware support components into
meta-yocto-bsp leaving policy configuration in meta-yocto.
Also rename the meta-yocto scripts directory to OE-Core can be a clearly
isolated component in poky.
(From meta-yocto rev: eac90e27a032ea23d9a4f35c7eef8b1940c80e22)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Darren Hart
Ross Burton
Saul Wold
Richard Purdie