Re: [yocto] readonly rootfs - storing data in separate partition

On Mon, Feb 18, 2019 at 6:05 PM Joshua Watt wrote: > On Mon, 2019-02-18 at 17:36 +0100, Belisko Marek wrote: > > Hi, > > I plan to use readonly rootfs option and store some custom data in > separate partition (like hostname, wpa_supplicant.conf etc). I have wic > file which create rootfs + then r

Re: [yocto] readonly rootfs - storing data in separate partition

On Mon, Feb 18, 2019 at 5:52 PM Marc Ferland wrote: > On Mon, Feb 18, 2019 at 11:37 AM Belisko Marek > wrote: > >> Hi, >> >> I plan to use readonly rootfs option and store some custom data in >> separate partition (like hostname, wpa_supplicant.conf etc). I have wic >> file which create rootfs +

Re: [yocto] QEMU Raspberry Pi 2 machine

On Mon, Feb 18, 2019 at 10:34 AM Jean-Christian de Rivaz wrote: > > Hi, > > The chromium-x11 browser can't be compiled for the qemuarm machine because it > use the old ARM926 processor. I have modified the qemuarm.conf file inside > poky/meta/conf/machine/ to add > DEFAULTTUNE ?= "cortexa7thf-n

[yocto] Triggering a rebuild when file deployed from other recipe changes

Hello, I have a recipe that packages images from ${DEPLOY_DIR_IMAGE} into a final binary that can be installed by the user. It looks something like this: do_compile[depends] += "virtual/rootfs-image:do_image_complete" do_compile[depends] += "virtual/boot-image:do_deploy" do_compile[depends] +

Re: [yocto] Yocto General purpose evaluation

Sounds like you should be using an embedded Linux, since only including the minimum required software will help keep your image small and power usage down. Removing audio, video and usb, including from your kernel config, should drastically reduce your size. You should consider the value of a read

Re: [yocto] QEMU Raspberry Pi 2 machine

You can just use a qemux86-64 target, which is much faster because it executes directly on the hardware. What's the need to emulate specifically arm? Alex On Mon, 18 Feb 2019 at 19:34, Jean-Christian de Rivaz wrote: > > Hi, > > The chromium-x11 browser can't be compiled for the qemuarm machine b

[yocto] [meta-raspberry] Bluetooth issue

Hi all, I’m making an image for a rpi3 from this meta : https://github.com/jumpnow/meta-rpi here the instruction for build : https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html I have a problem with the integrated Bluetooth soc on rpi3. It seems that is not recognized/mounted at boo

[yocto] QEMU Raspberry Pi 2 machine

Hi, The chromium-x11 browser can't be compiled for the qemuarm machine because it use the old ARM926 processor. I have modified the qemuarm.conf file  inside poky/meta/conf/machine/ to add DEFAULTTUNE ?= "cortexa7thf-neon-vfpv4" require conf/machine/include/tune-cortexa7.inc But I want to avoid

[yocto] Yocto General purpose evaluation

Hello, I'm looking to evaluate the general purpose/utility of a custom build Yocto embedded OS. I'm trying to get my head around the benefits of using such an OS. I'm sure it's on case by case basis so let me provide my background and requirements. Background/requirements Currently using D

Re: [yocto] readonly rootfs - storing data in separate partition

On Mon, 2019-02-18 at 17:36 +0100, Belisko Marek wrote: > Hi, > I plan to use readonly rootfs option and store some custom data in > separate partition (like hostname, wpa_supplicant.conf etc). I have > wic file which create rootfs + then rest is for data storage. I can > adjust various recipes to

Re: [yocto] readonly rootfs - storing data in separate partition

On Mon, Feb 18, 2019 at 11:37 AM Belisko Marek wrote: > Hi, > > I plan to use readonly rootfs option and store some custom data in > separate partition (like hostname, wpa_supplicant.conf etc). I have wic > file which create rootfs + then rest is for data storage. I can adjust > various recipes t

[yocto] readonly rootfs - storing data in separate partition

Hi, I plan to use readonly rootfs option and store some custom data in separate partition (like hostname, wpa_supplicant.conf etc). I have wic file which create rootfs + then rest is for data storage. I can adjust various recipes to symlink to /data partition. My question is if there exists some m

Re: [yocto] Add new compiler macro

On Mon, Feb 18, 2019 at 7:43 AM wrote: > > Hi, i wanted to add a compiler macro (NEW_MACRO) in order to compile all the > code hidden beetween > #ifdef NEW_MACRO > > #endif > in all my recipes. I think that the right place to do that is in bitbake.conf > file present under poky/meta/conf but whe

[yocto] Add new compiler macro

Hi, i wanted to add a compiler macro (NEW_MACRO) in order to compile all the code hidden beetween #ifdef NEW_MACRO #endif in all my recipes. I think that the right place to do that is in bitbake.conf file present under poky/meta/conf but when i try to do: TARGET_CPPFLAGS += "-MMC_WRITE" I get

Re: [yocto] yocto touchscreen

Hello Zoran I will try these 2 ways. Of course, the second way is the easiest, but I will try also the first way only to see if it is possible. I will keep you in touch if the first way can work. Best regards, Nikola De : Zoran Stojsavljevic Envoyé : lundi 18 février 2019 15:21 À

Re: [yocto] yocto touchscreen

Hello Nikola, Two things, which immediately came to my mind: [1 - Harder way] Either to change xorg-x11-server in sumo to match at least xorg-x11-server *1.20.3;* (harder way, since few people know exact dependencies among various GFX packages, and what and how many packages need to b

Re: [yocto] yocto touchscreen

Thank you Zoran for trying to help me. I tried to resolve the problem, but I didn’t succeed yet, I think I will to continue, and If after some time I find nothing, I’m going to migrate to the thud version. I will maybe try to use Bugzilla Nikola De : Zoran Stojsavljevic Envoyé : mardi