Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: dmitry.baryshkov@oss.qualcomm.com,
	 openembedded-core@lists.openembedded.org
Cc: "Khem Raj" <raj.khem@gmail.com>,
	"Zoltán Böszörményi" <zboszor@gmail.com>
Subject: Re: [OE-core] [PATCH v3 0/9] mesa: upgrade to 25.0.2
Date: Sun, 30 Mar 2025 23:40:19 +0100	[thread overview]
Message-ID: <f260bc5fa637f949b5877c5281cc71b70dfd1fd9.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250329-mesa-25-v3-0-f4d0328eb867@oss.qualcomm.com>

On Sat, 2025-03-29 at 22:07 +0200, Dmitry Baryshkov via
lists.openembedded.org wrote:
> libclc is required in order to build Intel drivers in Mesa 24.1 and
> later. Thus OE-Core is currently locked to the 24.0.x branch, which
> is
> no longer maintained, having last release in June 2024.
> 
> A clean solution is to package Clang, then use it to build libclc and
> SPIRV-LLVM-Translator (required for Mesa OpenCL support). However
> creating proper recipes for Clang is a long process (ongoing by Khem
> Raj).
> 
> This patchset attempts to solve the issue in a simpler way: by
> building
> libclc and SPIRV-LLVM-Translator together with the LLVM. This way we
> don't have to create target Clang recipes, there is no extra
> toolchain
> to support, etc. Clang binaries are creted as a part of the build
> process (in order to support building target packages), however it
> only
> hits the LLVM sysroot-native and is only used by the LLVM target
> build.
> 
> Future work by Khem (once Clang is properly supported in OE-Core)
> should
> allow us to create proper recipes for libclc and spirv-llvm-
> translator
> and drop them from the llvm / clang recipe.
> 
> I think this approach provides a good balance between OE-Core being
> stuck with the outdated Mesa release and being able to upgrade it,
> bringing support for new hardware.
> 
> Last two patches of the series bring in RustiCL support, a new OpenCL
> implementation within Mesa. They are optional for the sake of the
> upgrade and can be dropped if there is any issue with those. RustiCL
> support is mostly compile-tested at this point.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

Thanks for the patches. I haven't looked in detail yet but I did try
running them through testing which revealed:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/1283

as well as some issues working with meta-clang:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/18/builds/652

There are other patches causing issues in that build, I'll leave it
running in case it can spot any other issues with this patch series.

Cheers,

Richard


  parent reply	other threads:[~2025-03-30 22:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-29 20:07 [PATCH v3 0/9] mesa: upgrade to 25.0.2 Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 1/9] llvm: move libLLVM.so.N.M to llvm-libllvm package Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 2/9] llvm: use OECMAKE_SOURCEPATH to specify cmake dir Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 3/9] llvm: handle libdir in llvm-config Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 4/9] llvm: also use llvm-config wrapper for nativesdk recipes Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 5/9] llvm: support building libclc Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 6/9] llvm: add SPIRV-LLVM-Translator support Dmitry Baryshkov
2025-03-29 20:43   ` Patchtest results for " patchtest
2025-03-29 21:02     ` Dmitry Baryshkov
2025-03-31 10:13   ` [OE-core] " Alexander Kanavin
2025-03-31 11:46     ` Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 7/9] mesa: upgrade 24.0.7 -> 25.0.2 Dmitry Baryshkov
2025-03-31 10:17   ` [OE-core] " Alexander Kanavin
2025-03-29 20:07 ` [PATCH v3 8/9] bindgen-cli: a tool to generate Rust bindings Dmitry Baryshkov
2025-03-29 20:07 ` [PATCH v3 9/9] mesa: add support for RustiCL under PACKAGECONFIG "opencl" Dmitry Baryshkov
2025-03-31 10:22   ` [OE-core] " Alexander Kanavin
2025-03-30 22:40 ` Richard Purdie [this message]
2025-03-31 10:15   ` [OE-core] [PATCH v3 0/9] mesa: upgrade to 25.0.2 Dmitry Baryshkov

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=f260bc5fa637f949b5877c5281cc71b70dfd1fd9.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=zboszor@gmail.com \
    /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