(rusticl) OpenCL command cling is not detecting GPU in raspberry pi 5

Hello, I followed the instructions in https://docs.mesa3d.org/rusticl.html#rusticl to install OpenCL in Raspberry Pi 5. However, clinfo command is not showing any devices. Can anyone help with suggestions? Thank you, Victor smime.p7s Desc

Re: (rusticl) OpenCL command cling is not detecting GPU in raspberry pi 5

On Mon, 2025-01-13 at 16:24 +, Victor Labian Carro wrote: > Hello, >   > I followed the instructions in > https://docs.mesa3d.org/rusticl.html#rusticl to install OpenCL in > Raspberry Pi 5. However, clinfo command is not showing any devices. > Can anyone help with suggestions? >   What is show

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

I would keep the existing modifier interfaces, API extensions, and expectations the same as today for simplicity. The new linear modifier definition (proposal) will have these fields: 5 bits for log2 pitch alignment in bytes 5 bits for log2 height alignment in rows 5 bits for log2 offset

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

Hi Am 14.01.25 um 14:46 schrieb Thomas Zimmermann: Hi Am 15.12.24 um 21:53 schrieb Marek Olšák: The comment explains the problem with DRM_FORMAT_MOD_LINEAR. Signed-off-by: Marek Olšák diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h index 78abd819fd62e..8ec4163

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

Hi Am 15.12.24 um 21:53 schrieb Marek Olšák: The comment explains the problem with DRM_FORMAT_MOD_LINEAR. Signed-off-by: Marek Olšák diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h index 78abd819fd62e..8ec4163429014 100644 --- a/include/uapi/drm/drm_fourcc.h +++ b/

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

I don't see how that fits in the current modifier usage patterns. I'm not clear how applications are supposed to programmatically "look at the modifiers of other drivers to find commonalities," nor how that "keeps "expectations the same as today for simplicity.". I think replacing the existing

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

Hi, On Tue, 14 Jan 2025 at 09:38, Marek Olšák wrote: > I would keep the existing modifier interfaces, API extensions, and > expectations the same as today for simplicity. Well yes, not just for simplicity, but because everything stops working if you don't. > The new linear modifier definition

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

On January 14, 2025 03:39:45 Marek Olšák wrote: I would keep the existing modifier interfaces, API extensions, and expectations the same as today for simplicity. The new linear modifier definition (proposal) will have these fields: 5 bits for log2 pitch alignment in bytes 5 bits for log2 h

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

On Tue, Jan 14, 2025 at 1:34 PM Faith Ekstrand wrote: > On January 14, 2025 03:39:45 Marek Olšák wrote: > >> I would keep the existing modifier interfaces, API extensions, and >> expectations the same as today for simplicity. >> >> The new linear modifier definition (proposal) will have these fi

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

On Tue, Jan 14, 2025 at 12:55 PM James Jones wrote: > I don't see how that fits in the current modifier usage patterns. I'm > not clear how applications are supposed to programmatically "look at the > modifiers of other drivers to find commonalities," nor how that "keeps > "expectations the same

Re: [PATCH] drm/fourcc: add LINEAR modifiers with an exact pitch alignment

On Tue, Jan 14, 2025 at 12:58 PM Daniel Stone wrote: > Hi, > > On Tue, 14 Jan 2025 at 09:38, Marek Olšák wrote: > > I would keep the existing modifier interfaces, API extensions, and > expectations the same as today for simplicity. > > Well yes, not just for simplicity, but because everything st