[linux-yocto] [linux-yocto 4.1] fs/yaffs2: adjust to the change of inode_change_ok()

In commit cb8e1eef351b ("fs: Give dentry to inode_change_ok() instead of inode") the inode_change_ok() has been rename to setattr_prepare(), and one of the argument was also changed from inode to dentry. We adjust the invocation of inode_change_ok() in Yaffs2 according to this change.

Re: [yocto] DISTRO_FEATURES vs IMAGE_FEATURES

On 01/24/2017 06:40 PM, Takashi Matsuzawa wrote: Hello Yocto. Though it may feel to me matter of taste, is there suggestion on when which of these to use when you need to define your customized feature. DISTRO_FEATURES seems to be more relaxed, you can define things in your distro conf.

Re: [yocto] [meta-mingw] Morty branch?

On 1/25/17 11:15 AM, Bystricky, Juro wrote: > The LTO patch is needed, see for example: > https://lists.yoctoproject.org/pipermail/yocto/2016-October/032490.html > > The SDK builds without it just fine, but the error pops up while running > under Windows My suspicion is that binutils is missing

Re: [yocto] [meta-mingw] Morty branch?

The LTO patch is needed, see for example: https://lists.yoctoproject.org/pipermail/yocto/2016-October/032490.html The SDK builds without it just fine, but the error pops up while running under Windows Juro From: Mark Hatle [mark.ha...@windriver.com]

Re: [yocto] [meta-mingw] Morty branch?

On 1/25/17 9:29 AM, Bystricky, Juro wrote: > Hello Mark, > the meta-mingw morty branch was created a few moments ago. > Please have a look. Great. This seems to be the stuff that was working for me. One comment if anyone else comes on this in the future. The LTO commit. It's not completely

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

On Wed, Jan 25, 2017 at 5:37 AM, David Vincent wrote: > I've recently noticed that, on Morty, feature branches of a Yocto kernel > are not > merged anymore. This is due to the fact that the meta-series file does not > process the git merge commands anymore. > Indeed. I

Re: [yocto] [meta-mingw] Morty branch?

Hello Mark, the meta-mingw morty branch was created a few moments ago. Please have a look. Thanks Juro > -Original Message- > From: Mark Hatle [mailto:mark.ha...@windriver.com] > Sent: Wednesday, January 11, 2017 9:57 AM > To: Yocto Project > Cc: Bystricky,

Re: [yocto] Ordering of anonymous Python functions and task signature calculations

On Wed, Jan 25, 2017 at 3:03 AM, André Draszik wrote: > On Tue, 2017-01-24 at 11:55 -0600, Matt Hoosier wrote: > > In order to support a use-case that embeds information about the Git > > revision of Yocto itself that was used to make a build, I would like to > > run > > some

Re: [yocto] [meta-raspberrypi][morty][PATCH V2] Revert "u-boot: drop patch to include lowlevel_init"

On Tue, Jan 24, 2017 at 07:16:38PM +0100, Mirza Krak wrote: > From: Mirza Krak > > Not applicable on U-boot 2016.03 which is used in poky/morty and causes an > build > error when KERNEL_IMAGETYPE = "uImage". > > This reverts commit 031e26954b95d49a66ea4677b9e867d08441f450.

[yocto] How to setup syslog by using an own filterfile and log policy configuration?

Hej I like to configure syslog. It seems that are more than one way to set up syslog. I am asking for the comon way/steps to do that. I have several use cases. To simplify I like to ask how to configure syslog to write an infinity long log file in /var/log/. Following steps: 1.) configure

Re: [yocto] [meta-raspberrypi][PATCH] u-boot: drop backported patches

On Tue, Jan 24, 2017 at 07:32:04PM +0100, Mirza Krak wrote: > From: Mirza Krak > > U-boot has been updated to 2017.01 in poky/oe-core which contains these > patches. > > Signed-off-by: Mirza Krak > --- >

Re: [yocto] [meta-raspberrypi][PATCH 1/5] raspberrypi-cm.conf: Add dummy machine for CM1 (alias for RPi1)

On Fri, Jan 20, 2017 at 7:16 PM, Andrei Gherzan wrote: > Signed-off-by: Andrei Gherzan > --- > conf/machine/raspberrypi-cm.conf | 6 ++ > 1 file changed, 6 insertions(+) > create mode 100644 conf/machine/raspberrypi-cm.conf > > diff --git

Re: [yocto] Problems with building out-of-tree modules in morty

Hi, Thank you Raj. what was missing in linux-xlnx rev (tag xilinx-v2016.1.01) was --- a/arch/arm64/Makefile +++ b/arch/arm64/Makefile @@ -43,6 +43,7 @@ CHECKFLAGS+= -D__aarch64__ ifeq ($(CONFIG_ARM64_ERRATUM_843419), y) KBUILD_CFLAGS_MODULE += -mcmodel=large +KBUILD_CFLAGS_MODULE +=

Re: [yocto] More new messages

On 25 January 2017 at 08:53, Gary Thomas wrote: > WARNING: libsndfile1-1.0.27-r0 do_package: Manifest > /build/p0382_2016-01-13/tmp/sstate-control/manifest-allarch-alsa-lib.populate_sysroot > not found? > FWIW I see these too, for intel-corei7-64. Note how its looking for

[yocto] [yocto-kernel-tools][PATCH 1/1] scc: Move merge command

Create a new command to merge a feature branch inside the current branch when processing meta-series. Signed-off-by: David Vincent --- tools/kgit-meta | 14 ++ tools/scc| 13 - tools/scc-cmds/merge.cmd | 10 ++ 3

[yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

I've recently noticed that, on Morty, feature branches of a Yocto kernel are not merged anymore. This is due to the fact that the meta-series file does not process the git merge commands anymore. This commit creates a new merge command to be executed when processing the kernel metadata. To solve

Re: [yocto] Ordering of anonymous Python functions and task signature calculations

On Tue, 2017-01-24 at 11:55 -0600, Matt Hoosier wrote: > In order to support a use-case that embeds information about the Git > revision of Yocto itself that was used to make a build, I would like to > run > some arbitrary Python code and dump the results (Git SHA1's, tag names, > etc) into a

[yocto] More new messages

Seems updating to the latest master has brought a lot of new messages. I'm seeing lots like these: WARNING: libsndfile1-1.0.27-r0 do_package: Manifest /build/p0382_2016-01-13/tmp/sstate-control/manifest-allarch-alsa-lib.populate_sysroot not found? WARNING: pulseaudio-9.0-r0