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. 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 on headers from glsl, and I cannot find anywhere where it's possible to restrict the built version of GL, so maybe it's not possible to build a restricted version?
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 on headers from glsl, and I cannot find anywhere where it's possible to restrict the built version of GL, so maybe it's not possible to build a restricted version?
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 done on PC/Linux systems. Hard to believe it's been 30 years! [snip] 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'm not familiar with PiStorm32/Emu68 but the first big issue may be that Mesa makes pervasive use of 64-bit datatypes (int64_t, uint64_t). Just from its name, PiStorm32/Emu68 sounds like a 32-bit environment. So unless your compiler has good support for emulating 64-bit types with 32-bit operations, you may be out of luck. That's not the biggest issue. The biggest issue seems to be the pervasive pthreading throughout the library, which may be switching to C11 threading in future, I don't know, I dropped C and C++ (for good reasons) back in 2005 and haven't followed either so don't know what is planned for C11 thread support. It seems that is there is patchy support for pthreads, this has always been in case even bitd when I was using Amiga's daily. I really don't know whether the OS can even support a full pthreads implementation, I've seen people say it cannot. But there are issues with the toolchain, bebbo's gcc install raises false positives in the setup stage, i.e. clib2 installs: /opt/amiga-gcc/m68k-amigaos/clib2/include/dlfcn.h with no library backing it up. AmigaOS 3.x has a libdl on Aminet which works to some degree, I've not tested it thoroughly to see what it can and cannot handle. Latest zlib builds and installs with the command from the older zlib on Aminet. Even expat built, but the benchmark program would refuse to execute under AmigaOS with the OS saying it wasn't executable when it was. A simple hello world test program ran fine though, so the compiler does work. Luke.
Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots
> Am 12.04.2023 um 17:39 schrieb Brian Paul : > > On 4/12/23 02:30, Ignacio Soriano Hernandez wrote: >> !! External Email >> Dear Mesa dev community, >> Please let me apologize if you consider this off topic but I think that this >> is probably the audience that could help in reviving and getting back to the >> roots where Mesa3D originated from. >> 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 done on PC/Linux systems. > > Hard to believe it's been 30 years! > > >> So thirty years later the AMIGA community is still huge, growing and the >> development on hardware and software accelerators is giving us new >> capabilities. One of the most interesting projects has been the PiStorm32 >> and Emu68 which enable the AMIGA to use a Pi as CPU accelerator with a >> baremetal ARM <-> 68k CPU emulator. Incredible CPU power but no access to >> the GPU and acceleration that could also boost graphics capabilities and >> applications via an RTG (Retargetable Graphics) access. The AMIGA OS is >> actively being developed (yes, still 40 years later) and AMIGA >> cross-compiler toolchains do exist for all kind of nowadays operating >> systems. >> So what are we looking for? An experienced Mesa3D developer with and >> affinity/background for/on AMIGA that would be interested in porting an >> actual Mesa3D build to the PiStorm32/Emu68/AMIGA OS combo. Yes, 30 years >> later where it originated from. We have been collecting some funds as we >> know that this is not a weekend job but maybe someone is looking to for a >> challenge where „this is impossible“ gains your interest. > > I'm not familiar with PiStorm32/Emu68 but the first big issue may be that > Mesa makes pervasive use of 64-bit datatypes (int64_t, uint64_t). Just from > its name, PiStorm32/Emu68 sounds like a 32-bit environment. So unless your > compiler has good support for emulating 64-bit types with 32-bit operations, > you may be out of luck. > > -Brian > > Brian, thanks for taking the time .. while doing research I could see that you used AMIGA’s for nearly 10 years, we love it. With regards to the compiler it would be as good as gcc is as this is one of the core cross-compiler environments being used nowadays for AMIGA development, vbcc is another option. What we were mostly thinking of bigger challenges are around the whole infrastructure Mesa3D requires, shader compiler, X and Linux dependencies etc. to summarize it up we would need to understand the bigger picture so that we can can look into this tremendous task more realistically. There are some really good AMIGA programmers that would like to get onto "this mission to Mars“ but we lack the understanding of Mesa3D to a level where we know how we could try to do that with AMIGA OS. Thanks Iggi
Re: Porting / AMIGA / PiStorm32 / developer needed - Back to the roots
On 4/12/23 02:30, Ignacio Soriano Hernandez wrote: !! External Email Dear Mesa dev community, Please let me apologize if you consider this off topic but I think that this is probably the audience that could help in reviving and getting back to the roots where Mesa3D originated from. 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 done on PC/Linux systems. Hard to believe it's been 30 years! So thirty years later the AMIGA community is still huge, growing and the development on hardware and software accelerators is giving us new capabilities. One of the most interesting projects has been the PiStorm32 and Emu68 which enable the AMIGA to use a Pi as CPU accelerator with a baremetal ARM <-> 68k CPU emulator. Incredible CPU power but no access to the GPU and acceleration that could also boost graphics capabilities and applications via an RTG (Retargetable Graphics) access. The AMIGA OS is actively being developed (yes, still 40 years later) and AMIGA cross-compiler toolchains do exist for all kind of nowadays operating systems. So what are we looking for? An experienced Mesa3D developer with and affinity/background for/on AMIGA that would be interested in porting an actual Mesa3D build to the PiStorm32/Emu68/AMIGA OS combo. Yes, 30 years later where it originated from. We have been collecting some funds as we know that this is not a weekend job but maybe someone is looking to for a challenge where „this is impossible“ gains your interest. I'm not familiar with PiStorm32/Emu68 but the first big issue may be that Mesa makes pervasive use of 64-bit datatypes (int64_t, uint64_t). Just from its name, PiStorm32/Emu68 sounds like a 32-bit environment. So unless your compiler has good support for emulating 64-bit types with 32-bit operations, you may be out of luck. -Brian
