Reference platform kernel on github
Hi all, For the upcoming 16.03 release of the reference platform, we've been working on a unified kernel that works on Hikey, Dragonboard 410c and also enables enterprise HW that we have access to (D02, Overdrive, APM XGene). That kernel is now pushed to github[1] to the 96b/releases/2016.03 branch. It is based on the upstream kernel v4.4 and combines the work from the Hisilicon and Qualcomm landing teams with the enterprise bits coming from the Linaro Enterprise Group. A big thanks for their assistance in sorting out various integration issues. Please note that this kernel tree will now be used only to host a unified kernel. The Hisilicon landing team has graciously agreed to modify their workflow and move their kernel tree to the 96boards-hikey namespace[2] on github. I'll be talking about the experience of putting together this tree at Connect BKK16 (including some patch statistics) and soliciting feedback on the roadmap for this kernel tree - please get in touch if you have ideas. Look forward to more information about the release itself from Ricardo later. Regards, Amit [1] https://github.com/96boards/linux.git [2] https://github.com/96boards-hikey ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Reference platform kernel on github
Hi Amit, are you planning to support DRM/KMS on 4.4 Kernel/Hikey? At LHG we are currently using a 4.5 Kernel snapshot with Wayland/Weston due to incomplete support of DRM/KMS extensions on 4.4. The main issue we saw on the 4.4 was the missing VBlank support in the DRM driver. Br, Zoltan On 2 March 2016 at 10:53, Amit Kucheria wrote: > Hi all, > > For the upcoming 16.03 release of the reference platform, we've been > working on a unified kernel that works on Hikey, Dragonboard 410c and > also enables enterprise HW that we have access to (D02, Overdrive, APM > XGene). > > That kernel is now pushed to github[1] to the 96b/releases/2016.03 > branch. It is based on the upstream kernel v4.4 and combines the work > from the Hisilicon and Qualcomm landing teams with the enterprise bits > coming from the Linaro Enterprise Group. A big thanks for their > assistance in sorting out various integration issues. > > Please note that this kernel tree will now be used only to host a > unified kernel. The Hisilicon landing team has graciously agreed to > modify their workflow and move their kernel tree to the 96boards-hikey > namespace[2] on github. > > I'll be talking about the experience of putting together this tree at > Connect BKK16 (including some patch statistics) and soliciting > feedback on the roadmap for this kernel tree - please get in touch if > you have ideas. > > Look forward to more information about the release itself from Ricardo > later. > > Regards, > Amit > > [1] https://github.com/96boards/linux.git > [2] https://github.com/96boards-hikey > ___ > Dev mailing list > d...@lists.96boards.org > https://lists.96boards.org/mailman/listinfo/dev > -- Zoltan Kuscsik Senior Software Developer, Linaro Digital Home Group email: zoltan.kusc...@linaro.org IRC: zoli_ on irc.linaro.org ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Reference platform kernel on github
Hi Zoltan, We've already enabled DRM on the 4.4 kernel with the framebuffer Xorg driver. What do you need on top of that to enable you do run Wayland/Weston? A link to a patchset would allow me to evaluate whether we can incorporate these into the next release. Regards, Amit On Wed, Mar 2, 2016 at 3:54 PM, Zoltan Kuscsik wrote: > Hi Amit, > > are you planning to support DRM/KMS on 4.4 Kernel/Hikey? At LHG we are > currently using a 4.5 Kernel snapshot with Wayland/Weston due to incomplete > support of DRM/KMS extensions on 4.4. > The main issue we saw on the 4.4 was the missing VBlank support in the DRM > driver. > > Br, > > Zoltan > > On 2 March 2016 at 10:53, Amit Kucheria wrote: >> >> Hi all, >> >> For the upcoming 16.03 release of the reference platform, we've been >> working on a unified kernel that works on Hikey, Dragonboard 410c and >> also enables enterprise HW that we have access to (D02, Overdrive, APM >> XGene). >> >> That kernel is now pushed to github[1] to the 96b/releases/2016.03 >> branch. It is based on the upstream kernel v4.4 and combines the work >> from the Hisilicon and Qualcomm landing teams with the enterprise bits >> coming from the Linaro Enterprise Group. A big thanks for their >> assistance in sorting out various integration issues. >> >> Please note that this kernel tree will now be used only to host a >> unified kernel. The Hisilicon landing team has graciously agreed to >> modify their workflow and move their kernel tree to the 96boards-hikey >> namespace[2] on github. >> >> I'll be talking about the experience of putting together this tree at >> Connect BKK16 (including some patch statistics) and soliciting >> feedback on the roadmap for this kernel tree - please get in touch if >> you have ideas. >> >> Look forward to more information about the release itself from Ricardo >> later. >> >> Regards, >> Amit >> >> [1] https://github.com/96boards/linux.git >> [2] https://github.com/96boards-hikey >> ___ >> Dev mailing list >> d...@lists.96boards.org >> https://lists.96boards.org/mailman/listinfo/dev > > > > > -- > Zoltan Kuscsik > > Senior Software Developer, Linaro Digital Home Group > email: zoltan.kusc...@linaro.org > IRC: zoli_ on irc.linaro.org ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [Dev] Reference platform kernel on github
On Wed, Mar 2, 2016 at 9:11 AM, Amit Kucheria wrote: > Hi Zoltan, > > We've already enabled DRM on the 4.4 kernel with the framebuffer Xorg > driver. What do you need on top of that to enable you do run > Wayland/Weston? A link to a patchset would allow me to evaluate > whether we can incorporate these into the next release. Right, I know the version that will probably be merged quite soon had a few extra changes, so wonder if everything you need is included there (https://lists.freedesktop.org/archives/dri-devel/2016-February/101784.html). But please give us a link to the patch series used, and we can review the changes required. We are also going to discuss how we will maintain this kernel over time, including when to move to newer versions, so please also make sure to join the 96boards sessions in BKK16. Thanks, -- Ricardo Salveti ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
