On Wed, Aug 12, 2015 at 7:15 PM, Andreas Müller
wrote:
> FYI: I managed to get the vc4 driver loaded (should be in my repo
> branch vc4-2). With this I get some repeating kernel error messages
> (don't have them here). I am sure that I read something about these
> messages when preparing vc4 (yes
bake core-image-minimal -c populate_sdk
>
> and the details of my build are:
>
> Build Configuration:
> BB_VERSION= "1.27.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "openSUSE-project-13.2"
> TARG
CHINE = "firefly-emmc-mainline"
DISTRO= "poky"
DISTRO_VERSION= "1.8+snapshot-20150812"
TUNE_FEATURES = "arm armv7a vfp neon cortexa15"
TARGET_FPU= "vfp-neon"
meta = "master:4
On 08/10/2015 08:49 AM, Trevor Woerner wrote:
> On 08/09/15 06:07, Paul Barker wrote:
>> On Fri, Aug 07, 2015 at 09:19:45AM -0400, Trevor Woerner wrote:
>>> When packaging a zImage kernel for IPK in master-next the following
>>> error shows up:
>>>
>>> | kernel-image-zImage-4.1.2-fslc+g95d9e15
>>
On Wed, Aug 12, 2015 at 4:59 PM, Javier Martinez Canillas
wrote:
> Hello,
>
> On 08/10/2015 10:22 AM, Javier Martinez Canillas wrote:
>> Hello Andreas,
>>
>> On 08/10/2015 01:37 AM, Andreas Müller wrote:
Khem definitely has a very good point. Maybe his way of putting it in
words was
>>>
On Wed, Aug 12, 2015 at 6:48 AM, PIEWALD Georg
wrote:
> PREFERRED_VERSION_subversion = "1.6.15"
>
> in my local.conf, but it turned out that this only affects the builds for
> the target-machine (cortexa8hf-vfp-neon-3.8-oe-linux-gnueabi), but not the
> devtools on the build-machine (x86_64-linux).
Hello,
On 08/10/2015 10:22 AM, Javier Martinez Canillas wrote:
> Hello Andreas,
>
> On 08/10/2015 01:37 AM, Andreas Müller wrote:
>>> Khem definitely has a very good point. Maybe his way of putting it in words
>>> was
>>> not that productive. But the core idea was definitely right: I don't want
On Tue, Aug 11, 2015 at 7:07 PM, Joe MacDonald
wrote:
> [Re: [yocto] [meta-selinux][PATCH v1] libpam: use wildcard for version and
> cleanup] On 15.08.11 (Tue 16:39) Shrikant Bobade wrote:
>
> > Hi Philip,
> >
> >
> > On Tue, Aug 11, 2015 at 10:39 AM, Philip Tricca wrote:
> >
> > Hey Shrikan
Hi all,
I have two recipes for building Subversion (which I only need as a devtool on
the build-machine):
$ ls oe-core/meta/recipes-devtools/subversion/*.bb
subversion_1.6.15.bb
subversion_1.7.8.bb
Naturally Yocto uses 1.7.8, which is the newer. However, unfortunately I must
use 1.6.15 on my b
[[yocto] [meta-selinux] How about remove libcap-ng from meta-selinux?] On
15.08.12 (Wed 17:08) wenzong fan wrote:
> Hi All,
>
> There's a libcap-ng in meta-oe layer, it has been updated to 0.7.7 and the
> one in meta-selinux is 0.7.3.
>
> How about removing the one in meta-selinux and get this
On 12/08/2015 10:45, Joshua Lock wrote:
> On Wed, 2015-08-12 at 10:25 +0100, Joshua Lock wrote:
>> On Wed, 2015-08-12 at 10:17 +0100, Alex J Lennon wrote:
>>> We've been having a discussion on a way forward to manage patches
>>> and
>>> code review and would like to open this up for discussion t
On Wed, 2015-08-12 at 10:25 +0100, Joshua Lock wrote:
> On Wed, 2015-08-12 at 10:17 +0100, Alex J Lennon wrote:
> > We've been having a discussion on a way forward to manage patches
> > and
> > code review and would like to open this up for discussion to agree
> > a
> > way
> > forward.
>
> The
On Wed, 2015-08-12 at 10:17 +0100, Alex J Lennon wrote:
> We've been having a discussion on a way forward to manage patches and
> code review and would like to open this up for discussion to agree a
> way
> forward.
There's http://patchwork.openembedded.org/. I'm not sure who maintains
it, nor if
We've been having a discussion on a way forward to manage patches and
code review and would like to open this up for discussion to agree a way
forward.
Options appear to be github, gerrit, or bitbucket although there may be
others. This is in addition to continuing to send patches to the mailing
Hi All,
There's a libcap-ng in meta-oe layer, it has been updated to 0.7.7 and
the one in meta-selinux is 0.7.3.
How about removing the one in meta-selinux and get this layer depends on
meta-oe? Any suggestions?
Thanks
Wenzong
--
___
yocto mailin
2015-08-12 10:28 skrev Alex J Lennon:
> On 12/08/2015 09:08,
Petter Mabäcker wrote:
>
>> 2015-08-11 21:20 skrev Alex J Lennon:
>>
>>> On 11/08/2015 19:54, Petter Mabäcker wrote:
>>>
2015-08-11
19:04 skrev Alex J Lennon:
> - remove placeholder defconfig
and custom copying l
On 12/08/2015 09:08, Petter Mabäcker wrote:
> 2015-08-11 21:20 skrev Alex J Lennon:
>
>> On 11/08/2015 19:54, Petter Mabäcker wrote:
>>> 2015-08-11 19:04 skrev Alex J Lennon:
- remove placeholder defconfig and custom copying logic - use
KBUILD_DEFCONFIG for default in-tree configurations
2015-08-11 21:20 skrev Alex J Lennon:
> On 11/08/2015 19:54,
Petter Mabäcker wrote:
>
>> 2015-08-11 19:04 skrev Alex J Lennon:
>>
>>> - remove placeholder defconfig and custom copying logic - use
KBUILD_DEFCONFIG for default in-tree configurations instead - do not
replace all Yocto configur
> On Jul 21, 2015, at 6:07 PM, Edward Vidal wrote:
>
> Hi all,
> In the file poky/meta/recipes-graphics/libepoxy/libepoxy_git.bb
> I tried to add --disable-egl, with no success
>
>
> PACKAGECONFIG[x11] = "--enable-glx, --disable-glx, virtual/libx11"
> | checking for EGL... no
> | configure: er
> On Jul 22, 2015, at 12:00 AM, Lukas Weiss wrote:
>
> Hello yocto friends,
>
> I have a problem with yocto you could help me with. The Background:
> Iam working on a yocto-linux for a TI OMAP-L138, which is a ARM9+DSP in one
> package. The Linux on ARM is running fine, and does everything I w
20 matches
Mail list logo
