soo.. apparently the broadcom VC4+ GPUs (the ones used in raspberry pis and stuff) do not support format-less image writes, sooo.. supporting OpenCL images in #rusticl on that hardware will be a bit "difficult", because it needs to be handled within the kernel...
I should probably check out how other drivers are handling this, because either I'm missing something here or some other vendors are kinda in the same situation (not for all hardware, probably just older GPUs).
The driver replaced the backing buffer object of a host mapped memory object causing random faults and inconsistency issues.
Sadly the way mapping memory in OpenCL works is pretty annoying. I fear I'll have to rework those bits in #rusticl as well, because I'm way to optimistic on some assumptions. And I'll also have to fix contexts with multiple devices while at it.
@karolherbst Mesa3D is big enough to distros do the same. But before next release, I would aim to enable it by default with some drivers, so distros have more motivation to include #Rusticl
I just posted a short tutorial on setting up a simple #LLM on your #oneplus6 running #postmarketOS . The LLM (7b alpaca in this case) is not terribly accurate but possibly useful in some cases.
Warning! You phone will get hot. I haven't tested it long enough to know if it will harm your device, but do be careful.
Oh! I have a website now! Wow! My history with websites is hit and miss, so enjoy it while it lasts. I have half a dozen posts in the works already.