On 17 October 2012 22:58, Bodke, Kishore K wrote:
> Wanted to check if you had a chance to look into the cpu uitilization?
> We had less than 15% cpu uitilization, with the acceleration while playing
> the video.
With sintel_trailer-720p.mp4 (and ffmpeg codecs so the audio is also
being decoded)
On Wednesday 17 October 2012 21:07:20 Rifenbark, Scott M wrote:
> Thanks for the added investigation here. The original bug report listed
> COMMON_FEATURES as an undocumented variable. I see, however, that the
> variable referred to by both you and Paul Eggleton is COMBINED_FEATURES. I
> just di
On 18 October 2012 10:20, Paul Eggleton wrote:
>> I don't know the relationship between "features" and "packages"... maybe it
>> is a one-to-one relationship.
>
> It's definitely not 1-1, and sometimes a feature doesn't just control the
> installation of a package or packages, but influences how
On 18 October 2012 10:33, Burton, Ross wrote:
> A concrete example might help. For example there is a "bluetooth"
> machine feature that means bluez (the bluetooth daemon) is built and
> added to the image, ConnMan enabled bluetooth support, and so on.
I say machine feature, I mean distro featur
Hi,
I'm having trouble generating the module auto-loading instructions in
/etc for one of my modules. I have already many modules that all work
fine, but for some reason this one does not get listed in /etc/modules
nor /etc/modules-load.d.
The only thing that distinguishes this module from the ot
On Thu, Oct 18, 2012 at 11:13:13AM -0400, Marc Ferland wrote:
> Hi,
>
> I'm having trouble generating the module auto-loading instructions in
> /etc for one of my modules. I have already many modules that all work
> fine, but for some reason this one does not get listed in /etc/modules
> nor /etc/
Martin Jansa writes:
> On Thu, Oct 18, 2012 at 11:13:13AM -0400, Marc Ferland wrote:
>> Hi,
>>
>> I'm having trouble generating the module auto-loading instructions in
>> /etc for one of my modules. I have already many modules that all work
>> fine, but for some reason this one does not get list
On Thursday 18 October 2012 11:29:58 Marc Ferland wrote:
> Martin Jansa writes:
> > On Thu, Oct 18, 2012 at 11:13:13AM -0400, Marc Ferland wrote:
> >> Hi,
> >>
> >> I'm having trouble generating the module auto-loading instructions in
> >> /etc for one of my modules. I have already many modules t
Okay, I have done a couple of things:
1. I appended to the base-passwd recipe and added my own patch that would patch
the passwd file to have root use a bash shell. I have verified that this is
the case when I login via echo $0. It tells me that root's shell is bash.
2. I have appended to the
From: Kishore Bodke
Hi,
This is a revised patchset to add two new recipes for
zlib and openssl based Memory Management Module implemented
in the Intel Quick Assist Technology.
Please pull them into meta-intel/master.
Thanks
Kishore.
The following changes since commit 8341ed1b28a91b184547e6244
From: Kishore Bodke
This adds the two new modules zlib-qat-mem and openssl-qat-mem
modules to build with the custom Image.
Signed-off-by: Kishore Bodke
---
.../recipes-qat-image/images/core-image-qat-sdk.bb |2 ++
.../recipes-qat-image/images/core-image-qat.bb |2 ++
2 files change
From: Kishore Bodke
This adds a new recipe to build the Intel Quick Assist
Technology Memory Management Module for Zlib.
Signed-off-by: Kishore Bodke
---
.../zlib-qat-module/zlib-qat-module.bb | 52
.../zlib-qat-module/zlib_qat_module.patch | 43 ++
From: Kishore Bodke
This adds a new recipe to include the Intel Quick Assist
Technology libcrypto Memory Management Module.
Signed-off-by: Kishore Bodke
---
.../openssl-qat-module/openssl-qat-module.bb | 54
.../openssl-qat-module/openssl_qat_module.patch| 43
On Wed, 2012-10-17 at 17:27 -0700, rahul.sax...@intel.com wrote:
> From: Rahul Saxena
>
> This patch series does the following:
> -- Update README with product name and state Gfx acceleration support
> -- Fix package naming issue: Yocto bugzilla bug #3286.
> -- Add development headers in pvr
All of the Yocto Project hosted git repositories can be accessed via the
http protocol on port 80. This method uses the smart http backend and it
is as fast as access via the git protocol. Connecting via http will help
users behind a proxy clone and update repositories with minimal
configuration.
On 10/16/2012 09:44 AM, Evade Flow wrote:
>>> Is there a way to clone yocto repositories (say, poky) over https?
I just announced that repositories are available from
git.yoctoproject.org via http. I didn't mention it but clones via https
will work equally well if that is preferable.
> As Paul men
On 10/08/2012 10:18 AM, Evade Flow wrote:
Sending in response to:
- http://lists.yoctoproject.org/pipermail/yocto/2012-September/011802.html
Building with BB_NO_NETWORK can fail if recipes specify 'tag=' in
SRC_URI, since bitbake must contact the source repository to verify
which hash the ta
I have cleaned some of this stuff up. Still need to add DISTRO_EXTRA_RDEPENDS.
See the ref manual at
http://yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.html
Scott
-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
Sent: Thursday, October 18, 20
From: Nitin A Kamble
Only one commit in this pull request to avoid the mes-dri build time warning.
Thanks,
Nitin
The following changes since commit 69c3e43be6f493844a2f432ea0a56c2f6619ca00:
meta-cedartrail: Add development packages to pvr driver recipe (2012-10-18
09:08:07 -0500)
are avail
From: Nitin A Kamble
Extend the mesa-dri recipe from oecore to avoid conflict with
files generated by emgd-driver-bin recipe.
This commits avoids these build warning
WARNING: The recipe is trying to install files into a shared area when those
files already exist. Those files are:
/srv/home
Rahul,
FYI, This commit will also avoid similar warnings for cedar-trail build.
Nitin
> -Original Message-
> From: Kamble, Nitin A
> Sent: Thursday, October 18, 2012 5:00 PM
> To: yocto@yoctoproject.org; Zanussi, Tom; Hart, Darren
> Cc: Kamble, Nitin A
> Subject: [PATCH 1/1] mesa-dri.b
21 matches
Mail list logo
