Dear Yocto mailing list,
We are IC Nexus Co. Ltd. in Taipei City - Taiwan, a developer and
manufacturer of ARM-based Embedded Single Board Computers and Smart LCD
Display products (on Android / Linux / Yocto Project). We are currently
selling our products with Yocto O.S. to our worldwide custom
On Fri, May 13, 2016 at 9:25 AM, Chandrakanth Sherkhane (IC Nexus) <
c...@icnexus.com.tw> wrote:
> Dear Yocto mailing list,
>
>
>
> We are IC Nexus Co. Ltd. in Taipei City – Taiwan, a developer and
> manufacturer of ARM-based Embedded Single Board Computers and Smart LCD
> Display products (on
Hi,
I guess you forgot to add your module to the image recipe:
IMAGE_INSTALL_append = " ledmodule"
If you are working on your module code, you may prefer to copy your module with
ssh to the target system and load it dynamically with commands like this:
$ scp
$BUILDDIR/tmp/work/-poky-linux-gnue
Hi,
FYI, image recipes are in recipes-core/images folders.
So if you created your own image recipe, my previous mail should answer your
need.
Otherwise, I don't know if you could just add this line to your local.conf
file...
IMAGE_INSTALL_append = " ledmodule"
The best way to know that your I
On 13 May 2016 at 08:25, Chandrakanth Sherkhane (IC Nexus) <
c...@icnexus.com.tw> wrote:
> Could anyone help to provide more details for,
>
> 1. Yocto Virtual Keyboard in French language - is it available now?
>
> 2. If not available, when will it be available?
>
> 3. Is the Yocto Virtual Keyboard
Alternatively when you are using meta-qt5 layer, you could use something
like Maliit input framework (which is used by various distributions
(Jolla/Sailfish/Ubuntu/LuneOS) as well).
https://github.com/meta-qt5/meta-qt5/tree/master/recipes-qt/maliit
Herrie
On 2016-05-13 11:26, Burton, Ross wro
Thanks for taking the time to help me
I tried your approach but it does not worked.
I tell what I figured out so far:
I.) checking the target system
1.) When flashing the images into my device and boot the system, the
driver is not loaded.
2.) lsmod shows that there is no driver loaded
3.) modp
I solved that problem
Using
IMAGE_INSTALL += "ledmodule"
instead of
IMAGE_INSTALL_append = " ledmodule"
caused that the module was installed.
I found the hint in
https://communities.intel.com/thread/56810?start=0&tstart=0
Thanks for the help. Maybe a tip in the recipe template "hello_mod"
Great news !
BTW, I am surprised about this result… IMAGE_INSTALL_append works for me…
And the link you provided tells that _append method is preferred to +=…
Joël Esponde
Honeywell | Sensing and Productivity Solutions
De : s.jar...@esa-grimma.de [mailto:s.jar...@esa-grimma.de]
Envoyé : vendredi
Hej
I try to build the libdbus-c++ libary. The build process is based on
autotools. When compiling it do_configure throws an error. The macro
"AC_DEFINE" is not found. Any idea how to make autoreconf run?
Below I listed to recipe and after the Error plot
# libdbus-c++_0.9.bb #
On 13 May 2016 at 15:21, wrote:
> I try to build the libdbus-c++ libary. The build process is based on
> autotools. When compiling it do_configure throws an error. The macro
> "AC_DEFINE" is not found. Any idea how to make autoreconf run?
>
Try also inheriting pkgconfig. I've noticed that if t
Current Dev Position: YP 2.2 M1
Next Deadline: YP 2.2 cut off: June 13, 2016
SWAT team rotation: Juro -> Anibal
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* The bitbake python3 branch is nearing readiness, the OE-Core branch is
not quite at the same
Do I need an account enabled to submit to errors.yoctoproject?
- armin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Signed-off-by: Khem Raj
---
recipes-bsp/common/firmware.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index 8f095b9..bf11e4c 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmwa
Drop the patch which is upstreamed slightly differently
use VMCS_INSTALL_PREFIX to /usr via EXTRA_OECMAKE
Signed-off-by: Khem Raj
---
.../0001-set-VMCS_INSTALL_PREFIX-to-usr.patch | 28 --
recipes-graphics/userland/userland_git.bb | 6 ++---
2 files changed, 3
don’t think so
just do
echo `git config --get user.name` > ${HOME}/.oe-send-error
echo `git config --get user.email` >> ${HOME}/.oe-send-error
and it should be able to send
> On May 13, 2016, at 8:34 AM, akuster808 wrote:
>
> Do I need an account enabled to submit to errors.yoctoproject?
>
>
The firmware after 2016/04/12 () seems to have altered the behavior of device
tree loading on RaspberryPi: for overlays, it loads only .dtbo files, not .dtb
anymore.
Also, it does not check for -overlay extension, so the name of the overlay that
is placed in the "overlays" directory must be .dtb
Signed-off-by: Herve Jourdain
---
classes/linux-raspberrypi-base.bbclass | 4 +--
classes/sdcard_image-rpi.bbclass | 6 ++--
conf/machine/include/rpi-base.inc | 30 +--
.../0002-fix-dtbo-rules.patch | 35 +++
Signed-off-by: Herve Jourdain
---
meta/recipes-kernel/linux/linux-dtb.inc | 66 +
1 file changed, 35 insertions(+), 31 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-dtb.inc
b/meta/recipes-kernel/linux/linux-dtb.inc
index 651a19e..44782d8 100644
--- a/
Recent kernels tend to use .dtbo files for device tree overlays, instead of
.dtb before.
.dtb are still used, but only for the "real" device trees (not the overlays).
On some platforms (meta-raspberrypi for instance), recent firmware only loads
.dtbo files for overlays.
This patch tries to addr
20 matches
Mail list logo
