Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots

Hi, Some progress, on building, not testing: $ find . -name 'lib*.a' ./src/compiler/isaspec/libisaspec.a ./src/util/libmesa_util_sse41.a ./src/util/blake3/libblake3.a ./src/gallium/frontends/osmesa/libosmesa_st.a ./src/gallium/drivers/softpipe/libsoftpipe.a So, maybe it might just be possible.

Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots

The build could be worked to get a gles1 lib, which isn't optimal given the power of the pi's gpu. On 18/04/2024 11:57, Luke A. Guest wrote: On 18/04/2024 11:23, Luke A. Guest wrote: I took a look at this over the last few days with the plan to use fs-uae to get the following built: 1

Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots

On 18/04/2024 11:23, Luke A. Guest wrote: I took a look at this over the last few days with the plan to use fs-uae to get the following built: 1. Static lib build. 2. Aim for GL 1.5. 3. swrast (softpipe) and osmesa. I just disabled the compiler directory and found that libmesa depends

Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots

On 12/04/2023 16:39, Brian Paul wrote: On 4/12/23 02:30, Ignacio Soriano Hernandez wrote: > To use Brian Paul’s words: The core library was originally (started in 1993) written on an Amiga using the DCC compiler. Later, development was moved to an SGI workstation.  Current development is

Re: [Mesa-dev] Trying to build a opencl dev env

How do you run the opencl-cts tests on this? ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] Trying to build a opencl dev env

On 27/04/2021 08:00, Pierre Moreau wrote: Hello Luke, If you set `PKG_CONFIG_PATH=$PATH_TO_LIBCLC_INSTALL/share/pkgconfig` when running meson, it should pick that version instead of the system one. I run it as `PKG_CONFIG_PATH=[…] meson setup […]`; it might also be possible to pass it as an

[Mesa-dev] Trying to build a opencl dev env

Hi, So, I've built a generic LLVM tree for mesa and other projects and installed it alongside SPIRV-LLVM-Translator into $HOME/opt/llvm-dev-reldebug. I have installed libclc there too, although it wouldn't build as part of llvm and make install wouldn't install to the same llvm dir for some

Re: [Mesa-dev] [PATCH 2/2] egl: add linux-dmabuf-unstable-v1-protocol.c to "nodist"

master currently fails when enabling egl because drivers/dri2/linux-dmabuf-unstable-v1-protocol.c doesn't exist, should it? Luke. On 19/07/17 23:44, Andres Gomez wrote: > This fixes `make distcheck` > >> make[3]: *** No rule to make target >> 'drivers/dri2/linux-dmabuf-unstable-v1-protocol.c',

Re: [Mesa-dev] [PATCH 1/2] radv: Use the KHR dedicated alloc for the WSI.

can confirm this fixes the current radv rendering rubbish. Luke. On 15/07/17 18:56, Bas Nieuwenhuizen wrote: > NV isn't valid for external images anymore. > > Signed-off-by: Bas Nieuwenhuizen > Fixes: 6ddc64b93ea "radv: Add support for VK_KHR_dedicated_allocation." > --- >

Re: [Mesa-dev] Status of Clover (AMDGPU)

> I'd suggest that you check out the recently-open-sourced OpenCL > conformance test suite [0] or my slightly-more-linux-build-friendly > fork [1] and give it a run on top of mesa/clover. It'll give you a > good list of things to work on. Thanks, I took a quick look. Yeah, shame they didn't put

Re: [Mesa-dev] Status of Clover (AMDGPU)

> Nobody has worked on RadeonSI OpenCL for quite some time. Even the > main developer of R600 and RadeonSI OpenCL (Tom Stellard) was mostly > working on ROCm when he was at AMD. > >> So far I've found that gl sharing is missing as are some entry points in >> dispatch.cpp. > ROCm OpenCL has

Re: [Mesa-dev] Status of Clover (AMDGPU)

Forgot to mention I would be testing on R9 390 and R9 380 cards. Thanks, Luke. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] Status of Clover (AMDGPU)

as are some entry points in dispatch.cpp. 1) Would it be worth continuting and if so would we be allowed to shared clc files from ROCm to Mesa? 2) If not, is it worth considering porting Beignet instead, that at least gives OpenCL 2.0. Thoughts? Thanks, Luke A. Guest

Re: [Mesa-dev] [RFC] precursor patches to trying to merge radv

On 05/09/16 23:49, Marek Olšák wrote: > On Mon, Sep 5, 2016 at 11:32 PM, Luke A. Guest <lagu...@archeia.com> wrote: >> >> On 05/09/16 18:41, Marek Olšák wrote: >>> On Mon, Sep 5, 2016 at 3:03 AM, Dave Airlie <airl...@gmail.com> wrote: >>>&g

Re: [Mesa-dev] [RFC] precursor patches to trying to merge radv

On 05/09/16 18:41, Marek Olšák wrote: > On Mon, Sep 5, 2016 at 3:03 AM, Dave Airlie wrote: >> So currently out-of-tree radv, reuses addrlib (by copying the all >> the files), and at least wants to share the register and family >> header files. >> >> This is a set of patches