Development of Yocto Project Kernel outside of Intel?
Hello,
Can someone please share with me the forecast (or any info) on whether the Yocto Project Kernel methodology will be picked up by additional non Intel cores / companies in 2014 or beyond?
I was just reviewing the available branches in linux-yocto-dev and linux-yocto-3.10, and I see that the overwhelming majority of them are for Intel chipsets / development boards.
It seems to me that the methodology documented in the Yocto Project Kernel manuals is well thought out and useful. However, due to the cores that I have chosen to use to date, it's just been something I browse through and forget about.
I think it would be great if all the Yocto member companies that are deploying processors would jump on board and support their kernel(s) the same way.
Any information regarding this will be greatly appreciated.
Thank you,
Bob
Quoted 15 lines · Bob Cochran
Hello,
Can someone please share with me the forecast (or any info) on whether the Yocto Project Kernel methodology will be picked up by additional non Intel cores / companies in 2014 or beyond?
I was just reviewing the available branches in linux-yocto-dev and linux-yocto-3.10, and I see that the overwhelming majority of them are for Intel chipsets / development boards.
It seems to me that the methodology documented in the Yocto Project Kernel manuals is well thought out and useful. However, due to the cores that I have chosen to use to date, it's just been something I browse through and forget about.
Quoted 5 lines
I think it would be great if all the Yocto member companies that are deploying processors would jump on board and support their kernel(s) the same way.
Any information regarding this will be greatly appreciated.
I can add a few thoughts.
We obviously have the reference BSPs to represent the major architectures, and on the linux-yocto mailing list, we've been looking at BSPs from LSI as well as some other pending boards (I'm waiting on them to be submitted, so I won't mention
them here). The xilinx boards also have some yocto-style support in their repository
with us working to adopt and integrated version of them as we move into Yocto 1.6+.
It's generally a slow process to get kernel versions aligned, but with the LF LTSI
kernel(s), it helps create a neutral version that the Yocto project, OSVs, semis and
others can use as a synchronization point. LTSI is part of the linux-yocto kernel
trees as an integrated baseline, and LTSI has recently picked up more attention ..
which has a byproduct of more BSPs being available in a similar format, version and
configuration.
Obviously we'd also love to see all relevant BSPs completely mainlined, with short
stays in the Yocto tree (or others) as a BSP is developed, stabilized and eventually
upstreamed.
There's obviously a place for cutting edge trees, semi trees for the latest and greatest,
stable trees .. and integrated staging grounds for all of the above. So navigating that
mix, takes time, and we are getting there.
Cheers,
Bruce
Quoted 10 lines
Thank you,
Bob
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 35 lines · Bruce Ashfield
I can add a few thoughts.
We obviously have the reference BSPs to represent the major architectures, and on the linux-yocto mailing list, we've been looking at BSPs from LSI as well as some other pending boards (I'm waiting on them to be submitted, so I won't mention
them here). The xilinx boards also have some yocto-style support in their repository
with us working to adopt and integrated version of them as we move into Yocto 1.6+.It's generally a slow process to get kernel versions aligned, but with the LF LTSI
kernel(s), it helps create a neutral version that the Yocto project, OSVs, semis and
others can use as a synchronization point. LTSI is part of the linux-yocto kernel
trees as an integrated baseline, and LTSI has recently picked up more attention ..
which has a byproduct of more BSPs being available in a similar format, version and
configuration.Obviously we'd also love to see all relevant BSPs completely mainlined, with short
stays in the Yocto tree (or others) as a BSP is developed, stabilized and eventually
upstreamed.There's obviously a place for cutting edge trees, semi trees for the latest and greatest,
stable trees .. and integrated staging grounds for all of the above. So navigating that
mix, takes time, and we are getting there.
Quoted 3 lines
Cheers,
Bruce
Hi Bruce (& other yocto developers),
Thank you for the information. Below is a related follow on question, as I try to sort out who's doing what with kernel patches for the varying embedded system chips / SoCs:
To what extent do kernel patches exist for Intel chip sets that are released to embedded Intel customers but aren't yet posted as patches in the yocto kernels? I assume there are proprietary drivers for IP covered under NDA. Is this the case? Does an Intel customer find themselves picking some kernel patches from the linux-yocto branches and others from login protected Intel sites?
Thank you,
Bob
Quoted 49 lines · Bob Cochran
Quoted 37 lines · Bruce Ashfield
I can add a few thoughts.
We obviously have the reference BSPs to represent the major architectures, and
on the linux-yocto mailing list, we've been looking at BSPs from LSI as well as
some other pending boards (I'm waiting on them to be submitted, so I won't mention
them here). The xilinx boards also have some yocto-style support in their repository
with us working to adopt and integrated version of them as we move into Yocto 1.6+.It's generally a slow process to get kernel versions aligned, but with the LF LTSI
kernel(s), it helps create a neutral version that the Yocto project, OSVs, semis and
others can use as a synchronization point. LTSI is part of the linux-yocto kernel
trees as an integrated baseline, and LTSI has recently picked up more attention ..
which has a byproduct of more BSPs being available in a similar format, version and
configuration.Obviously we'd also love to see all relevant BSPs completely mainlined, with short
stays in the Yocto tree (or others) as a BSP is developed, stabilized and eventually
upstreamed.There's obviously a place for cutting edge trees, semi trees for the latest and greatest,
stable trees .. and integrated staging grounds for all of the above. So navigating that
mix, takes time, and we are getting there.Quoted 3 lines
Cheers,
Bruce
Hi Bruce (& other yocto developers),
Thank you for the information. Below is a related follow on question, as I try to sort out who's doing what with kernel patches for the varying embedded system chips / SoCs:
Quoted 6 lines
To what extent do kernel patches exist for Intel chip sets that are released to embedded Intel customers but aren't yet posted as patches in the yocto kernels? I assume there are proprietary drivers for IP covered under NDA. Is this the case? Does an Intel customer find themselves picking some kernel patches from the linux-yocto branches and others from login protected Intel sites?
Adding Darren, since he can elaborate better than I can.
The target for kernel modifications is inevitably the mainline linux kernel, but in the meantime, yes you will have patches that are both developed to support boards and then sent to LTSI or the Linux Yocto kernel as intermediate "release" mechanisms .
To what extend the mixing and matching happens, that wouldn't be a goal, since that is a home-brew mix of changes that no one really calls a BSP. Maybe Darren has more information, or knows where to direct the query.
Bruce
Quoted 11 lines
Thank you,
Bob
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 64 lines · Bruce Ashfield
Quoted 49 lines · Bob Cochran
Quoted 37 lines · Bruce Ashfield
I can add a few thoughts.
We obviously have the reference BSPs to represent the major architectures, and
on the linux-yocto mailing list, we've been looking at BSPs from LSI as well as
some other pending boards (I'm waiting on them to be submitted, so I won't mention
them here). The xilinx boards also have some yocto-style support in their repository
with us working to adopt and integrated version of them as we move into Yocto 1.6+.It's generally a slow process to get kernel versions aligned, but with the LF LTSI
kernel(s), it helps create a neutral version that the Yocto project, OSVs, semis and
others can use as a synchronization point. LTSI is part of the linux-yocto kernel
trees as an integrated baseline, and LTSI has recently picked up more attention ..
which has a byproduct of more BSPs being available in a similar format, version and
configuration.Obviously we'd also love to see all relevant BSPs completely mainlined, with short
stays in the Yocto tree (or others) as a BSP is developed, stabilized and eventually
upstreamed.There's obviously a place for cutting edge trees, semi trees for the latest and greatest,
stable trees .. and integrated staging grounds for all of the above. So navigating that
mix, takes time, and we are getting there.Quoted 3 lines
Cheers,
Bruce
Hi Bruce (& other yocto developers),
Thank you for the information. Below is a related follow on question, as I try to sort out who's doing what with kernel patches for the varying embedded system chips / SoCs:
Quoted 6 lines
To what extent do kernel patches exist for Intel chip sets that are released to embedded Intel customers but aren't yet posted as patches in the yocto kernels? I assume there are proprietary drivers for IP covered under NDA. Is this the case? Does an Intel customer find themselves picking some kernel patches from the linux-yocto branches and others from login protected Intel sites?
Adding Darren, since he can elaborate better than I can.
The target for kernel modifications is inevitably the mainline linux kernel, but in the meantime, yes you will have patches that are both developed to support boards and then sent to LTSI or the Linux Yocto kernel as intermediate "release" mechanisms .
Quoted 4 lines
To what extend the mixing and matching happens, that wouldn't be a goal, since that is a home-brew mix of changes that no one really calls a BSP. Maybe Darren has more information, or knows where to direct the query.
Hi Bob,
There are a couple of ways I can answer this. Intel is a big place, so anything I say must be qualified with the realm of my experience and influence.
As you say, there do exist IP-encumbered kernel features, these are relatively rare and are becoming more so over time as we continue to emphasize the importance of upstream-first development models. However, even some of these are available through the Yocto Project (such as the EMGD graphics driver). The meta-intel BSP layer is where these sorts of things are done.
The vast majority of Linux support for Intel hardware and features are developed upstream. Some areas are stronger in this area than others:
graphics, networking, power management, and other core areas are strong examples of this done early and done well.
Other more esoteric features tend to lag with respect to the pace of silicon and Linux development processes. When this happens, the linux-yocto repository and the LTSI kernels provide a means by which we can get support for these features out to end-users while we continue to work on getting them pushed upstream.
We continue to strive to work faster and push more and more of these features into the upstream-first category, and I can say with first-hand experience that things are improving here.
Does this answer your question?
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel