From: Carlos Rafael Giani <crg7475@mailbox.org>
To: meta-freescale@lists.yoctoproject.org
Cc: Max Krummenacher <max.krummenacher@toradex.com>
Subject: Mismatch between linux-imx-headers version and toradex kernel in current git master
Date: Tue, 29 Mar 2022 20:03:25 +0200 [thread overview]
Message-ID: <068df86a-87b0-adaa-13cf-2f9f241d713a@mailbox.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
When building code with support for DMA-BUF heaps (
https://github.com/torvalds/linux/blob/master/include/uapi/linux/dma-heap.h
), I noticed that my code was detecting the dma-heap.h userspace API
header in the Yocto SDK, while on the running system, no dma-heap was found.
It turns out that the linux-imx-headers (which contain the dma-heap.h
header) are from linux-imx 5.10, while the Toradex kernel is at 5.4.
This makes me wonder how to address this. I can think of two options:
1. Recipes of software that supports DMA-BUF heaps needs to have a
"dma-heap" packageconfig that is explicitly disabled on systems with
pre-5.6 kernels (5.6 is when DMA-BUF heaps were added as part of the
userspace API).
2. Somehow check for the actual kernel version in the recipe and turn
off DMA-BUF heaps if the version is <5.6.
Furthermore, I am concerned that such version mismatches between these
two recipes could lead to other subtle errors.
Is a linux-toradex upgrade to 5.10 planned? Or is there a smarter way to
address such version discrepancies?
Carlos
[-- Attachment #2: Type: text/html, Size: 1595 bytes --]
next reply other threads:[~2022-03-29 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 18:03 Carlos Rafael Giani [this message]
2022-03-30 12:02 ` [meta-freescale] Mismatch between linux-imx-headers version and toradex kernel in current git master Otavio Salvador
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=068df86a-87b0-adaa-13cf-2f9f241d713a@mailbox.org \
--to=crg7475@mailbox.org \
--cc=max.krummenacher@toradex.com \
--cc=meta-freescale@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).