>> NVME, USB 3.0
> MorphOS drivers?

Geennaam comment on amiga-news.de:
Tested Linux distributions are all booting and running from NVMe. I also have experience with NVMe drivers, so consider this covered for OS4 and MorphOS as well.

>>> NVME, USB 3.0

>> MorphOS drivers?

> Geennaam comment on amiga-news.de: […] I also have experience
> with NVMe drivers, so consider this covered for […] MorphOS

Alright, so USB3 (USB 3.2 specifically) yet to assign then, I guess.

Update:

> Complete MorphOS-related entries from the "blog": […]

4th June: "A Medal of Honor…
MorphOS developer and Porter Cowcat brought us OpenMOHAA. Lets see if it runs on the Mirari Proto board."
https://www.youtube.com/watch?v=DJF-Xy60lBE

^ Many thanks for completing my request on my bday :) It sure loads much faster and the gameplay is 100% smooth compared to my system (especially when entering large sceneries and battling many enemies). How did you get the fps values on the down left side, so I can do a direct comparison? Overal seems a nice improvement compared to what I have available right now as my main computer at home. I think final test on 3D capabilities should be Doom 3, which along with OpenMohaa are the heaviest software pieces we have to compare.

[ Edited by Cool_amigaN 05.06.2025 - 09:14 ]

> Alright, so USB3 (USB 3.2 specifically) yet to assign then, I guess.

In this I believe @geennaam, that he succeeds also with USB3 drivers. And if not, we can use USB3 with linux - the same way like I do it with my X1000. And USB3.0 is enough for Mirari:

Used chip ( if I read it correctly from photos ) has four USB3.0 ports and is connected to PCIe v2.0 line.
Mirari with CPU T1024 has all SEDRES lines with speed of PCIe v2.0, it means speeds only upto USB 3.0.

Only way howto use USB 3.1 is to have Mirari with T2081 CPU and put USB 3.1(or 3.2) PCIe card to x4 connector.
T2081 CPU in Mirari configuration ( see possible SERDES mapping of CPU ) has one PCIe 3.0 line, connected to this slot. And if there is only one PCIe link, you cannot use USB3.2 speed, which needs two lines. Thus every USB3.2 device will work max in 3.1 mode.


[ Edited by sailor 05.06.2025 - 09:36 ]

>> USB 3.2 specifically

> Used chip [...] has four USB3.0 ports

You're correct. I once knew but unfortunately forgot that "USB 3.2 Gen 1" is just a new fancy name for the old 5 Gbit/s USB 3.0 (and "USB 3.2 Gen 2×1" a new name for 10 Gbit/s USB 3.1, and only "USB 3.2 Gen 2×2" the real 20 Gbit/s USB 3.2). Thanks for reminding me.

> PCIe v2.0 [...] means speeds only upto USB 3.0.

...or USB 3.2 Gen 1 ;-)

Update:

> Complete MorphOS-related entries from the "blog": […]

8th June: "Good old Quake3 ..
On of my old time favorite`s .. the Daddy of all FPS games Quake 3 ! Running on the Mirari board."
https://www.youtube.com/watch?v=TSTczmkqq5w

12th June: "Classics using ScummVM
Classic games running on ScummVM and MorphOS 3.20. Lets see how that turns out."
https://www.youtube.com/watch?v=XekRwvtiVKQ


Edit: added another entry

[ Edited by Andreas_Wolf 13.06.2025 - 18:45 ]

Update:

> Complete MorphOS-related entries from the "blog": […]

13th June: "HD Audio driver for MorphOS
Harald has just finished his first MorphOS driver. It’s for PCIe discrete soundcard complying with the Intel Hdaudio standard. That includes:
Sound Blaster Audigy FX
Sound Blaster Audigy FX V2
CM8828+CM9882A cards"
https://mirari.vitasys.nl/wp-content/uploads/2025/06/HDaudio_Alpha_MOS.jpg

@Andreas_Wolf,

Do you know when the audio part will be supported/managed by the Trion FPGA chip ? I saw/read somewhere that this chip would/should do the job.

Brumiga

> Do you know when the audio part will be supported/managed
> by the Trion FPGA chip ? I saw/read somewhere that this chip
> would/should do the job.

That would be this part of the overall description:
"The T1042 features an I2S interface for direct connection to external audio codecs, while the T208x does not. Therefore, we've implemented the I2S and S/PDIF controllers in the FPGA. This means there's no audio driver readily available for Linux. For OS4 and MorphOS, I have experience writing AHI drivers, so consider this covered."

Sorry, I've no knowledge whether those controllers have already been implemented in the FPGA (and just the drivers missing) or are yet to be implemented (and if so, when).

Quote:

Well the last "news" is that he got the drivers for a fancy surround sound PCIe card working, so I'd say

no

>> I've no knowledge whether those controllers have already
>> been implemented in the FPGA (and just the drivers missing)
>> or are yet to be implemented (and if so, when).

> the last "news" is that he got the drivers for a fancy
> surround sound PCIe card working

Yes, see comment #83 :-) This is likely just a MorphOS port of the author's existing OS4 driver.

> so I'd say no

Strictly speaking, the statement regarding the I²S and S/PDIF controller implementation in the FPGA is written in present perfect tense, rather implying a 'yes'.

The drivers build by @geennaam are the HDaudio drivers.

It’s for PCIe discrete soundcards complying with the Intel Hdaudio standard.
That includes:
Sound Blaster Audigy FX
Sound Blaster Audigy FX V2
CM8828+CM9882A cards

Its not the driver for the onboard FPGA yet.

> The drivers build by @geennaam are the HDaudio drivers. It’s
> for PCIe discrete soundcards complying with the Intel Hdaudio
> standard. [...] Its not the driver for the onboard FPGA yet.

Yes, that's what's already been worked out in comments #82 to #87. Instead, the question (see comment #84) was whether the FPGA-based I²S and S/PDIF controller implementations have already been completed or not. The used language (see quote in comment #85) implies a 'yes', while others (see comment #86) assume a 'no'.

I can say the logic is in the FPGA and a Tone can be send to the Jack and Optical out.
No driver yet.

> I can say the logic is in the FPGA and a Tone
> can be send to the Jack and Optical out.

Thanks for confirmation that both controllers have been implemented already.

I can say the logic is in the FPGA and a Tone can be send to the Jack and Optical out.
No driver yet.

Quote:

Thanks for visiting here and browsing through the feedback from MorphOS users! This is indeed a good sign!

I sincerely hope you read and take to your heart the requests from the MorphOS world about the more powerful CPU option. This is what *we* want!

I am actually looking to buy a board with this CPU for MorphOS use, should you have a working one to provide. (Maybe an optional "Butterfly" Mirari bootloader image in blue? Not very important though...)

Maybe the next run is earmarked only for developers? But I would even buy an early individual board with this CPU, if made available to me. Long holiday coming up. Let me know if you end up with a spare board left over.

Update:

> Complete MorphOS-related entries from the "blog": […]

23rd June: "Testing Harald`s HD Audio driver with the mighty Soundblaster Audigy FX V2"
https://www.youtube.com/watch?v=ClaeQZb5VQ0