Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Cape Manager
Date: Mon, 30 Jun 2014 10:15:07 +0200	[thread overview]
Message-ID: <20140630081507.GA5083@ad.chargestorm.se> (raw)
In-Reply-To: <53B0DD86.4030402@windriver.com>

* Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:


> On 06/30/2014 12:24 AM, Life Life wrote:
> > Hello,

> > I'm trying build yocto based linux, My hardware is beaglebone black I
> > successfull build system image. But I can't see capemanager. Beacuse my lcd is
> > not work.

> Hello,

> The cape manager is in meta-ti layer:

> http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/

> Seems that we'd better add it to meta-yoco-bsp ?

Unless something has changed since I last looked at this, I don't think
so. 

If I remember correctly, capemgr basically consists of a number of
patches not in the mainline kernel (and also not in TI's staging
kernel). I haven't checked it, by I doubt that we have them in the
linux-yocto kernel. (Especially as the last time I checked it, you had
to revert to a 3.8 (if I rember correctly, it might have been an even
earlier kernel) kernel to get full capemgr support.

If this has changed, then it'd be interesting to know!

Cheers,
Anders

> Add Saul in the loop.


-- 
Anders Darander
ChargeStorm AB / eStorm AB


  parent reply	other threads:[~2014-06-30  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 16:24 Cape Manager Life Life
2014-06-30  3:46 ` Robert Yang
2014-06-30  7:22   ` Life Life
2014-06-30  8:15   ` Anders Darander [this message]
2014-06-30  8:36     ` Life Life
2014-06-30  8:49       ` Anders Darander
2014-06-30 11:27         ` Life Life
2014-06-30 13:40     ` Diego Sueiro
2014-06-30 17:27       ` Life Life
2014-06-30 18:16         ` Saul Wold
2014-07-01 20:01     ` Denys Dmytriyenko
2014-07-03 10:33       ` Life Life

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=20140630081507.GA5083@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox