I've got a soft Mesa working now with OpenGL 1.1; it took a while to get it building in the autobuilder but it's working now. The hardware rendered version is also working again on the Iyonix.

I also managed to get the latest Mesa building in Ubuntu with software and hardware rendering - it took a while because I spent quite a lot of time trying to get it working on macOS, but then I ended up dual-booting Ubuntu on my Windows PC so I'm unblocked now.

I've had a very busy August at work and I'm about to go to the UK for 3 weeks (departing in a few hours). I don't have any way to do development while I am there because my work laptop is locked down and cannot run a VM.

I uploaded the RISC OS version of Mesa to github a couple of weeks ago: https://github.com/simonrules/Mesa-3.4.1-riscos

There are some demo files in the ros_demos directory.

I will push my latest changes there today so that readers are able to try with the autobuilder.

Here is an article of Nemo about data transfer and Clipboard

https://www.getrevue.co/profile/nemo20000/issues/the-ineffability-of-the-data-transfer-and-clipboard-protocols

Currently there exists one port of a raytracer for RISC OS of POVray https://www.riscosports.co.uk/vfp/
But there exists some more sophisticated renderers that could be ported.

https://www.mitsuba-renderer.org/

Watch the video about the physical based rendering technology:
http://rgl.epfl.ch/publications/NimierDa...19Mitsuba2

or

https://www.pbrt.org/

https://www.pbrt.org/gallery

PBRT example:




Who would like to port them and maybe inetgrate them into an 3D editor. A very simple 3D editor is available in the form of the Merlin 3D editor on this site also.

One application that is really missing in RISC OS is a 2D/3D CAD program.
There is RiscCAD for £30 (35 EUR / 40 USD) Visit RiscCAD website
and ProCAD for £60 (70 EUR / 80 USD) Visit ProCAD website
So one solution to close there gap is to port an open source CAD.

Here are 4 examples what open source CAD software are available:

www.freecadweb.org



www.librecad.org



www.openscad.org



www.salome-platform.org
[url=https://www.youtube.com/watch?v=slK1SVn_G28][/url]

Actually there exists the official GCC release for RISC OS of version 4.7.2.
For the release of the new !Iris browser Lee Noa has been working on GCC 10.2.
There might be some other people involved but I don't have insight information about it. So sorry for possibly incomplete information.

From the GCC mailing list at RISCOS.info I got this info from Chris Gardensen:

The GCCK 10.2.0 native compiler hasn't been released yet. Once you have the
autobuilder set up you can build it yourself.

mkdir gccsdk
cd gccsdk
svn co svn://svn.riscos.info/gccsdk/trunk/autobuilder/ autobuilder
svn co svn://svn.riscos.info/gccsdk/trunk/gcc4/ gcc4

mkdir build
cd build


Create a file call build-setvars containing the following contents.
(Assuming the autobuilder has been installed in /home/gccsdk.)

      GCCSDK_INSTALL_CROSSBIN=/home/gccsdk/cross/bin
      GCCSDK_INSTALL_ENV=/home/gccsdk/env
      RO_SHAREDLIBS=yes
      RO_USE_ARMEABIHF=yes
      AB_ELFBUILD=yes

rm -f /home/gccsdk/autobuilder/develop/gcc/gcc.dwarf2out.c.p
../autobuilder/build -v gcc

The packages for the native compiler will be created in
/home/gccsdk/autobuilder/autobuilder_packages/arm/Development.

Using GCC natively on RISC OS is very slow. It's OK for simple stuff.

I had to set a 32000k wimplot otherwise everything froze.

Using GCC 10.2.0 with the autobuilder successully builds e.g. Qupzilla,
RPCEmu, ffmpeg and  mplayer.

RISC OS is missing a standard 3D API and drivers. In the past there have been numerous projects which have attempted to bring 3D rendering to RISC OS, but none had sufficient support or were restricted to a single platform.

The main ones I'm aware of are:

• Software rendered OpenGL 1.x via a Mesa 3.x port from the early 2000s. This had an ARM code renderer and would work on machines of the time but the assembly needs updating for current compilers.
  
• Hardware rendered OpenGL 1.x via a Mesa 3.x port from 2005 for the Iyonix. This had a hardware accelerated renderer but would only work on the Iyonix with specific GeForce cards. Vertex processing was still done in software so although it could run games like GLQuake, it was fairly slow. I made this port.
  
• Hardware rendered "Khronos" driver for the Raspberry Pi 1-3, including a module which provides SWI access to the OpenGL API.
  

Hi all, I wanted to make an introduction. I'm Simon Wilson and I'm working on a 3D driver for RISC OS. I started programming on RISC OS when I was 12 and I have the following (working) machines: A3000, A3010, A5000, A7000+, RiscPC, RiscPC Kinetic, Iyonix, Titanium, ARMBook, and a few Raspberry PIs. 

My background is in embedded software engineering and graphics. I ported the first 3D drivers to Android (for the G1 and Nexus 1 phones) when I was working at Qualcomm, and I'm also the designer/author of tinyalsa (the de-facto audio library for Android) and Nanohub/Context Hub (the sensor co-processor OS for Android).

Please feel free to say hi or ask questions. I'll also post a technical thread for the 3D driver.

One of the missing important drivers for RISC OS is a hardware video decoder for the Raspberry Pi 3 & 4.
this is specially needed in the age of internet where a majority of content is presented as videos.

I found this content:

[/url]https://github.com/rockchip-linux/mpp
https://github.com/rockchip-linux/libv4l-rkmpp


[url=http://opensource.rock-chips.com/wiki_Mpp]http://lkml.iu.edu/hypermail/linux/kerne...02233.html

https://patchwork.kernel.org/project/lin...ulik.info/

https://www.programmersought.com/article/56114329398/
https://lwn.net/Articles/816270/

The task will be two parts:
1. Videoplayer integration into RISC OS that it could be integrated also in web browsers (Iris, NetSurf)
2. Driver to access the hardware video decoder

One of the missing important drivers for RISC OS is a hardware video decoder for the Raspberry Pi 3 & 4.
this is specially needed in the age of internet where a majority of content is presented as videos.

I found this content on the Raspberry Forum:

Pi0-3 have hardware accelerated decode for H264, MPEG4, H263, and through optional codec licences for MPEG2 and VC1.
Pi4 has the same hardware accelerated decode for H264, but not the other codecs. It also has a separate block for HEVC.

The block for H264 etc can only be accessed via the VPU firmware, which means either MMAL or IL. That applies to all platforms.
There is a wrapper above MMAL that implements the V4L2 M2M stateful decoder API - https://github.com/raspberrypi/linux/bl ... l2-codec.c. This should appear as /dev/video10 on our downstream kernel builds.

FFmpeg has a client implementation for V4L2 M2M
V..... h263_v4l2m2m V4L2 mem2mem H.263 decoder wrapper (codec h263)
V..... h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264)
V..... mpeg2_v4l2m2m V4L2 mem2mem MPEG2 decoder wrapper (codec mpeg2video)
V..... mpeg4_v4l2m2m V4L2 mem2mem MPEG4 decoder wrapper (codec mpeg4)
It also has a client implementation for MMAL
V..... h264_mmal h264 (mmal) (codec h264)
V..... mpeg2_mmal mpeg2 (mmal) (codec mpeg2video)
V..... mpeg4_mmal mpeg4 (mmal) (codec mpeg4)
V..... vc1_mmal vc1 (mmal) (codec vc1)

GStreamer likewise has components for V4L2 decode as v4l2h264dec, etc.

HEVC decode on the Pi4 is through a separate block that is driven by the Linux kernel. I'm just finishing off PR for that - https://github.com/raspberrypi/linux/pull/3505.


Full thread can be read here:
https://www.raspberrypi.org/forums/viewt...p?t=268356

Further information:
https://elinux.org/Raspberry_Pi_VideoCore_APIs
https://en.wikipedia.org/wiki/VideoCore

The task will be two parts:
1. Videoplayer integration into RISC OS that it could be integrated also in web browsers (Iris, NetSurf)
2. Driver to access the hardware video decoder of the VideoCore IV (Raspberry Pi 0 to 3) or VI (Raspberry Pi 4)

There is a lack of an up-to-date matrix printer driver for RISC OS. MW-Software offers still the GutenPrint driver but it is based on a version that is about 10 years old.
So the current GutenPrint version must be compiled and integrated into RISC OS printer system.
Martin Würthner from MW Software is willing to supply the sources for the RISC OS printer side but details must be still discussed.

www.gimp-print.sourceforge.net
Sources for GutenPrint