Would be awesome if IntuitionBase got back in action again! Have used that site a lot in the past, especially for information on the early A1's and Sam's.
I was wondering who here is planning to get the new A1222 Plus?
I've sold my Sam Flex, so I'm ready to get a new computer. Not on the original early adopter list though, but hopefully it all goes well.
I have a graphics card, Radeon R7 240, which I hope will work, as well as a case and SSD's, but also considering getting a pre-built system if one of the shops makes something cool (and small).
The script supports choosing AmigaAmp, ffplay and Emotion to play streams. ffplay displays realtime graphics while playing. It also support saving streams to a file.
Thanks for the tip, I'll try it right away. It's a pity that TuneNet doesn't provide this support, nothing against AmigaAmp, but TuneNet is an independent AmigaOs4.1 development and also a bit more resource-friendly compared to AmigaAmp.
Finally I know what FFPlay is good for The script really works very well, you should add this function MediaVault. If I had not asked, I would not know that such a thing is possible. Fantastic....I love it.
@walkero
Quote:
That solution is a "temporary" one, for the last 2 years :D I still want to make a proper configuration window where user can set things like that.
Such support would be very nice for the future, but don't pressure yourself. MediaVault works very well without this feature.
Edited by Maijestro on 2023/7/27 10:26:44 Edited by Maijestro on 2023/7/27 10:38:00 Edited by Maijestro on 2023/7/27 21:00:57
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Is there a possibility to use MediaVoult together with TuneNet 2.18 (Enhancer 2.2 ) for radio streams. ?
When MediaVault was first released I looked at adding TuneNet support to my script but TuneNet only supports streaming of mp3 streams and does not support aac streams. For this reason it is not a good player to use, so I decided not to support it.
The script supports choosing AmigaAmp, ffplay and Emotion to play streams. ffplay displays realtime graphics while playing. It also support saving streams to a file.
@afxgroup You could use assembler, or asm inline(), code using the mffs/mtfsf instructions instead if you only need it for the current task, but using OS functions like (Read|Write)TaskContext() instead is better.
@joerg Question is : can we, without patching the kernel or patching the firmware, flatten the list from Balaton's BBoot, so, things will have no needs to be scanned recursively by kernel ? right, you already answer on.
At least, that probably the next step need to be done, to flatten the list, and see how kernel will eat that. Only need to ask Balaton to find time for it :)
And, all other AmigaOS machines do see bridges and Radeons in it, with the same version of kernels, and even on the same "32 bit only" kernels.
Wrong, all AmigaOS 4.x kernels are very different and only include the required code for the specific hardware (only code for the CPUs supported on that hardware, motherboard specific hardware, etc.), and more important: AmigaOS 4.x kernels depend on the firmware, MorphOS may not (or much less).
Quote:
This is limitation only of pegasos2 kernel and its PCI parsing code.
Maybe, but since there is no bridge, and as result no PCI tree but just a flat PCI list in a Pegasos2, unlike on all other systems, support for it in the Pegasos2 kernel (or more specifically the conversion of the OpenFirmware PCI list to the PCI tree required by the kernel) wasn't required... If there is only a single MorphOS kernel for all systems, unlike the different AmigaOS 4.x kernels for the different systems, it has to include support for bridges, for example for the Pegasos1.
Quote:
It may be simple assume that on pegasos2 only PCI0/1 lines, with BUS 0 everywhere and that all.
Yes, because the Pegasos2 hardware only has 2 busses, no bridges.
Maybe BBoot can convert the OpenFirmware PCI tree to a simple list supported by the Pegasos2 kernel.
I need to get (and set) the floating-point exception mode. I’ve seen that in exec/interrupts.h there are:
float64 fpr[32]; /* Floating point registers */
uint64 fpscr; /* Floating point control and status register */
That should be get and set via ReadTaskContext/WriteTaskContext. Now my question is. Is the only way to get that register? Is it the correct way? Is there a #define to get only the bit I need?
@joerg Not sure that there are any "Special support for bridges" anywhere, be it morphos or os4, as bridge is simple "PCI" from hardware point of view. PCI which have just different BUSs than the main (0) one.
And, all other AmigaOS machines do see bridges and Radeons in it, with the same version of kernels, and even on the same "32 bit only" kernels for machines such as XE, mA1 and sam440. This is limitation only of pegasos2 kernel and its PCI parsing code. Probably pegasos2's PCI scan code of OS4s kernel simple assume that on pegasos2 only PCI0/1 lines, with BUS 0 everywhere and that all.
And in firmware we do have RadeonHD visibly as i show before, just it's sitting on other BUS, and amigaos4 kernel fail to see that. But firmware definitely see it, and that probably what Morphos kernel get, just morphos's kernel do have correct parsing of BUSs, while OS4 pegasos2's (and only pegasos2) kernel don't do so.
@kas1e Maybe MorphOS is scanning the PCI bus(ses) and builds the PCI tree, incl. support for bridges, itself. AmigaOS doesn't, it simply uses whatever it gets from the firmware.
I don't know if the problem is the Pegasos2 SmartFirmware doing something different than U-Boot, or the Pegasos2 kernel not supporting bridges/trees because, unlike for example AmigaOne SE/XE/µA1 and Sam4x0, the Pegasos2 hardware doesn't include any PCI-to-PCI bridges and therefore including support for it wasn't required.
It looks like not pegasos2 smartfirmware : Check 2 previous posts of me with screenshot and info from morphos's boot. It explains everything probably, but bottom line is : morphos kernel do scan other BUSs than 0 on PCI0/1 lines and so find RadeonHD in bridge, while, the OS4 kernel seems didn't scan any other BUS than 0 on the PCI0/1 lines, so have flat list => fail to find RadeonHD which on the BUS1 of the PCI0 line of bridge.
On the screenshots you linked in the Sailor's article, it also shows that RadeonHD sits on the BUS2, of some PCI line. So it can one more time confirm that pegasos2 kernel do have issues with scanning any BUS except 0.
Sure, at the moment we don't know for sure on GPU passthrough if the register addresses (I think that's what we're talking about, I know which addresses I mean in the output / code anyway) should be left undefined as they appear to be on real Pegasos2, whether the IRQ's should be mapped when they are unassigned by firmware and so on.
Dunno if you check thread about real pegasos2-with-bridge, but i find out, that morphos kernel, do see both bridge, and RadeonHD in, and, RadeonHD in both audio and video parts sitting on IRQ#9, too. Even being on BUS#1 of PCI0 line.
At least in Ranger on Peg2 i do have many labels as bridges (which can be just name-labeling of course). That how it looks like:
Your Ranger PCI result, as well as any other Pegasos2 ones I've seen so far, no matter if real hardware or QEmu, are just a simple list. Check for example https://www.amigaportal.cz/filedata/fetch?id=159426&d=1669032514 how it has to look like on a system with bridge support: It's a tree, not just a flat list. I don't know if the problem is the Pegasos2 SmartFirmware doing something different than U-Boot, or the Pegasos2 kernel not supporting bridges/trees because, unlike for example AmigaOne SE/XE/µA1 and Sam4x0, the Pegasos2 hardware doesn't include any PCI-to-PCI bridges and therefore including support for it wasn't required.