Adding -rt support for kernel

Adding -rt support for kernel

[Eric Nelson]

Hi all,

Based on some customer requests, we've applied the "-rt" patches
to our kernel trees and pushed branches like this to our Github
tree:
	https://github.com/boundarydevices/linux-imx6/tree/boundary-imx_3.10.17_1.0.0_ga-rt

This makes it pretty simple for someone who's used git to build
these kernels outside of Yocto, but is painful for integration
into a Yocto-based build.

For the "linux-imx" kernel, the package "linux-imx-rt" recipe
defines a new variant of the kernel, but I don't understand how
this can be used in a build.

In other words, do you specify
	PREFERRED_PROVIDER_virtual/kernel="linux-imx-rt"
or
	PREFERRED_VERSION_virtual/kernel_linux-imx="rt-3.10.17"

Please advise,


Eric

Adding -rt support for kernel

[Jacob Kroon]

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

Forgot to cc mailing list.

/Jacob

---------- Forwarded message ----------
From: Jacob Kroon <jacob.kroon@gmail.com>
Date: Fri, Jun 20, 2014 at 6:01 PM
Subject: Re: [meta-freescale] Adding -rt support for kernel
To: Eric Nelson <eric.nelson@boundarydevices.com>


Hi Eric,

On Fri, Jun 20, 2014 at 5:21 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Hi all,
>
> Based on some customer requests, we've applied the "-rt" patches
> to our kernel trees and pushed branches like this to our Github
> tree:
>
> https://github.com/boundarydevices/linux-imx6/tree/boundary-imx_3.10.17_1.0.0_ga-rt
>
> This makes it pretty simple for someone who's used git to build
> these kernels outside of Yocto, but is painful for integration
> into a Yocto-based build.
>
> For the "linux-imx" kernel, the package "linux-imx-rt" recipe
> defines a new variant of the kernel, but I don't understand how
> this can be used in a build.
>
> In other words, do you specify
>         PREFERRED_PROVIDER_virtual/kernel="linux-imx-rt"
> or
>         PREFERRED_VERSION_virtual/kernel_linux-imx="rt-3.10.17"
>
> Please advise,
>
>
For using the real-time patched kernel, I have

PREFERRED_PROVIDER_virtual/kernel_mx6 = "linux-imx-rt"

in my distro.conf, but plain

PREFERRED_PROVIDER_virtual/kernel = "linux-imx-rt"

should work just aswell. Is this not working for you ?

/Jacob

[-- Attachment #2: Type: text/html, Size: 2494 bytes --]

Re: Adding -rt support for kernel

[Eric Nelson]

Thanks Jacob,

On 06/20/2014 09:03 AM, Jacob Kroon wrote:
> Forgot to cc mailing list.
> 

And I followed your lead ;)

> /Jacob
> 
> ---------- Forwarded message ----------
> From: *Jacob Kroon* <jacob.kroon@gmail.com <mailto:jacob.kroon@gmail.com>>
> Date: Fri, Jun 20, 2014 at 6:01 PM
> Subject: Re: [meta-freescale] Adding -rt support for kernel
> To: Eric Nelson <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>>
> 
> 
> Hi Eric,
> 
> On Fri, Jun 20, 2014 at 5:21 PM, Eric Nelson
> <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>> wrote:
> 
>     Hi all,
> 
>     Based on some customer requests, we've applied the "-rt" patches
>     to our kernel trees and pushed branches like this to our Github
>     tree:
>            
>     https://github.com/boundarydevices/linux-imx6/tree/boundary-imx_3.10.17_1.0.0_ga-rt
> 
>     This makes it pretty simple for someone who's used git to build
>     these kernels outside of Yocto, but is painful for integration
>     into a Yocto-based build.
> 
>     For the "linux-imx" kernel, the package "linux-imx-rt" recipe
>     defines a new variant of the kernel, but I don't understand how
>     this can be used in a build.
> 
>     In other words, do you specify
>             PREFERRED_PROVIDER_virtual/kernel="linux-imx-rt"
>     or
>             PREFERRED_VERSION_virtual/kernel_linux-imx="rt-3.10.17"
> 
>     Please advise,
> 
> 
> For using the real-time patched kernel, I have
> 
> PREFERRED_PROVIDER_virtual/kernel_mx6 = "linux-imx-rt"
> 
> in my distro.conf, but plain
> 
> PREFERRED_PROVIDER_virtual/kernel = "linux-imx-rt"
> 
> should work just aswell. Is this not working for you ?
> 

I haven't tried it. I'm just trying to understand in order to
provide a similar "linux-boundary-rt".

I think this gives me enough to go on.

Regards,


Eric