Re: [yocto] #yocto howto use deltask

arget_${PN}() { } pkg_postinst_ontarget_${PN}() { } pkg_postinst_ontarget_${PN}() {} Thank you and best regards hu -Ursprüngliche Nachricht- Von: Quentin Schulz Gesendet: Monday, 6 July 2020 13:51 An: Hans-Ulrich Schlieben Cc: yocto@lists.yoctoproject.org Betreff: Re: [yocto] #yocto

Re: [yocto] #yocto howto use deltask

t seems there is no way to patch a recipe. My workaround would be to make a copy of the apparmor recipe without the postinst part. Is there a better or another way to do this? Best regards hu Von: Alexander Kanavin Gesendet: Monday, 6 July 2020 13:17 An: Hans-Ulrich Schlieben Cc: yocto@lists.yo

[yocto] #yocto howto use deltask

Hi, my image build fails with: ERROR: ims-image-fieldgate-1.0-r0 do_rootfs: The following packages could not be configured offline and rootfs is read-only: ['apparmor'] The image build succeeds if i remove the task pkg_postinst_ontarget_${PN} from apparmor_2.13.3.bb. I tried to use deltask in

Re: [yocto] Enable systemd service with unit template instance on startup

Why is SYSTEMD_SERVICE_${PN} = " \ can@can0.service \ " and not SYSTEMD_SERVICE_${PN} = " \ can@.service \ " ? Von: yocto@lists.yoctoproject.org Im Auftrag von Robert Varga via lists.yoctoproject.org Gesendet: Wednesday, 17 June 2020 10:35

[yocto] #yocto apparmor recipe prevents read only file system

Hi, building my image with EXTRA_IMAGE_FEATURES += "read-only-rootfs" was prevented by the apparmor_2.13.3 recipe with pkg_postinst_ontarget_${PN} () { if [ ! -d /etc/apparmor.d/cache ] ; then mkdir /etc/apparmor.d/cache fi } removing the these lines for testing the image built just fine. Why i

Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rauc bundle

d I remove / override these automount files in a recipe? Thank you and best regards hu > -Original Message- > From: Stefan Riedmüller > Sent: Wednesday, 26 February 2020 14:24 > To: Hans-Ulrich Schlieben > Cc: Enrico Jörns ; yocto@lists.yoctoproject.org; > bare..

Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rauc bundle

he imx6 folders and run bitbake -f -c compile barebox and built the image. Did this disable the automount? Best regards hu > -Original Message- > From: Stefan Riedmüller > Sent: Tuesday, 25 February 2020 16:16 > To: Hans-Ulrich Schlieben > Cc: Enrico Jörns ; yocto@l

Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rauc bundle

1.boot: mmc0.1 * bootchooser.targets: system0 system1 Best regards hu -Original Message- From: Enrico Jörns Sent: Wednesday, 19 February 2020 17:28 To: Hans-Ulrich Schlieben Cc: yocto@lists.yoctoproject.org; bare...@lists.infradead.org; r...@pengutronix.de Subject: Re: [RAUC] Private

Re: Private: Re: [yocto] #yocto update the kernel with a rauc bundle

... for system0 and /mnt/mmc0.1/boot... for system1 Best regards hu -Original Message- From: Enrico Jörns Sent: Tuesday, 18 February 2020 01:12 To: Hans-Ulrich Schlieben Subject: Re: Private: Re: [yocto] #yocto update the kernel with a rauc bundle Hi hu, please keep at least any list in CC

[yocto] #yocto update the kernel with a rauc bundle

Hi, i have a working configuration with images and rauc bundles. My problem is that kernel and devicetree are located outside the rootfs and so a bundle update never includes these. My image.wks looks this: part BAREBOX --source rawcopy --sourceparams="file=barebox.bin,skip=1024" --ondisk mmc -

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

Hi, both dd copies of barebox (with and without offset) reproduced a system which no longer shows anything on the console. Probably I setup something wrong when building barebox. Regards hu > Hi Ahmad, > >> >> Hello, >> >> On 1/23/20 4:30 PM, Hans-Ulrich

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

Hi Ahmad, > > Hello, > > On 1/23/20 4:30 PM, Hans-Ulrich Schlieben wrote: > > Hi Robert, > > > > there where no SDK, bison and flex missing. Now it compiled. Thanx. > > There are > > > > Copying it onto the system and running it from t

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

: Tuesday, 21 January 2020 21:21 To: Hans-Ulrich Schlieben ; Enrico Joerns ; yocto@lists.yoctoproject.org Cc: bare...@lists.infradead.org Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state' Hi, On 1/21/20 6:51 PM, Hans-Ulrich Schlieben wrote: > Hi Ahmad, > > than

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

Best Regards hu -Original Message- From: Robert ber...@yocto.user Sent: Wednesday, 22 January 2020 18:59 To: Hans-Ulrich Schlieben ; Ahmad Fatoum ; Enrico Joerns Cc: yocto@lists.yoctoproject.org; bare...@lists.infradead.org Subject: Re: [yocto] #yocto bootchooser: Cannot get state

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

Hi Ahmad, > git clone > https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.pengutronix.de%2Fgit%2Fbarebox&data=01%7C01%7Chu.schlieben%40codewrights.de%7C5fdd291346554b1d5e3d08d79dbdda2b%7C0974af9b352b437cb606e9f242c0c227%7C0&sdata=L8WAZYdcm0kjTNZG8OFnedXXyG3DHyIHx1r4gh%2B%2F

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

> From: Ahmad Fatoum > Sent: Monday, 20 January 2020 16:23 > To: Hans-Ulrich Schlieben ; Enrico Joerns > ; yocto@lists.yoctoproject.org > Cc: bare...@lists.infradead.org > Subject: Re: [yocto] #yocto bootchooser: Cannot get state 'state' > > Hello, > >

[yocto] #yocto eth0 stays down if enp1s0 is renamed in zeus

Hi, moving from thud to zeus eth0 no longer goes up on boot. The device has two ethernet ports eth0 and enp1s0. The image renames enp1s0 to eth1 which works fine in thud using: # cat /etc/systemd/network/50-eth1.link [Match] Driver=igb Path=platform-1ffc000.pcie-pci-:01:00.0 [Link] Name=eth

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

------ -Original Message- From: Enrico Joerns Sent: Wednesday, 15 January 2020 15:48 To: Hans-Ulrich Schlieben Cc: bare...@lists.infradead.org; yocto@lists.yoctoproject.org; Ahmad Fatoum Subject: Re: [yocto] #yocto bootchoose

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

1.0 suffers from the same problem? I do not know yet how to include an upstream package like barebox 2020.01.0. Do I have to rename the old recipe or download the recipe somewhere? Thank you and Best Regards hu -----Original Message- From: Ahmad Fatoum Sent: Wednesday, 15 J

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

}; }; Is there a problem because ubi works now and garbles the data in the flash? > What does running the state command say? barebox@Phytec phyCORE-i.MX6 Quad with NAND:/ state registered state instances: is empty in zeus, whereas thud returned: (backend: raw, path: /dev/eeprom0.update-eepro

Re: [yocto] #yocto bootchooser: Cannot get state 'state'

devicetree and so on when moving to warrior/zeus? In thud this worked. Thank you Regards hu > -Original Message- > From: Enrico Joerns > Sent: Wednesday, 15 January 2020 14:03 > To: Hans-Ulrich Schlieben ; > yocto@lists.yoctoproject.org > Cc: bare...@lists.infradead.or