aboutsummaryrefslogtreecommitdiffstats
path: root/meta-fri2
AgeCommit message (Collapse)Author
2011-08-20meta-intel: update SRCREVsTom Zanussi
Update linux-yocto_3.0 kernel SRCREVS for fishriver, fri2, jasperforest, and sugarbay. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2011-08-20meta-intel: change PREFERRED_VERSIONsTom Zanussi
Change PREFERRED_VERSION_linux-yocto to a form that will pick up the new numbering scheme. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2011-08-17meta-intel: update linux-yocto 3.0 kernel SRCREVsTom Zanussi
Update 3.0 kernel SRCREVs for fishriver, fri2, jasperforest, sugarbay. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2011-08-12rt: simplify linux-yocto-rt.bbappend for all BSPsDarren Hart
As the all the BSPs use the same BSP branch and meta commit ID as the base recipe, there is no need specify the KBRANCH and SRCREVs. Not doing so greatly simplifies maintenance. Leaving the syntax in place, but commented out, serves as documentation should the need arise to use a different BSP branch or meta commit ID. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-11allow override of kernel providerDarren Hart
Allow users or layers to override PREFERRED_PROVIDER_virtual/kernel. This is required to use the linux-yocto-rt kernel, for example. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-11add linux-yocto-rt_3.0 support for all meta-intel BSPsDarren Hart
All the BSPs build out of the preempt-rt/base branch (rather than a preempt-rt/$MACHINE branch), so separate KMACHINE and KBRANCH assignments are required for each BSP. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
2011-08-03meta-fri2: add 3g and wifi featuresTom Zanussi
Make sure the 3g and wifi bits get added. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
2011-08-03meta-fri2: new layer for Fish River Island II (E6XX/EG20T) systemsTom Zanussi
This layer provides support for E6XX + EG20T Intel systems. Currently it supports only vesa graphics, which will be upgraded shortly. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>