From: "Guo, Yanmei" <yanmei.guo@boeing.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
"Jesus.JimenezSanchez@verifone.com"
<Jesus.JimenezSanchez@verifone.com>
Subject: RE: [EXTERNAL] Re: [yocto] Help enabling the BT_QCA driver
Date: Thu, 10 Oct 2024 05:27:53 +0000 [thread overview]
Message-ID: <c3abd08e14094d17b776808fe437cfa2@boeing.com> (raw)
In-Reply-To: <10004.1728466643973723741@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
Could it be that you disabled the support of the kernel modules in the kconfig by accident?
This config in particular,
```
CONFIG_MODULES=y
```
-May
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Jesus Jimenez Sanchez via lists.yoctoproject.org
Sent: Wednesday, October 9, 2024 8:07 PM
To: Jesus Jimenez Sanchez <Jesus.JimenezSanchez@verifone.com>; yocto@lists.yoctoproject.org
Subject: [EXTERNAL] Re: [yocto] Help enabling the BT_QCA driver
EXT email: be mindful of links/attachments.
Hello,
I wanted to add that I have been able to enable the driver using menuconfig by enabling its dependencies.
The problem I'm facing now is that Yocto is not building the kernel object files (.ko), not even the ones it was building before. As far as I know I have only changed the configuration to build this new driver but I could be wrong and maybe touche where I shouldn't.
Is there a way to tell Yocto to build those kernel objects?
Thank you.
[-- Attachment #2: Type: text/html, Size: 9736 bytes --]
prev parent reply other threads:[~2024-10-10 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 15:10 Help enabling the BT_QCA driver Jesus Jimenez Sanchez
2024-10-09 9:37 ` [yocto] " Jesus Jimenez Sanchez
2024-10-09 21:58 ` Khem Raj
2024-10-10 5:27 ` Guo, Yanmei [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3abd08e14094d17b776808fe437cfa2@boeing.com \
--to=yanmei.guo@boeing.com \
--cc=Jesus.JimenezSanchez@verifone.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox