All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Using meta-intel with Denzil
Date: Thu, 10 May 2012 16:23:51 -0500	[thread overview]
Message-ID: <1336685031.27808.22.camel@elmorro> (raw)
In-Reply-To: <B92CF48D-EC98-44C0-94E1-4260EE7C8CEC@keylevel.com>

On Thu, 2012-05-10 at 22:07 +0100, Chris Tapp wrote:
> On 10 May 2012, at 22:01, Tom Zanussi wrote:
> 
> > On Thu, 2012-05-10 at 21:54 +0100, Chris Tapp wrote:
> >> On 10 May 2012, at 21:44, Tom Zanussi wrote:
> >> 
> >>> On Thu, 2012-05-10 at 21:38 +0100, Chris Tapp wrote:
> >>>> I just tried to build 'crownbay' under Denzil but I got an error saying that xserver-xf86-dri-lite.inc could not be found.
> >>>> 
> >>>> It looks as if new meta is available in the git repository. Is there a plan for 7.0.0 downloads to be available from the downloads page?
> >>>> 
> >>> 
> >>> Yes, the plan these days is to release the meta-intel BSPs a few weeks
> >>> or so following the poky release.  We expect to have denzil BSP
> >>> downloads available from the downloads directory in a couple weeks...
> >> 
> >> 
> >> Thanks Tom.
> >> 
> >> Is there any information produced for a release to explain what needs looking at to bring a BSP in line with the release?
> >> 
> >> I found the above when I tried to bring something I'm working on in to Denzil. It would be really helpful if there was an easy way to find out what I need to consider ;-)
> >> 
> > 
> > I wish there were. ;-)  I don't know any substitute for that kind of
> > thing than looking at git history and trying to build.
> > 
> > BTW, I don't know why you'd be seeing that xserver-xf86-dri-lite.inc
> > error unless you had something out of date - the current master for
> > crownbay works find for me with poky/denzil...
> 
> 
> I've got an embryonic BSP based on meta-intel from an older version (6.0.1). It currently 'lives' within meta-intel/mybsp. When it didn't build I tried crownbay as I always start by assuming I've got something wrong in my code... ;-)
> 

Oh, I guess you must have been trying the edison crownbay with denzil
which has this and won't work with denzil:

meta-crownbay/conf/machine/crownbay.conf:PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
meta-crownbay/conf/machine/crownbay.conf:PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
meta-crownbay/conf/machine/crownbay.conf:XSERVER ?=
"xserver-xf86-dri-lite \
meta-crownbay/conf/machine/crownbay.conf:PREFERRED_VERSION_xserver-xf86-dri-lite ?= "1.9.3"

You really should be looking at the current crownbay BSP in master -
there have been a lot of changes in this (matching changes for the X
overhaul in oe-core IIRC) and other areas since then...

Tom

> Chris Tapp
> 
> opensource@keylevel.com
> www.keylevel.com
> 
> 
> 




  reply	other threads:[~2012-05-10 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 20:38 Using meta-intel with Denzil Chris Tapp
2012-05-10 20:44 ` Tom Zanussi
2012-05-10 20:52   ` Khem Raj
2012-05-10 20:59     ` Tom Zanussi
2012-05-10 21:01       ` Khem Raj
2012-05-10 20:54   ` Chris Tapp
2012-05-10 21:01     ` Tom Zanussi
2012-05-10 21:07       ` Chris Tapp
2012-05-10 21:23         ` Tom Zanussi [this message]
2012-05-10 21:32           ` Chris Tapp

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=1336685031.27808.22.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=opensource@keylevel.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.