1. Yocto
  2. Messages

Expanded

Topics Messages
   Date   
Re: Custom QA Checks

Paul Wicks
 

Thanks for the example, very helpful!

-Paul Wicks


On Wed, Aug 17, 2022 at 6:53 AM Ross Burton <Ross.Burton@...> wrote:
On 7 Aug 2022, at 20:21, Paul Wicks via lists.yoctoproject.org <pwicks86=gmail.com@...> wrote:
>
> Is it possible to create additional QA checks such that they apply to all recipes automatically? Or even just to all recipes in a given layer?

Yes, and yes.

For example, I have https://github.com/rossburton/meta-ross/blob/master/classes/insanitier.bbclass

This defines some new sanity checks, and adds them to WARN_QA so that they’re enabled and classified as warnings (use ERROR_QA if you want them to be errors).

Simply inheriting the class in your local or distro configuration with INHERIT += is enough to enable them for all recipes.

Ross
Yocto Project Status 23 August 2022 (WW34)

Stephen Jolley
 

Current Dev Position: YP 4.1 M3 (Feature Freeze)

Next Deadline: 22nd August 2022 YP 4.1 M3 Build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 4.0.3 was released
  • YP 3.1.19 has been built and is in QA
  • We are now at feature freeze for 4.1.
  • The 4.1 build is planned as soon as we resolve the status of some pending patches. The known remaining issues are the rust automated tests, layer setup changes and gcc and rust version upgrades. We also need to fix some autobuilder errors such as the llvm reproducibility issue with mesa.
  • Several patch series have been problematic in the last week which has put strain on our infrastructure, particularly the binutils upgrade.
  • The CVE count for master rose sharply again this week due to multiple issues in vim and tiff. The vim issues have been patched, tiff hasn’t as yet.
  • We have seen a sharp rise in the number of patches in OE-Core, particularly related to changes in new clang versions. Many of these have been submitted upstream and/or have good reasons for being present but we need to continue to work to reduce our patch burden.
  • Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

 

YP 4.1 Milestone Dates:

  • YP 4.1 M3 build date 2022/08/22
  • YP 4.1 M3 Release date 2022/09/02
  • YP 4.1 M4 build date 2022/10/03
  • YP 4.1 M4 Release date 2022/10/28

 

Upcoming dot releases:

  • YP 4.0.3 is released
  • YP 3.1.19 is in QA
  • YP 3.1.19 Release date 2022/09/09
  • YP 4.0.4 build date 2022/09/19
  • YP 4.0.4 Release date 2022/09/30
  • YP 3.1.20 build date 2022/10/10
  • YP 3.1.20 Release date 2022/10/21
  • YP 4.0.5 build date 2022/10/31
  • YP 4.0.5 Release date 2022/11/11

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Re: Bitbake + Patches

Peter Kjellerstedt
 

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Khem Raj
Sent: den 23 augusti 2022 00:29
To: bitflipper <forums@...>
Cc: yocto@...
Subject: Re: [yocto] Bitbake + Patches

On Mon, Aug 22, 2022 at 1:54 PM bitflipper <forums@...> wrote:



I was told this was the right group to ask my question. If this is not
right, please let me know.

I am currently using Zeus, and with Zeus, we get Apache v2.4.41. But I
would like to get a later version of apache because there have been a few
fixes related to cyber security. So I believe that, given we’re using
Zeus, we can’t upgrade to the latest version of Apache given the current
recipe that Zeus uses. Therefore I believe that the only way accomplish
getting tho the latest version of apache with Zeus would to be ‘patch’
the v2.4.41 version that comes with Zeus.

Looking at the Bitbake manual, in section 4.1, it states the following:

"BitBake takes several steps when fetching source code or files. The
fetcher codebase deals with two distinct processes in order: obtaining the
files from somewhere (cached or otherwise) and then unpacking those files
into a specific location and perhaps in a specific way. Getting and
unpacking the files is often optionally followed by patching. Patching,
however, is not covered by this module."


The manual does not cover patching.

Where can I get information on this process of patching something like
apache or any other application that was add via IMAGE_INSTALL_append
method.

Any help pointing me to where this process might be documented is much
appreciated.
look into mega manual something like this would help
https://docs.yoctoproject.org/dev-manual/common-tasks.html?highlight=writing+recipe#patching-code

Thanks, Jim
You don't really need to go patching apache just to update it. What you
need is to add a bbappend file in one of your own layers. Call it
recipes-httpd/apache2/apache2_2.4.41.bbappend and make it contain:

FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"

LIC_FILES_CHKSUM = "file://LICENSE;md5=bddeddfac80b2c9a882241d008bb41c3"

PV = "2.4.54"

SRC_URI += "file://0008-Fix-perl-install-directory-to-usr-bin.patch \
file://0009-support-apxs.in-force-destdir-to-be-empty-string.patch \
file://0001-make_exports.awk-not-expose-the-path.patch"
SRC_URI_remove = "file://apache-configure_perlbin.patch"

SRC_URI[md5sum] = "<I don't have this at hand, but bitbake will tell you what it should be>"
SRC_URI[sha256sum] = "eb397feeefccaf254f8d45de3768d9d68e8e73851c49afd5b7176d1ecf80c340"

You then also need to copy the three new patches and any other
patches that differs between zeus and master and put them in your
layer together with the bbappend file (in a subdirectory called
"recipes-httpd/apache2/apache2").

The suggested contents of the bbappend above is based on the
differences between the apache2 recipe in zeus and master.

//Peter
Boot QCOW2 image on ARM64 with EFI

Gian Lorenzo Meocci <glmeocci@...>
 

Hi,

Is there a tutorial or some example that explains how to generate a wic.qcow2 image that is able to boot using UEFI on qemu/UTM (on Mac M1) ?

thanks
Compiling and installing mariadb-connector-c

S. Srinivasan <shsrvn@...>
 

Hello,

I'm having issues compiling mariadb-connector-c in yocto (BSP-Yocto-i.MX6-PD20.1.0). The following is my recipe:

SUMMARY = "MariadbConnector"
SECTION = "base"
DESCRIPTION = "This recipe is for installing MariadbConnector"
LICENSE = "BSD"
LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c \
file://win/packaging/license.rtf;md5=d84792abbbf7478e48e648c9caf8107b \
file://cmake/COPYING-CMAKE-SCRIPTS;md5=54c7042be62e169199200bc6477f04d1"
SRC_URI = https://dlm.mariadb.com/2319728/Connectors/c/connector-c-3.3.1/mariadb-connector-c-3.3.1-src.tar.gz;name=source
SRC_URI[source.md5sum] = "bd8090528becf9a788f78ed14bb90764"
SRC_URI[source.sha256sum] = "29993f4ae4c975662724978792d1a503b9ee760fbb194d321a754253cbe60aad"

S = "${WORKDIR}/mariadb-connector-c-3.3.1-src"

DEPENDS = "zlib openssl gnutls krb5 curl zstd"

inherit cmake

do_configure() {
cd ${WORKDIR}/build/
cmake ../mariadb-connector-c-3.3.1-src -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
}

do_compile() {
cmake -DCMAKE_TOOLCHAIN_FILE=../toolchain.cmake --build .
}

Here is the link to the log file: https://pastebin.com/qK20ZJsK

I'm new to yocto, so please let me know if I must provide more details! Additionally, I managed to successfully compile and install mariadb-connector-c on the host Ubuntu 18.04.6 LTS system.

Thanks!
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.19.rc1)

Teoh, Jay Shen
 

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.19.rc1. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. NUC 7
3. NUC 6
4. Edgerouter
5. Beaglebone

ETA for completion this Friday, August 26.

Thanks,
Jay

-----Original Message-----
From: qa-build-notification@... <qa-build-
notification@...> On Behalf Of Pokybuild User
Sent: Tuesday, 23 August, 2022 5:59 AM
To: yocto@...
Cc: qa-build-notification@...
Subject: [qa-build-notification] QA notification for completed autobuilder
build (yocto-3.1.19.rc1)


A build flagged for QA (yocto-3.1.19.rc1) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.19.rc1


Build hash information:

bitbake: 17be38290d1e971cd89785e6bf44caef0a6416f8
meta-agl: 8ce71214c1935c2160d139140972f328afacabee
meta-arm: 69547052727a461f33967e64630aa03b34a7eadd
meta-aws: bc38cc397e98c6d6d8d4b701de5944f72d169108
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 8ed6f20cfb116e88e573ee6a08637aa5ac12e1c5
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: f22bf6efaae61a8fd9272be64e7d75223c58922e
meta-virtualization: a63a54df3170fed387f810f23cdc2f483ad587df
oecore: a3cba15142e98177119ef36c09f553d09acf35ef
poky: 4aad5914efe9789755789856882aac53de6c4ed3



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...
M+ & H bugs with Milestone Movements WW34

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW34 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

14125

busybox wget ssl is exposed to MitM attack due to CVE-2018-1000500

randy.macleod@...

shachar@...

4.1 M2

4.1 M4

 

14201

Bitbake server intermittent timeout

randy.macleod@...

unassigned@...

4.1 M2

4.1 M4

 

14263

AB-INT PTEST: lttng-tools ptest intermittent failure

randy.macleod@...

unassigned@...

4.1 M2

4.1 M4

 

14467

curl timeout while dnf is downloading package

randy.macleod@...

sakib.sajal@...

4.1 M2

4.1 M4

 

14486

qemu rootfs copy is taking too much time

randy.macleod@...

Aryaman.Gupta@...

4.1 M2

4.1 M4

 

14522

qemuppc doesn't shutdown within timeout (serial console issues)

randy.macleod@...

sakib.sajal@...

4.1 M2

4.1 M4

 

14665

AB-INT: prservice.BitbakePrTests.test_import_export_replace_db failure

randy.macleod@...

unassigned@...

4.1 M2

4.1 M4

 

14694

logrotate.LogrotateTest.test_logrotate_wtmp failure: /var/lib/logrotate.status is already locked

randy.macleod@...

unassigned@...

4.1 M2

4.1 M3

 

14705

weston.WestonTest.test_wayland_info intermittent failure

randy.macleod@...

randy.macleod@...

4.1

4.1 M4

 

14713

AB-INT-NET: TLS Handshake failure during gotoolchain

randy.macleod@...

bruce.ashfield@...

4.1 M2

4.1 M4

 

14716

Add additional resolvers to autobuilder workers

randy.macleod@...

mhalstead@...

4.1 M2

4.1 M3

 

14789

ltp controllers test failure

randy.macleod@...

Aryaman.Gupta@...

4.1 M2

4.1 M4

 

14823

AB-INT-NET: network failure when fetching yocto-autobuilder-helper

randy.macleod@...

mhalstead@...

4.1 M2

4.1 M3

 

14857

AB-INT: Unable to connect to bitbake server, or start one

randy.macleod@...

unassigned@...

4.1 M2

4.1 M4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Enhancements/Bugs closed WW34!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

randy.macleod@...

5

johannes.schrimpf@...

1

richard.purdie@...

1

Grand Total

7

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Current high bug count owners for Yocto Project 4.1

Stephen Jolley
 

All,

Below is the list as of top 36 bug owners as of the end of WW34 of who have open medium or higher bugs and enhancements against YP 4.1.   There are 47 possible work days left until the final release candidates for YP 4.1 needs to be released.

Who

Count

michael.opdenacker@...

36

david.reyna@...

23

bruce.ashfield@...

22

ross.burton@...

21

randy.macleod@...

16

richard.purdie@...

15

sakib.sajal@...

11

saul.wold@...

10

JPEWhacker@...

9

Aryaman.Gupta@...

7

sundeep.kokkonda@...

6

tim.orling@...

6

jon.mason@...

4

mhalstead@...

3

akuster808@...

3

pavel@...

3

Qi.Chen@...

2

pgowda.cve@...

2

hongxu.jia@...

2

sgw@...

2

tvgamblin@...

2

mostthingsweb@...

1

thomas.perrot@...

1

martin.beeger@...

1

raj.khem@...

1

Martin.Jansa@...

1

shachar@...

1

ola.x.nilsson@...

1

alexandre.belloni@...

1

nicolas.dechesne@...

1

behanw@...

1

aehs29@...

1

ptsneves@...

1

skulkarni@...

1

open.source@...

1

alejandro@...

1

Grand Total

220

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 414 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now,  “4.1”, “4.2”, "4.99" and "Future", the more pressing/urgent issues being in "4.1" and then “4.2” and “4.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 
Re: Bitbake + Patches

Khem Raj
 

On Mon, Aug 22, 2022 at 1:54 PM bitflipper <forums@...> wrote:



I was told this was the right group to ask my question. If this is not right, please let me know.

I am currently using Zeus, and with Zeus, we get Apache v2.4.41. But I would like to get a later version of apache because there have been a few fixes related to cyber security. So I believe that, given we’re using Zeus, we can’t upgrade to the latest version of Apache given the current recipe that Zeus uses. Therefore I believe that the only way accomplish getting tho the latest version of apache with Zeus would to be ‘patch’ the v2.4.41 version that comes with Zeus.

Looking at the Bitbake manual, in section 4.1, it states the following:

"BitBake takes several steps when fetching source code or files. The fetcher codebase deals with two distinct processes in order: obtaining the files from somewhere (cached or otherwise) and then unpacking those files into a specific location and perhaps in a specific way. Getting and unpacking the files is often optionally followed by patching. Patching, however, is not covered by this module."


The manual does not cover patching.

Where can I get information on this process of patching something like apache or any other application that was add via IMAGE_INSTALL_append method.

Any help pointing me to where this process might be documented is much appreciated.
look into mega manual something like this would help
https://docs.yoctoproject.org/dev-manual/common-tasks.html?highlight=writing+recipe#patching-code



Thanks, Jim
QA notification for completed autobuilder build (yocto-3.1.19.rc1)

Pokybuild User <pokybuild@...>
 

A build flagged for QA (yocto-3.1.19.rc1) was completed on the autobuilder and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.19.rc1


Build hash information:

bitbake: 17be38290d1e971cd89785e6bf44caef0a6416f8
meta-agl: 8ce71214c1935c2160d139140972f328afacabee
meta-arm: 69547052727a461f33967e64630aa03b34a7eadd
meta-aws: bc38cc397e98c6d6d8d4b701de5944f72d169108
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 8ed6f20cfb116e88e573ee6a08637aa5ac12e1c5
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: f22bf6efaae61a8fd9272be64e7d75223c58922e
meta-virtualization: a63a54df3170fed387f810f23cdc2f483ad587df
oecore: a3cba15142e98177119ef36c09f553d09acf35ef
poky: 4aad5914efe9789755789856882aac53de6c4ed3



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...
Bitbake + Patches

bitflipper <forums@...>
 



I was told this was the right group to ask my question. If this is not right, please let me know.

I am currently using  Zeus, and with Zeus, we get Apache v2.4.41. But I would like to get a later version of apache because there have been a few fixes related to cyber security. So I believe that, given we’re using Zeus, we can’t upgrade to the latest version of Apache given the current recipe that Zeus uses. Therefore I believe that the only way accomplish getting tho the latest version of apache with Zeus would to be ‘patch’  the v2.4.41 version that comes with Zeus.

Looking at the Bitbake manual, in section 4.1, it states the following:

"BitBake takes several steps when fetching source code or files. The fetcher codebase deals with two distinct processes in order: obtaining the files from somewhere (cached or otherwise) and then unpacking those files into a specific location and perhaps in a specific way. Getting and unpacking the files is often optionally followed by patching. Patching, however, is not covered by this module."


The manual does not cover patching. 

Where can I get information on this process of patching something like apache or any other application that was add via IMAGE_INSTALL_append method.

Any help pointing me to where this process might be documented is much appreciated.


Thanks, Jim
Re: Create the patch for the linux kernel module #dunfell

Mahendra Sondagar
 

Hi... Quentin
Yes, it works!

I'm able to customise the kernel module by the patch


Many thanks :)

Regards,
Mahendra


On Mon, Aug 22, 2022 at 11:09 PM Mahendra Sondagar <mahendrasondagar08@...> wrote:
Hi...Quentin

Thanks for the revert :)
Let me try this

Regards
Mahendra

On Mon, Aug 22, 2022 at 10:49 PM Quentin Schulz <foss+yocto@...> wrote:
Hi Mahendra,

On August 22, 2022 7:04:46 PM GMT+02:00, mahendrasondagar08@... wrote:
>Hi... Khem Raj
>
>First of all, Thanks for the swift reply.
>Let me brief the case.
>
>Actually, I'm dealing with the TP-Link Bluetooth dongle
>I have been enabled it's suitable drivers
>However, the things not working well
>
>After some googling, i got to know that to work with the TP-Link Bluetooth dongle, I'll have to apply the patch by making some changes at the busb.c and hci_ldisc.c files
>And that's how, I have created it's patches by *git diff --no-index* command *
>
>* FYI: I have meta-custom layer, in which i have created the recpies-kernel/linux/stm32mp1 directory
>I have stored, all 2 patches in to the stm32mp1 files
>
>in linux file, i have created the .bbappend file called *linux-stm32mp_%.bbappend*
>For the instance, i have added the all to patches path in to the .bbappend file at *SRC_URI*
>
>Now, My problem is,  during the baking of the custom image I'm getting the following errors
>*"can't find file to patch at input line 5"*
>
>*Error logs*
>
>For your reference, i have attached the contents of the .bbappend file and patch here
>
>In above .bbappend file, the last two patches are for this modules which i need to modify
>
>Once of the patch contents are mentioned at here
>
>I have also attached both of these patches here
>
>I guess, there might be some issue with the actual source file location mentioned in to the patches
>but, I'm not sure
>

The issue is that the path in your patch is incorrect, it should not have kernel-source/ in it, just remove it.

Cheers,
Quentin


>Pl. suggest me the right solution
>
>Thanks
>Mahendra
Re: Create the patch for the linux kernel module #dunfell

Mahendra Sondagar
 

Hi...Quentin

Thanks for the revert :)
Let me try this

Regards
Mahendra


On Mon, Aug 22, 2022 at 10:49 PM Quentin Schulz <foss+yocto@...> wrote:
Hi Mahendra,

On August 22, 2022 7:04:46 PM GMT+02:00, mahendrasondagar08@... wrote:
>Hi... Khem Raj
>
>First of all, Thanks for the swift reply.
>Let me brief the case.
>
>Actually, I'm dealing with the TP-Link Bluetooth dongle
>I have been enabled it's suitable drivers
>However, the things not working well
>
>After some googling, i got to know that to work with the TP-Link Bluetooth dongle, I'll have to apply the patch by making some changes at the busb.c and hci_ldisc.c files
>And that's how, I have created it's patches by *git diff --no-index* command *
>
>* FYI: I have meta-custom layer, in which i have created the recpies-kernel/linux/stm32mp1 directory
>I have stored, all 2 patches in to the stm32mp1 files
>
>in linux file, i have created the .bbappend file called *linux-stm32mp_%.bbappend*
>For the instance, i have added the all to patches path in to the .bbappend file at *SRC_URI*
>
>Now, My problem is,  during the baking of the custom image I'm getting the following errors
>*"can't find file to patch at input line 5"*
>
>*Error logs*
>
>For your reference, i have attached the contents of the .bbappend file and patch here
>
>In above .bbappend file, the last two patches are for this modules which i need to modify
>
>Once of the patch contents are mentioned at here
>
>I have also attached both of these patches here
>
>I guess, there might be some issue with the actual source file location mentioned in to the patches
>but, I'm not sure
>

The issue is that the path in your patch is incorrect, it should not have kernel-source/ in it, just remove it.

Cheers,
Quentin


>Pl. suggest me the right solution
>
>Thanks
>Mahendra
Re: Create the patch for the linux kernel module #dunfell

Quentin Schulz
 

Hi Mahendra,

On August 22, 2022 7:04:46 PM GMT+02:00, mahendrasondagar08@... wrote:
Hi... Khem Raj

First of all, Thanks for the swift reply.
Let me brief the case.

Actually, I'm dealing with the TP-Link Bluetooth dongle
I have been enabled it's suitable drivers
However, the things not working well

After some googling, i got to know that to work with the TP-Link Bluetooth dongle, I'll have to apply the patch by making some changes at the busb.c and hci_ldisc.c files
And that's how, I have created it's patches by *git diff --no-index* command *

* FYI: I have meta-custom layer, in which i have created the recpies-kernel/linux/stm32mp1 directory
I have stored, all 2 patches in to the stm32mp1 files

in linux file, i have created the .bbappend file called *linux-stm32mp_%.bbappend*
For the instance, i have added the all to patches path in to the .bbappend file at *SRC_URI*

Now, My problem is,  during the baking of the custom image I'm getting the following errors
*"can't find file to patch at input line 5"*

*Error logs*

For your reference, i have attached the contents of the .bbappend file and patch here

In above .bbappend file, the last two patches are for this modules which i need to modify

Once of the patch contents are mentioned at here

I have also attached both of these patches here

I guess, there might be some issue with the actual source file location mentioned in to the patches
but, I'm not sure
The issue is that the path in your patch is incorrect, it should not have kernel-source/ in it, just remove it.

Cheers,
Quentin


Pl. suggest me the right solution

Thanks
Mahendra
Re: Create the patch for the linux kernel module #dunfell

Mahendra Sondagar
 

Hi... Khem Raj

First of all, Thanks for the swift reply.
Let me brief the case.

Actually, I'm dealing with the TP-Link Bluetooth dongle
I have been enabled it's suitable drivers
However, the things not working well

After some googling, i got to know that to work with the TP-Link Bluetooth dongle, I'll have to apply the patch by making some changes at the busb.c and hci_ldisc.c files
And that's how, I have created it's patches by git diff --no-index command


FYI: I have meta-custom layer, in which i have created the recpies-kernel/linux/stm32mp1 directory
I have stored, all 2 patches in to the stm32mp1 files

in linux file, i have created the .bbappend file called linux-stm32mp_%.bbappend
For the instance, i have added the all to patches path in to the .bbappend file at SRC_URI

Now, My problem is,  during the baking of the custom image I'm getting the following errors 
"can't find file to patch at input line 5"

Error logs


For your reference, i have attached the contents of the .bbappend file and patch here 



In above .bbappend file, the last two patches are for this modules which i need to modify

Once of the patch contents are mentioned at here




I have also attached both of these patches here

I guess, there might be some issue with the actual source file location mentioned in to the patches
but, I'm not sure

Pl. suggest me the right solution

Thanks
Mahendra

stm32mp157a-dk1.dts.orig

stm32mp157a-dk1.dts.orig
0003-stm32mp157a-dk1-hci_ldisc-fix.patch

0003-stm32mp157a-dk1-hci_ldisc-fix.patch
0002-stm32mp157a-dk1-btusb-fix.patch

0002-stm32mp157a-dk1-btusb-fix.patch

Re: Error while testing "core-image-minimal" through "bitbake core-image-minimal -c testimage -v" #linux #warning #toolchain #bitbake #dunfell

Alexander Kanavin
 

You need to rebuild the image:

bitbake core-image-minimal

Alex

On Mon, 22 Aug 2022 at 12:32, Nikita Gupta <nikitagupta2509@...> wrote:

Hello

i was not able to find that how to force a no-graphical execution by unset Display before running bitbake . So i again tried to test my image by previous method
bitbake rpm busybox curl run-postinsts
bitbake package-index
bitbake core-image-minimal -c testimage -v

but this time i did not get error like previous one this time i lost my deploy folders in which images folder was present . i have no idea how it happened i am able to see all folders except deploy ( see in attachment) .

kindly tell why deploy folder got disappeared and how i can recover that ?

Thanks in Advance
Re: Error while testing "core-image-minimal" through "bitbake core-image-minimal -c testimage -v" #linux #warning #toolchain #bitbake #dunfell

Nikita Gupta <nikitagupta2509@...>
 

Hello 

i was not able to find that how to force a no-graphical execution by unset Display before running bitbake . So i again tried to test my image by previous method 
bitbake rpm busybox curl run-postinsts
bitbake package-index
bitbake core-image-minimal -c testimage -v

but this time i did not get error like previous one this time i lost my deploy folders in which images folder was present . i have no idea how it happened i am able to see all folders except deploy ( see in attachment) .

kindly tell  why deploy folder got disappeared and how i can recover that ?

Thanks in Advance

Screenshot from 2022-08-22 15-20-15.png

Re: Create the patch for the linux kernel module #dunfell

Khem Raj
 



On Sat, Aug 20, 2022 at 11:52 AM <mahendrasondagar08@...> wrote:

Hi... Community

Hope all are doing well

I'm dealing with the yocto dunfell branch with the STM32MP1

I know, how to create the patch for the device tree source (DTS) and add with the custom image

My intend is to modify the busb.c to work with my bluetooth USB dongle
I have create the patch for the same and adding the same way as i does with the DTS file

But, unfortunately, it's causing the issue wile baking the image!


If it’s in-tree kernel module then you create a patch with your changes and apply it via recipe like any other recipe is going to do in metadata 

However you need to share specific details on errors so someone can get a better content to help you 


Can any one redirect me to the tutorial to customize the kernel module via patch under yocto ?

 

All suggestions and comments welcome

Thanks
Mahendra
2341 - 2360 of 60175