Hi Yocto Gurus
Our SDK has the Yocto Project 1.7 Dizzy version and it supports cmake 2.8.12
version as show below:
./meta/recipes-devtools/cmake/cmake_2.8.12.2.bb
./meta/recipes-devtools/cmake/cmake-native_2.8.12.2.bb
We need to pulling the cmake 3.x.x version for our sdk-dslink-c recipe
On Tue, Nov 01, 2016 at 11:14:48AM -0400, Nicolas Bigaouette wrote:
> We are using Yocto (jethro and krogoth) to build an image for a device.
>
> I organized the compilation process into multiple stages for easier
> integration with our tooling. The last stage is a call to `wic` to
> create a
Hello Bruce,
This change enables Intel PMIC TMU config as module on broxton platform.
This change is targeted for yocto-4.4 branch.
Nilesh Bacchewar (1):
Broxton: Enable PMIC TMU module
features/power/intel_pmic.cfg | 3 +++
1 file changed, 3 insertions(+)
--
1.9.1
--
Enable Intel Whiskey Cove PMIC TMU driver as module.
Signed-off-by: Nilesh Bacchewar
---
features/power/intel_pmic.cfg | 3 +++
1 file changed, 3 insertions(+)
diff --git a/features/power/intel_pmic.cfg b/features/power/intel_pmic.cfg
index 4b2472b..ba47aa5 100644
Backport:
- Submitted upstream [https://patchwork.kernel.org/patch/9415995/]
- Backport fix.
This adds TMU (Time Management Unit) support for Intel BXT platform.
It enables the alarm wake-up functionality in the TMU unit of Whiskey Cove
PMIC.
Signed-off-by: Nilesh Bacchewar
Backports this patch on linux-yocto-4.4. Patch has been submitted upstream
and the approval is in progress, hence may not be final. Patch has been
rebased on bxt-rebase branch.
Nilesh Bacchewar (1):
platform: x86: Add Whiskey Cove PMIC TMU support
drivers/mfd/intel_soc_pmic_bxtwc.c | 38
On Mon, Nov 7, 2016 at 11:48 AM, Paul Eggleton
wrote:
> On Mon, 07 Nov 2016 09:24:18 Khem Raj wrote:
>> On 11/7/16 3:48 AM, Keskinarkaus, Teemu wrote:
>> > Hi,
>> >
>> >
>> >
>> > I tried googling this and reading the manual, but I guess this is too
>> > trivial or
On Mon, 07 Nov 2016 09:24:18 Khem Raj wrote:
> On 11/7/16 3:48 AM, Keskinarkaus, Teemu wrote:
> > Hi,
> >
> >
> >
> > I tried googling this and reading the manual, but I guess this is too
> > trivial or I’m doing something wrong.
> >
> >
> >
> > I’m trying to get UTF-8 support to my image.
Hi,
How you store your project configuration ? How you prepare workspace
(download each layer separately)?
Basic stuff, SW release should be reproducible (in easy way). Store
somewhere used hash of each piece or use tags. Non company assets should be
already somehow tagged or you use HEAD or
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: November 07, 2016 12:37
>
> On 11/7/16 9:27 AM, Vuille, Martin (Martin) wrote:
> > I see that “sysvinit” and “systemd” style init is supported.
> >
> >
> >
> > Is there support for BSD-style init, or some other minimal init?
> >
> >
>
> there
On 11/7/16 9:27 AM, Vuille, Martin (Martin) wrote:
> I see that “sysvinit” and “systemd” style init is supported.
>
>
>
> Is there support for BSD-style init, or some other minimal init?
>
>
there is busybox/mdev init option in OE-core if you are looking for
a minimal init and not
I see that "sysvinit" and "systemd" style init is supported.
Is there support for BSD-style init, or some other minimal init?
Does anyone know of such support in a separate layer?
MV
--
___
yocto mailing list
yocto@yoctoproject.org
On 11/7/16 3:48 AM, Keskinarkaus, Teemu wrote:
> Hi,
>
>
>
> I tried googling this and reading the manual, but I guess this is too trivial
> or I’m doing something wrong.
>
>
>
> I’m trying to get UTF-8 support to my image. UTF-8 locale more specific. If I
> run locale –a command I get
On 2016-11-06 09:52 PM, Song liwei wrote:
summary:
This two patches use to fix the compile error when enable CONFIG_CRYPTODEV
Thanks. I've pushed these patches. SRCREV updates will follow, but the
changes are now available for anyone that needs them.
Bruce
Testing Commands:
Hi Scott,
On 3 November 2016 at 20:21, Scott Rifenbark wrote:
> See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-
> manual.html#detailed-supported-distros and let me know if this is okay.
> If so, I will make sure the same commit is on my yocto-docs/morty branch.
>
2016-11-07 9:48 GMT-02:00 Keskinarkaus, Teemu
:
> Hi,
>
>
>
> I tried googling this and reading the manual, but I guess this is too
> trivial or I’m doing something wrong.
>
>
>
> I’m trying to get UTF-8 support to my image. UTF-8 locale more specific. If
> I
Hi,
I tried googling this and reading the manual, but I guess this is too trivial
or I'm doing something wrong.
I'm trying to get UTF-8 support to my image. UTF-8 locale more specific. If I
run locale -a command I get these locales listed:
C
POSIX
en_GB
en_US
I added this line to my
Signed-off-by: Andrea Galbusera
---
documentation/kernel-dev/kernel-dev-advanced.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml
b/documentation/kernel-dev/kernel-dev-advanced.xml
index 9e15f17..ed982fb
On 7 November 2016 at 09:09, Burton, Ross wrote:
> Currently the Yocto Project commits to supporting the previous two
> releases with security fixes. If you want a longer life-cycle than that
> then it is recommended to approach one of the many OSVs who support Yocto
>
On 6 November 2016 at 15:33, Vuille, Martin (Martin)
wrote:
> Has there ever been any discussion of making select releases
>
> “Long Term Support” releases, i.e., committing to support them
>
> for a number of years?
>
>
>
> Presumably that would entail having the resources to
20 matches
Mail list logo