* Development of Yocto Project Kernel outside of Intel? @ 2013-12-23 17:58 Bob Cochran 2013-12-24 2:10 ` Bruce Ashfield 0 siblings, 1 reply; 6+ messages in thread From: Bob Cochran @ 2013-12-23 17:58 UTC (permalink / raw) To: Yocto discussion list 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Development of Yocto Project Kernel outside of Intel? 2013-12-23 17:58 Development of Yocto Project Kernel outside of Intel? Bob Cochran @ 2013-12-24 2:10 ` Bruce Ashfield 2014-01-20 15:59 ` Bob Cochran 0 siblings, 1 reply; 6+ messages in thread From: Bruce Ashfield @ 2013-12-24 2:10 UTC (permalink / raw) To: Bob Cochran; +Cc: Yocto discussion list On Mon, Dec 23, 2013 at 1:58 PM, Bob Cochran <yocto@mindchasers.com> wrote: > 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. 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 > > Thank you, > > Bob > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Development of Yocto Project Kernel outside of Intel? 2013-12-24 2:10 ` Bruce Ashfield @ 2014-01-20 15:59 ` Bob Cochran 2014-01-20 17:23 ` Bruce Ashfield 0 siblings, 1 reply; 6+ messages in thread From: Bob Cochran @ 2014-01-20 15:59 UTC (permalink / raw) To: Bruce Ashfield; +Cc: Yocto discussion list On 12/23/2013 09:10 PM, Bruce Ashfield wrote: > 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 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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Development of Yocto Project Kernel outside of Intel? 2014-01-20 15:59 ` Bob Cochran @ 2014-01-20 17:23 ` Bruce Ashfield 2014-01-20 17:43 ` Darren Hart 0 siblings, 1 reply; 6+ messages in thread From: Bruce Ashfield @ 2014-01-20 17:23 UTC (permalink / raw) To: Bob Cochran, Bruce Ashfield; +Cc: Yocto discussion list, Darren Hart On 14-01-20 10:59 AM, Bob Cochran wrote: > On 12/23/2013 09:10 PM, Bruce Ashfield wrote: >> 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 > > > 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? 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 > > Thank you, > > Bob > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Development of Yocto Project Kernel outside of Intel? 2014-01-20 17:23 ` Bruce Ashfield @ 2014-01-20 17:43 ` Darren Hart 0 siblings, 0 replies; 6+ messages in thread From: Darren Hart @ 2014-01-20 17:43 UTC (permalink / raw) To: Bruce Ashfield; +Cc: Yocto discussion list On Mon, 2014-01-20 at 12:23 -0500, Bruce Ashfield wrote: > On 14-01-20 10:59 AM, Bob Cochran wrote: > > On 12/23/2013 09:10 PM, Bruce Ashfield wrote: > >> 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 > > > > > > 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? > > 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. 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? -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Development of Yocto Project Kernel outside of Intel? @ 2013-12-23 18:31 Edward Vidal 0 siblings, 0 replies; 6+ messages in thread From: Edward Vidal @ 2013-12-23 18:31 UTC (permalink / raw) To: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 1256 bytes --] Hello Bob, Bob wrote 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 am currently using the dylan branch with the zedboard. Build Configuration: BB_VERSION = "1.18.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-19" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "zedboard" DISTRO = "poky" DISTRO_VERSION = "1.4.3" TUNE_FEATURES = " armv7a vfp neon zynq" TARGET_FPU = "vfp-neon" meta meta-yocto = "dylan:544c58df358b03dda007700b83ffe2e5f07a7bbb" meta-browser = "dylan:2140f2a114f7009f86479afb12a524bb157cbb0e" meta-gnome meta-oe meta-multimedia = "dylan:44754206632dd5b0725aeb43e99e4ff9e0245dca" meta-xilinx meta-kc705 meta-zc702 meta-zedboard = "dylan:cf9571203be0af5fc654952d3f00e0a7e0fb1174" meta-yocto-bsp = "dylan:544c58df358b03dda007700b83ffe2e5f07a7bbb"meta-yocto-bsp = "(detachedfromorigin/dylan):57e6d537e847b88e4f89cd01be8a2926953b0082" I have used earlier yocto dylan branch with beaglebone, beagleboard ,and pandaboard. develone@sbcglobal.net or vidal.develone@gmail.com [-- Attachment #2: Type: text/html, Size: 1691 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-01-20 17:43 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-12-23 17:58 Development of Yocto Project Kernel outside of Intel? Bob Cochran 2013-12-24 2:10 ` Bruce Ashfield 2014-01-20 15:59 ` Bob Cochran 2014-01-20 17:23 ` Bruce Ashfield 2014-01-20 17:43 ` Darren Hart -- strict thread matches above, loose matches on Subject: below -- 2013-12-23 18:31 Edward Vidal
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.