path: root/meta-fri2/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
Commit message (Collapse)AuthorAgeFilesLines
* meta-intel: remove linux-yocto*_3.0 bbappendsTom Zanussi2012-10-291-11/+0
| | | | | | | The 3.2 and 3.4 kernels are the ones supported for Yocto 1.3, so remove the 3.0 versions. Signed-off-by: Tom Zanussi <>
* fri2: Autoload module iwlwifiDarren Hart2012-03-201-0/+2
| | | | | | | | | iwlwifi uses a firmware blob that must exist on the FS at the time the driver is loaded. If the driver is built-in, the blob must exist in the initrd. We avoid this by building as a module, but we still want this to load at boot - so add it to autoload. Signed-off-by: Darren Hart <>
* fri2: Update KMACHINE and KBRANCH variablesDarren Hart2012-03-201-5/+4
| | | | | | | | Specify only the machine itself in KMACHINE and set the branch explicitly. Use an fri2 specific branch in non-rt while we sort out whether or not to create these dynamically or not. Signed-off-by: Darren Hart <>
* meta-fri2: allow linux-yocto-rt to be used for fri2-noemgdTom Zanussi2011-10-281-0/+2
| | | | | | | The fri2 linux-yocto-rt .bbappend is missing settings needed for use with fri2-noemgd - this adds them. Signed-off-by: Tom Zanussi <>
* rt: simplify linux-yocto-rt.bbappend for all BSPsDarren Hart2011-08-121-3/+4
| | | | | | | | | | 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 <>
* add linux-yocto-rt_3.0 support for all meta-intel BSPsDarren Hart2011-08-111-0/+7
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 <>