Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
63 user(s) are online (34 user(s) are browsing Forums)

Members: 3
Guests: 60

skynet, FlynnTheAvatar, nbache, more...

Headlines

Forum Index


Board index » All Posts (smarkusg)




Re: MPlayer 1.5 released!
Not too shy to talk
Not too shy to talk


@Maijestro

You can try to directly access the ffmpeg libraries from mplayer via ffmpeg:// and add -cache
It seems to me that this will not work anyway.
If you have the ability to use emotion or ffplay use these programs.

I have no way to check because these stream as "pjs" wrote is for my region/country is blocked.

Go to top


Re: Qemu Pegasos II interrupts issue
Not too shy to talk
Not too shy to talk


@balatonQuote:
I can't tell if Linux doesn't do that elsewhere or it does not need to because it can handle shared edge triggered interrupts (probably the latter) but this also does not matter for AmigaOS on an uncommon PPC board what does Linux do on x86.


I checked the stability of the network connection on QEMU (8.1 as I remember correctly ) Linux/debian pegasos2 and A1XE. The kernels were from the 3.x and 4.x series.
I even compiled one myself under A1XE (I wanted to check sm502).
Everything worked properly. Sessions of 2h using audio stream and running mplayer in the background.
Based on this, I can say that QEMU emulation with pegasos2 and A1Xe machines using orginal uboot/firmware worked.
The AOS4 system using the original uboot/firmware did not....

edit:
I found a post even on the forum

https://www.amigans.net/modules/newbb/ ... id=143474#forumpost143474

Then I also still had some fun with those Linux on Peg and A1

Go to top


Re: Cannon fodder open source
Not too shy to talk
Not too shy to talk


@AmigaOldskooler

Thanks.
I hope you will have fun ..as I did. I discovered over the years that this game is not as easy as it used to be

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


@balaton

Quote:
I'd still need the lspci or showconfig output from a real Sam460 as I've asked above to confirm it's the right fix but seems to resolve the problem at least for now


I don't know too many people who have a real sam460, but if no one answers, I'll try to ask around and let you know @.

Go to top


Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


@balaton

I saw that you posted a patch for "ppc440_pcix.c" yesterday.
I checked quickly Qemu with sam460.I plugged in a disk image with SFS initializes and works.

I have SFS with ES - version 1.293
Qemu version 9 RC1
Thank you

Resized Image

Go to top


Re: MPlayer 1.5 released!
Not too shy to talk
Not too shy to talk


@sailor
Maybe try some mp3 encoder , lame for starters.
A few months ago I tried to do something with the ffmpeg compilation from this guide
that you provided in that https://www.amigans.net/modules/newbb/ ... id=147361#forumpost147361
But without the physical hardware, it's like a telephone consultation with an ophthalmologist I see nothing he sees nothing and you get a prescription sore throat even though you need glasses...

Go to top


Re: Cannon fodder open source
Not too shy to talk
Not too shy to talk


@LiveForIt
I only corrected a few bugs and moved to the new version 1.8. salass00 did most of the work. He left out a few bugs.
Ports are ports... anyway, most credit goes to the authors of the original versions.

Go to top


Re: Cannon fodder open source
Not too shy to talk
Not too shy to talk


Hi

AmiWest 2024's theme of "Get your game on!". Games were the backbone of the Amiga platform.
There was no native Cannon Fodder after AOS4. With help came an open port of Open fodder.... and @salass00's work on the previous port.
Plus the help of @Javier and @Samir
Thanks guys!!!

https://github.com/smarkusg/openfodder/releases/tag/31032024

If anyone found any bugs before publishing on os4depot thanks in advance for your help

* full version of Cannon Fodder is required to make the port fully functional

version with full installation of the original cannon fodder





Edited by smarkusg on 2024/3/31 22:22:09
Go to top


Re: mplayer and VA.library
Not too shy to talk
Not too shy to talk


Hi

In recent months, a new version of mplayer 1.5 has been released, building on the work of previous releases of this program under AOS4.
New things have been added and some things have been improved. From the beginning, the idea was that mplayer could also use the va-api video output.
For a few months now, we have been testing a solution based on the mplayer port under Linux, where there is a vaapi video output.
To make it work, we need to undo some changes in the ffmpeg code and add the code to mplayer. Changes to ffmpeg and mplayer alone will not make it work. It was also necessary to adapt the va-api implementation to work with the existing va-api version under AOS4.

Lastly, mplayer and ffmpeg itself appears to work under AOS4. The only problem is the video output. The video output in mplayer itself is on X11.
For testing, a simple output was made to simulate operation under AOS4. What is missing is for this output to be rewritten/re-written in order to lastdznie confirm the operation.
Here is my request, is there any person who could help with this ?


Example log from mplayer vaapi output under AOS4 where you can see

MPlayer -vo vaapi -ao null PRUEBAS:Big_Buck_Bunny_1080_10s_30MB.mp4 
MPlayer SVN
-r38448-snapshot (C2000-2024 MPlayer Team

Playing PRUEBAS
:Big_Buck_Bunny_1080_10s_30MB.mp4.
libavformat version 60.16.100 (internal)
libavformat file format detected.
[
lavfstream 0video (h264), -vid 0
VIDEO
:  [H264]  1920x1080  24bpp  30.000 fps  24559.9 kbps (2998.0 kbyte/s)
[
vaapiinitialised (API version 1.5).
==========================================================================
Opening video decoder: [ffmpegFFmpeg's libavcodec codec family
libavcodec version 60.31.102 (internal)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
major_brand: isom
minor_version: 512
compatible_brands: isomiso2avc1mp41
title: Big Buck Bunny, Sunflower version
artist: Blender Foundation 2008, Janus Bager Kristensen 2013
composer: Sacha Goedegebure
encoder: Lavf57.63.100
comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net
genre: Animation
Load subtitles in PRUEBAS:
Audio: no sound
Starting playback...
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [vaapi] 1920x1080 => 1920x1080 H.264 VAAPI acceleration 
[vaapi] hardware supports codec: format H.264 VAAPI acceleration -> VAProfile 7.
[vaapi] context initialised: config 0x1, context 0x14.

[h264 @ 0x436e86a8]Using deprecated struct vaapi_context in decode.
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [vaapi] 1920x1080 => 1920x1080 H.264 VAAPI acceleration 
[vaapi] OSD drawing is not supported.
--


For comparison, here is the log from mplayer vaapi under Linux

MPlayer SVN-r38423-snapshot-12 (C2000-2023 MPlayer Team
do_connect
could not connect to socket
connect
No such file or directory
Failed to open LIRC support
You will not be able to use your remote control.

Playing /home/markus/Wideo/2020/2020-03-04_09-49-20.mp4.
libavformat version 60.3.100 (internal)
libavformat file format detected.
[
mov,mp4,m4a,3gp,3g2,mj2 0x556a3bdac2c0]Protocol name not providedcannot determine if input is local or a network protocolbuffers and access patterns cannot be configured optimally without knowing the protocol
[lavfstream 0video (h264), -vid 0
[lavfstream 1audio (aac), -aid 0, -alang eng
VIDEO
:  [H264]  1280x720  24bpp  45000.000 fps  14004.9 kbps (1709.6 kbyte/s)
libva infoVA-API version 1.14.0
libva info
Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info
Found init function __vaDriverInit_1_6
libva info
va_openDriver() returns 0
[vaapiinitialised (API version 1.14).
==========================================================================
Opening video decoder: [ffmpegFFmpeg's libavcodec codec family
libavcodec version 60.3.100 (internal)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: isommp42
 creation_time: 2020-03-04T08:49:20.000000Z
 location: +50.3001+018.8347/
 location-eng: +50.3001+018.8347/
 com.android.version: 7.1.2
Load subtitles in /home/markus/Wideo/2020/
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, floatle, 96.0 kbit/3.12% (ratio: 12000->384000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
couldn'
t open play streamDevice or resource busy
ao2
can't open sndio
[AO OSS] audio_setup: Can'
t open audio device /dev/dspNo such file or directory
AO
: [alsa48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.78:prescaling to correct movie aspect.
VO: [vaapi1280x720 => 1280x720 H.264 VAAPI acceleration 
[vaapihardware supports codecformat H.264 VAAPI acceleration -> VAProfile 7.
[vaapicontext initialisedconfig 0x1000000context 0x2000000.

[
h264 0x556a3bdd1de0]Using deprecated struct vaapi_context in decode.
Movie-Aspect is 1.78:prescaling to correct movie aspect.
VO: [vaapi1280x720 => 1280x720 H.264 VAAPI acceleration 
[vaapiOSD drawing is not supported.



thank you in advance for your help

Go to top


Re: Hi New Member Here
Not too shy to talk
Not too shy to talk


I hope I am not too late ...
A very warm welcome to you !

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@balaton

Quote:
Maybe the AmigaOS lsi scsi driver is not init'ing/using these cards properly as the Linux drivers do or does something that works on real card >but QEMU is not emulating as the Linux and other OS drivers don't do that?


I would be more in favour of saying that lsi53c810 under qemu was written for specific machines.
It was certainly not done on purpose, but some of the code may have been omitted because the author decided it was not used/needed for a particular system and driver- and rightly so
Quote:
>The assert means that the condition should be true. If it's not then there's a problem somewhere, either the guest sent some unexpected commands >or there's a problem with emulation. Commenting the assert won't help as it's there to make sure it won't break later.

I wrote with exclamation marks that it was a test and I would never leave it like that in my life The test was successful because it showed that AOS is able to work with its lsi53c810 driver, making the correct drive data available.

Unfortunately, I am unable to debug this problem. I hope you find a solution

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@balaton
Quote:
you could do by replacing nonvolatile.library to use nvram/nvrom.txt as @joerg said


After reading lsi53c8xx_dev.doc I changed the card identification in the qemu sources.
In the documentation it even says that the cart "0x0001" should work but requires lsi53c8xx_override 0001
I have not touched anything in the system. I especially didn't want to change anything in the CD.
I wanted sam460 to behave as if it already had the correct card inserted at the start.

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@joerg
I did as you wrote.
QEMU Sam460 and Pegasos(pegasos.rom) when trying to initialise after loading the kernel and AOS4 modules from the cd it crashes.
--
 
in lsi_do_command(LSIState *s)
 ..
 
assert(s->current == NULL
 --

EMU launch command line Sam460
-machine sam460ex -rtc base=localtime -drive if=none,id=cd,file=Sam460InstallCD-53.58.iso,format=raw  -device ide-cd,drive=cd,bus=ide.1  -device lsi53c810,id=scsi0 -device scsi-hd,drive=scsi-drive,bus=scsi0.0,channel=0,scsi-id=0,lun=-drive file=lol.hdf,if=none,id=scsi-drive,if=none,format=raw

!!!Just for a test I did a rem "assert"!!!
sam460 sees the card and the disk. The problem is on the QEMU side. Most people from what I have seen are tuning the lsi53c810 to run linux via QEMU. It is possible that no one has tried this on AOS before and it doesn't work and the lsi53c810 itself in QEMU needs to be checked.

Resized Image

Pegasos bboot hangs on something like this and booting AOS4 (debug) is stopped
--
[
peg2ide/init_portPort 1 task started
[peg2ide/dev_initAll done
lsi53c8xx
.device 53.22 (28.6.2017)
[
lsi53c8xx/dev_initFound chip #0
[lsi53c8xx/ide_initchipWaiting for devices to spin up..
[
lsi53c8xx/init_port] ---> Port 0
[lsi53c8xx/scsi_scanScanning SCSI bus...
--

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@joerg

Thank you very much for your help !!!
I will check in the evening when I have more time and let you know SFS on lsi53c810 in QEMU/sam460 works.

EDIT:
On qemu sam460 i have crush.... looks like some kind of problem with qemu
Assertion failed: (s->current == NULL), function lsi_do_command, file lsi53c895a.c, line 866.
zsh: abort /tmp/z2/bin/qemu-system-ppc -machine sam460ex -rtc base=localtime -drive


Edited by smarkusg on 2024/3/1 23:14:11
Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@balaton

SCSI (LSI/NCR/SYM 53c8xx) works but AOS4 (lsi53c8xx.device.kmod) doesn't seem to support this model of card is in QEMU.
uboot sees the card and the board but, it even loads the system boot .... and that is the end.



edit:
Here the command line
-machine pegasos2 -rtc base=localtime -m 1024 -bios ./pegasos2.rom -serial stdio   -vga none  -device sm501 -device lsi53c810,multifunction=on,id=scsi -drive file=Pegasos2InstallCD-53.54.iso,id=scsi_iso,if=none -device scsi-cd,drive=scsi_iso


I checked on pegasos with rom and bboot because I have this emulation currently available


Edited by smarkusg on 2024/3/1 14:58:46
Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@balaton

Quote:
0x1302 not 0x1320.


0x1302 not 0x1320 - yes meant that value what you gave. I misspelled the values . Thanks for the explanation

qemu 8.1 also sfs not working

Resized Image

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@joerg @balaton

One more question
in Linux kernel regarding pvr for 460ex rev. B is set 0x13202004
i checked out of curiosity setting such value in qemu and AOS got up.
I also checked for certainty by setting a random value and AOS did not boot - so I set everything right. uboot was also initialized without any problem

As I understood the pvr mask 0x1320 applies to 4xx series porceosrs.
This means that for AOS it does not matter pvr only in specific programs that try to check it ?
thank you for your reply

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@balaton

Not working
here you have a screen - qemu 8.1.5
SFS with ES does not initiate

Resized Image

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@joerg

Thank you for your information.
I may not agree with it, but you are the creator of SFS and owner of the rights to it, and I accept what you wrote and your decision.
I am grateful that you wrote it directly. There is also a version of SFS which you have made available on aminet/os4depot which can be used.

I also hope that all the things you described will eventually end in a happy ending for everyone.

Go to top


Re: Sam460 which file systems can be used
Not too shy to talk
Not too shy to talk


@joerg

If I understood correctly SFS could be run on the specific machines that AmigaOS 4 was running on.
I came across a topic on another forum where one of the new x5000 users has to edit the AOS4FE install CD to add SFS with ES to make it work for him.
JXFS has no restrictions and no assignment to the specific processor it can run on. This is also your file system.
Would it not be possible to remove this from SFS and make versions available as part of an ES update?
You are the rights holder for SFS , you have the source code.... I just don't know if you want to do this.

Thanks for the information regarding the NGFS author.
I will try to ask him somehow about the possibility of testing NGFS.
However, there may be a problem with this
I came across a thread in the hyperion forum about NGFS
The older version was only temporary for the X5000 as an alternative to SFS.
The second version as an update is available for X5000 and possibly A1222 owners.
It will not work on other machines.
NGFS is supposed to be available for other machines as AmigaOS 4.2.

If NGFS is again assigned to specific processors and machines in a few years, the problem will return like with SFS when a new machine or emulator is created.
Unless AmigaOS 4.2 is released or the restrictions are removed.

If I have misunderstood something or I am wrong about something please correct me

Go to top



TopTop
(1) 2 3 4 ... 13 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project