[yocto] dropbear is working after including in IMAGE_FEATURES

Hi, I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe image. and created the image. But after flashing the image i was not able to connect to target from my host machine. but target to host is working fine. Can any one tell me why it is not working. Is there any package

[yocto] dropbear is not working after including in IMAGE_FEATURES

Hi, I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe image. and created the image. But after flashing the image i was not able to connect to target using ssh from my host machine. but target to host is working fine. Can any one tell me why it is not working. Is there any

Re: [yocto] dropbear is working after including in IMAGE_FEATURES

> On Sep 10, 2015, at 7:09 AM, Vivek Per wrote: > > Hi, > I have included IMAGE_FEATURES += "ssh-server-dropbear" in my recipe > image. and created the image. > But after flashing the image i was not able to connect to target from my host > machine. but target to

Re: [linux-yocto] [V2] Fix yaffs2 build failure on 4.1 kernel

On 15-09-09 03:45 PM, Yang Shi wrote: Fix yaffs2 build failure on 4.1 kernel and bring in missed patch. I've merged the series, and will send a pull request once my build tests have passed. Cheers, Bruce Yang Shi (2): yaffs2: replace f_dentry to f_path.dentry yaffs2: remove

Re: [yocto] dropbear is not working after including in IMAGE_FEATURES

On 09/10/2015 05:17 PM, Vivek Per wrote:> Hi, > I have included IMAGE_FEATURES += "ssh-server-dropbear" in my > recipe image. and created the image. So you have something like: image-features-image.bb with something like this? --> IMAGE_INSTALL = "packagegroup-core-boot

Re: [yocto] [meta-raspberrypi] du giving non-integer result?

>From the feedback, it looks like I'm the only one seeing this issue. That's okay, but I'll update this issue with new information in case it's useful to others. Today I also had some other strangeness with the "make sd card image" portion of a build, this time for cubietruck (meta-sunxi):

[yocto] [PATCH][meta-selinux] net-tools: Rename net-tools bbappend with wildcard for minor version.

Signed-off-by: Philip Tricca --- recipes-extended/net-tools/net-tools_1.%.bbappend | 11 +++ recipes-extended/net-tools/net-tools_1.60-25.bbappend | 11 --- 2 files changed, 11 insertions(+), 11 deletions(-) create mode 100644

[yocto-announce] Intel Core Processor (Haswell-Walnut Canyon) BSP for Yocto Project version 1.7.2 (Dizzy) now available.

Hi all, We are pleased to announce the updated release of the Intel(r) Haswell-Walnut Canyon BSP for the Yocto Project "dizzy" 1.7.2 release. https://www.yoctoproject.org/downloads/bsps/dizzy172/haswell-walnut-canyon Features Supported in this Release: * Linux kernel version 3.10 * Support

Re: [yocto] dropbear is not working after including in IMAGE_FEATURES

Hi, Now Dropbear feature is including in the image but it is getting failed to start time while booting error [3.164188] systemd[1]: Failed to start SSH Server. Does can one help with this issue. Thanks and Regards vivek On Thu, Sep 10, 2015 at 11:07 PM, Robert Berger <

[yocto] kernel change detection for packages that depend on kernel version?

I'm running into an issue where the branch for my kernel received some new commits, changing what the kernel version string looks like. When I rebuilt my system (bitbake my-image) the kernel was rebuilt (I believe at some point I probably also ran bitbake virtual/kernel -c clean), however

Re: [linux-yocto] ${S} variable resists being set in recipe

I tried that before. Here are the results: WARNING: ${workdir} ('S') doesn't exist, please set 'S' to a proper value ERROR: Function failed: gst-crypto: LIC_FILES_CHKSUM points to an invalid file: ${workdir}/COPYING ERROR: Logfile of failure stored in:

[yocto] Peripheral hardware support

I'd like to include a RFID reader in a Yocto-based project. What is the best way to find devices that have driver support already or that provide open-source drivers suitable for inclusion? Is there a hardware support list for stuff like that somewhere? Thanks, Brad --

[linux-yocto] ${S} variable resists being set in recipe

All, I'm having a problem with a recipe. It runs without error, but doesn't build the code, and it doesn't deploy the artifacts. It also give a warning that S must be set properly. Here is my recipe. DESCRIPTION = "Gstreamer plugin provided by RidgeRun to decrypt videos on the fly, static