All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: "Bodke, Kishore K" <kishore.k.bodke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 2/9] [meta-intel] Cedartrail: Update SRCREVS and add EFI Support.
Date: Mon, 23 Apr 2012 12:33:10 -0700	[thread overview]
Message-ID: <4F95AE76.1040001@intel.com> (raw)
In-Reply-To: <D956029D25CF204F948EA0FB515E1EE20AC74BFA@ORSMSX106.amr.corp.intel.com>

On 04/23/2012 11:31 AM, Bodke, Kishore K wrote:
> 
>>>  KERNEL_FEATURES_append_cedartrail += " cfg/smp.scc"
>>> +KERNEL_FEATURES_append_cedartrail += " cfg/drm-cdvpvr.scc"
>>> +KERNEL_FEATURES_append_cedartrail += " bsp/cedartrail/cedartrail-pvr-
>> merge.scc"
>>> +KERNEL_FEATURES_append_cedartrail += " cfg/efi-ext.scc"
>>
>>
>> I suggest moving all of this into the cedartrail.scc file in the
>> linux-yocto meta branch. These are all core bits required for the BSP,
>> they don't need to be easily changed from recipe-space.
>>
>> The exception would be the pvr bits. You can make a single
>> cedartrail.scc that supports both configs (with and without pvr) and
>> only modify the pvr one here in recipe space - the rest belongs in
>> linux-yocto/meta
> 
> Hi Darren,
> 
> All the above are specific to pvr only.  

You can't use EFI to boot the system with the pvr driver?

--
Darren

> (cfg/drm-cdvpvr.scc , bsp/cedartrail/cedartrail-pvr-merge.scc, and cfg/efi-ext.scc)
> These are not needed for without pvr versions of the BSP.
> I think if I move them to Cedartrail.scc, these will get pulled in for no-pvr version of the build and may cause the build to fail.
> 
> Thanks
> Kishore.
> 
> 
>>
>>
>>> +COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
>>> +KMACHINE_cedartrail-nopvr  = "cedartrail"
>>> +KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
>>
>> Same here.
>>
>> --
>> Darren
>>
>> --
>> Darren Hart
>> Intel Open Source Technology Center
>> Yocto Project - Linux Kernel


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2012-04-23 19:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 18:55 [PATCH 0/9] [meta-intel] cedartrail patches to support pvr graphics kishore.k.bodke
2012-04-10 18:55 ` [PATCH 1/9] [meta-intel] Cedartrail: Split machine.conf kishore.k.bodke
2012-04-10 18:55 ` [PATCH 2/9] [meta-intel] Cedartrail: Update SRCREVS and add EFI Support kishore.k.bodke
2012-04-23 17:47   ` Darren Hart
2012-04-23 18:31     ` Bodke, Kishore K
2012-04-23 19:33       ` Darren Hart [this message]
2012-04-24  4:15         ` Bodke, Kishore K
2012-04-10 18:55 ` [PATCH 3/9] [meta-intel] Cedartrail: split xorg.conf files kishore.k.bodke
2012-04-10 18:55 ` [PATCH 4/9] [meta-intel] Cedartrail: Add PVR graphics support kishore.k.bodke
2012-04-10 18:55 ` [PATCH 5/9] [meta-intel] Cedartrail: Add Cedartrail-nopvr statement kishore.k.bodke
2012-04-10 18:55 ` [PATCH 6/9] [meta-intel] Cedartrail: separte machconfig in recipes-bsp kishore.k.bodke
2012-04-10 18:55 ` [PATCH 7/9] [meta-intel] Cedartrail: Add new recipes for audio and video samples kishore.k.bodke
2012-04-10 18:55 ` [PATCH 8/9] [meta-intel] Cedartrail: Add new recipe for test image kishore.k.bodke
2012-04-10 18:55 ` [PATCH 9/9] [meta-intel] Cedartrail: Update the README kishore.k.bodke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F95AE76.1040001@intel.com \
    --to=darren.hart@intel.com \
    --cc=kishore.k.bodke@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.