[yocto] [PATCH 0/1][linux-yocto] Remove Cedartrail Machine

[Chris Tapp]

On 12 Feb 2013, at 19:56, Tom Zanussi wrote:

> On Mon, 2013-02-11 at 22:02 -0800, Sean Liming wrote:
>> 
>>> -----Original Message-----
>>> From: yocto-bounces at yoctoproject.org [mailto:yocto-
>>> bounces at yoctoproject.org] On Behalf Of Liu, Song
>>> Sent: Monday, February 11, 2013 1:25 PM
>>> To: Chris Tapp
>>> Cc: Darren Hart; Yocto Discussion Mailing List
>>> Subject: Re: [yocto] [PATCH 0/1][linux-yocto] Remove Cedartrail Machine
>>> 
>>> Thanks for the reply, Chris! Feel free to let us know if you have any
>>> questions. Hope your project will go well.
>>> 
>>> Song
>>> 
>>> -----Original Message-----
>>> From: Chris Tapp [mailto:opensource at keylevel.com]
>>> Sent: Monday, February 11, 2013 1:17 PM
>>> To: Liu, Song
>>> Cc: Bodke, Kishore K; Bruce Ashfield; Darren Hart; Saxena, Rahul; Zanussi,
>>> Tom; Yocto Discussion Mailing List
>>> Subject: Re: [yocto] [PATCH 0/1][linux-yocto] Remove Cedartrail Machine
>>> 
>>> Hi Song / Kishore,
>>> 
>>> On 11 Feb 2013, at 18:47, Liu, Song wrote:
>>> 
>>>> Hi Chris,
>>>> 
>>>> Intel is still supporting critical fixes for the Cedar Trail BSP on
>> Yocto Project
>>> 1.3 release. If you need additional support for your project, I can
>> connect you
>>> with some Intel sales/support people who can help. At the same time, would
>>> you be able to share more information about your project with me? It will
>>> help when I ask them for additional support.
>>> 
>>> Thanks, that's good news.
>>> 
>>> The only slight down side from my perspective is we won't get the benefits
>>> from 1.4 (and future) improvements. However, it will give me an excuse to
>>> move the hardware on as new platforms become available ;-)
>>> 
>>> 
>>>> Song
>>>> 
>>>> -----Original Message-----
>>>> From: Chris Tapp [mailto:opensource at keylevel.com]
>>>> Sent: Saturday, February 09, 2013 1:33 AM
>>>> To: Bodke, Kishore K
>>>> Cc: bruce.ashfield at windriver.com; dvhart at linux.intel.com; Saxena,
>>>> Rahul; Liu, Song; Zanussi, Tom; linux-yocto at yoctoproject.org;
>>>> yocto at yoctoproject.org
>>>> Subject: Re: [yocto] [PATCH 0/1][linux-yocto] Remove Cedartrail
>>>> Machine
>>>> 
>>>> 
>>>> On 8 Feb 2013, at 23:18, kishore.k.bodke at intel.com wrote:
>>>> 
>>>>> From: Kishore Bodke <kishore.k.bodke at intel.com>
>>>>> 
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> This patch set is to remove the Cedartail Machine from
>>>>> Linux-yocto-3.4 Kernel.
>>>>> Cedartrail BSP will not be supported for Yocto 1.4 Release.
>>>> 
>>>> Hi Kishore,
>>>> 
>>>> Are there any plans to bring support back in? We recently committed a
>>> project to using this BSP for the Intel DN2800MT...
>>>> 
>>>>> Also Please remove the standard/cedartrail branch.
>>>>> 
>>>>> Please pull into linux-yocto-3.4/meta branch.
>>>>> 
>>>>> Thanks
>>>>> Kishore.
>>>>> 
>>>>> The following changes since commit
>>> f697e099bc76d5df3a307a5bc0cc25021dd6dfe0:
>>>>> 
>>>>> meta: bump to v3.4.28, rt-40 (2013-02-04 00:14:21 -0500)
>>>>> 
>>>>> are available in the git repository at:
>>>>> 
>>>>> git://git.pokylinux.org/linux-yocto-contrib kishore/cedartrail_remove
>>>>> http://git.pokylinux.org/cgit.cgi/linux-yocto-contrib/log/?h=kishore/
>>>>> c
>>>>> edartrail_remove
>>>>> 
>>>>> Kishore Bodke (1):
>>>>> meta: Remove Cedartrail Machine
>>>>> 
>>>>> .../bsp/cedartrail/cedartrail-preempt-rt.scc       |   13 ------
>>>>> .../bsp/cedartrail/cedartrail-standard.scc         |    8 ----
>>>>> .../cfg/kernel-cache/bsp/cedartrail/cedartrail.cfg |   46
>> --------------------
>>>>> .../cfg/kernel-cache/bsp/cedartrail/cedartrail.scc |   15 -------
>>>>> 4 files changed, 82 deletions(-)
>>>>> delete mode 100755
>>>>> meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-preempt-rt.scc
>>>>> delete mode 100755
>>>>> meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-standard.scc
>>>>> delete mode 100755
>>>>> meta/cfg/kernel-cache/bsp/cedartrail/cedartrail.cfg
>>>>> delete mode 100644
>>>>> meta/cfg/kernel-cache/bsp/cedartrail/cedartrail.scc
>>>>> 
>>>>> --
>>>>> 1.7.9.5
>>>>> 
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto at yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>> 
>>>> Chris Tapp
>>>> 
>>>> opensource at keylevel.com
>>>> www.keylevel.com
>>>> 
>>>> 
>>>> 
>>> 
>>> Chris Tapp
>>> 
>>> opensource at keylevel.com
>>> www.keylevel.com
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> yocto mailing list
>>> yocto at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>> 
>> 
>> I haven't looked at the changes. Out of curiosity, is it possible to add a
>> BSP back in for a new Yocto Project version? What would be the challenge?
>> 
> 
> It probably wouldn't take much to bring it back - basically the pvr
> graphics driver, which I assume is one of the most important features of
> this BSP for users, is stuck at kernel version 3.0.  If everything else
> stayed the same, forward-porting the GPL'ed kernel portion of the driver
> would be all that would be needed to get it working again.  We've done
> that routinely for other drivers such as EMGD, so I don't think that
> would be too big a deal.

Would that mean only non-accelerated graphics? I remember someone on this list a while back saying they had seen it ported to (I think) 3.2 under a main-stream distro.

> The bigger problem is who would support it going forward.  I could do
> the initial work to fix it up (if I had the hardware, which I don't - I
> may get a cedartrail netbook in March, so that ) (or we could take
> patches) but I wouldn't have the time to support it after that.
> 
> If someone stepped up to support it, though, that would make a
> difference in keeping it around in 1.4 and beyond, I think.

What would that involve? Is it fairly stand-alone, or would in-depth knowledge of the kernel 'magic' be required?

> Tom
> 
>> Regards,
>> 
>> Sean Liming
>> 
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 

Chris Tapp

opensource at keylevel.com
www.keylevel.com