Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
56 user(s) are online (44 user(s) are browsing Forums)

Members: 1
Guests: 55

skynet, more...

Support us!

Headlines

 
  Register To Post  

« 1 ... 53 54 55 (56) 57 58 59 ... 75 »
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@balatonQuote:
balaton wrote:@Maijestro
Quote:
At least the numbers show that it is different, shouldn't it always be the same?

It should be about the same if the same thing has been run in the guest when you collect these statistics so if you always do the same and get the stats at the same point then difference shows something if they are from runs where different things happened since starting QEMU then they don't show anything.

PPC interrupt 8 is syscall when guest executes sc instruction which is done when something is calling AmigaOS services so maybe something is running in guest that does more stuff sometimes? Is there some task manager where you can check what task is using CPU time and compare that?


Thanks for the explanation, the test on both sessions always runs the same. I start Qemu Boote AmigaOs4.1 until Workbench is available and then I start Quake Timedemo1 and look at the benchmarks. Good session 32 FPS, bad session 16 FPS. So I can also determine which session with Qemu is bad and which is good. So I could assign IRQ and JIT info to the respective sessions.

A reliable CPU task manager under AmigaOs4.1 does not exist at the moment, but should not be necessary since both Qemu sessions run exactly the same.In the test nothing else is started like AmigaOs4.1 up to the Workbench and then directly Quake Timedemo1.

Edit: Believe me, I have tested this countless times. It's like when I noticed that the sound output under MacOs with Qemu and AmigaOs4.1 runs too fast, this error was also hard to reproduce until I recorded it on my handy

In a bad Qemu session I also notice that I can stream YouTube videos in 720p with MPlayer, but the FPS numbers collapse and the video plays slower, as if I had a good session with Qemu where Quake with 32 FP benchmark is available.

Since no one has tested it further, I'm not sure if it's only a MacOs problem. Or if it is due to the Mac M1 CPU which makes it sometimes faster and sometimes slower.Or maybe it is a problem of Qemu.


Edited by Maijestro on 2023/7/25 19:31:55
Edited by Maijestro on 2023/7/25 19:36:23
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@Maijestro
Quote:
A reliable CPU task manager under AmigaOs4.1 does not exist at the moment
If all you need is something like top on Unix my "top" and Capehill's "tequila" should be reliable enough.

Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@joergQuote:
joerg wrote:@Maijestro
Quote:
A reliable CPU task manager under AmigaOs4.1 does not exist at the moment
If all you need is something like top on Unix my "top" and Capehill's "tequila" should be reliable enough.


"Tequila" I have already used under AmigaOs4.1 it works well, but it is not perfect, but it does not have to be, because it is still being worked on.

"Top" I have not yet tried under AmigaOs4.1, thanks for the tip.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


See User information
@joerg
The millions of sc exceptions do come from somwhere so even if no apps use this somthing in the kernel definitely does and not even rarely.

Top would probably help if it lists cumulative CPU time from boot like under Unix.

Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@balaton
Quote:
Top would probably help if it lists cumulative CPU time from boot like under Unix.
My "top" and "Tequila" can only display CPU times/task after they were started.
The kernel records per task CPU usage times as well, but not on all systems/CPUs, some CPUs don't include the required hardware for it. I did implement a "top" version using the kernel stats instead of calculating it itself, but since it couldn't work on all CPUs I never released it.
Additionally to per task CPU usage my "top" tool displays the number of IExec->SuperState() calls per second, i.e. the number of switches from user to supervisor mode and back per second, and if that's a very high number there is definitely a problem (maybe not QEmu related, can be kernel or AmigaOS hardware drivers, or even user software, related as well).

Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


See User information
@joerg

That would be enough as one can start top at boot from WBStartup or startup-sequence or similar then leave it running to collect CPU time from boot. Then hopefully running the same things might show some difference to find which task may have something to do with this. If there's no difference then it's probably not a user program but something lower level. Measuring user/supervisor transitions could be checked if it correlates with syscall exceptions in info irq too.

Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Quite a regular
Quite a regular


See User information
@balaton

qemu (build 8.1.0-rc1)

I probably missed the last steps written in the post
or is it a mistake

because if I choose:
-cpu 7447
or
-cpu 750cxe

the speed is always at 999mhz for both CPUs chosen

while instead before with

-cpu 7447

I had the CPU at 1.5ghz:
https://ibb.co/wpxZc2Q

I noticed it now

it is now -cpu 7447 it looks like this (999mhz):
https://ibb.co/YNJwPm8

it is due to this:
qemu-system-ppc -M pegasos2 -cpu 7447 -accel tcg -kernel /home/white/Download/bboot-0.4/bboot -initrd /home/white/Download/Kickstart.zip


Because if i use the old command that use pegasos2.rom
i get the cpu at 1.5ghz


Edited by white on 2023/7/26 3:20:55
Edited by white on 2023/7/26 3:44:34
Edited by white on 2023/7/26 4:05:38
Edited by white on 2023/7/26 4:24:37
Edited by white on 2023/7/26 5:45:45
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@whiteQuote:
white wrote:@balaton
it is now -cpu 7447 it looks like this (999mhz):


I've noticed that too, but it doesn't change the speed, on the contrary it shows things a bit more accurately.

The real Pegasos 2 G4 is clocked with 1Ghz (not overclocked) because Qemu emulates a Pegasos 2 it is displayed correctly with Ranger under AmigaOs4.1.

http://www.tt-room.de/Pegasos2.html

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just popping in
Just popping in


See User information
@joergQuote:

Additionally to per task CPU usage my "top" tool displays the number of IExec->SuperState() calls per second, i.e. the number of switches from user to supervisor mode and back per second, and if that's a very high number there is definitely a problem (maybe not QEmu related, can be kernel or AmigaOS hardware drivers, or even user software, related as well).


There are cases where you can get unexpected high number of taskswatches in AOS or clones even if there's no problem (assuming problem = bug). For example when multiple tasks use the same semaphore a lot (for example it could be some memory allocation lock, or something gfx related like OwnBlitter()) and ~"bad luck" causes the semaphore to get in what I call "pingpong state".

If you ran a test program like this:

for(;;)
{
   
ObtainSem sem;
   
dosomething();
   print 
taskname;
   
ReleaseSem sem;
}


two times, then you would expect/hope to get output like this:

task1
task1
task1
task1
...
task2
task2
task2
...


But sooner or later it will get into ping pong state and then output will be:

task1
task2
task1
task2
task1
task2
task1
task2
...


Happens when one of the test programs gets preempted while holding the semaphore. From then one at every ReleaseSem() time there will always be the other task in the wait queue causing switch to this other task (when thistask calls ObtainSem()).


Edited by Georg on 2023/7/26 14:13:39
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


See User information
I managed to build bboot on OS4 last night (in Qemu on my MacBook). I had 3 issues with the code compiling but they were all sovled in the end. I don't know if it's worth listing them because I doubt many people are likely to be building it on OS4. Just try as I might I could not easily get a cross-compiler set up.

The whole reason I'm even building it at all is so that I can at least attempt to try different things out when things don't work. Hopefully that's helpful!

Unfortunately my time continues to be limited this week and there will be no time at all soon due to vacation. But I should be good for tonight to at least check that the bboot that I built runs.


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@MartinWQuote:

The whole reason I'm even building it at all is so that I can at least attempt to try different things out when things don't work. Hopefully that's helpful!


I don't understand what this should be good for, but everything that brings Qemu and AmigaOs4.1 further in development should be good in my opinion.

Maybe you can give some details what exactly you have in mind to understand what it can be useful for.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


See User information
@Maijestro

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.

I could keep coming back here, posting log output and then Balaton can make a minor change with "try this", or I could try the changes myself first. If I understand where to make the change of course. It doesn't matter if I do it exactly how Balaton would do it, or not, at least then I can say "well, I tried x and y but it didn't help, here are the logs". Etc.

Unless I'm wrong and we've exhausted all options but I don't think that is the case. I also have access to HD5450, RX550 and RX580.

One thing I will say is that I've switched to a different PC and the PCIe slots are a bit blocked by the CPU cooler so I'm a bit limited now. "New" (actually older) PC is Intel 6700K based but actually, that has a faster single core frequency than my Ryzen system so it's better for Qemu really. The IOMMU isolation is not as good however and I think it might be causing me problems.


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@MartinW

Quote:
MartinW wrote:@Maijestro

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.

I could keep coming back here, posting log output and then Balaton can make a minor change with "try this", or I could try the changes myself first. If I understand where to make the change of course. It doesn't matter if I do it exactly how Balaton would do it, or not, at least then I can say "well, I tried x and y but it didn't help, here are the logs". Etc.

Unless I'm wrong and we've exhausted all options but I don't think that is the case. I also have access to HD5450, RX550 and RX580.

One thing I will say is that I've switched to a different PC and the PCIe slots are a bit blocked by the CPU cooler so I'm a bit limited now. "New" (actually older) PC is Intel 6700K based but actually, that has a faster single core frequency than my Ryzen system so it's better for Qemu really. The IOMMU isolation is not as good however and I think it might be causing me problems.


I keep my fingers crossed that they get it running decently.

Since no Amiga NG x5000 comes into question for me (too expensive) and for that AmigaOs4.1 is still too limited at the moment, I would prefer such a solution on current PC hardware.

Otherwise I'm waiting for a Qemu Pegasos 2 GFX driver for the emulated GFX, because I've also played with the idea to buy the new MacStudio with M2 Max or M2 Ultra, on such a hardware AmigaOs4.1 would probably be even faster as it already is.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@Maijestro
Quote:
Since no Amiga NG x5000 comes into question for me (too expensive)
...
I've also played with the idea to buy the new MacStudio with M2 Max or M2 Ultra, on such a hardware AmigaOs4.1 would probably be even faster as it already is.
Doesn't make sense if you want to use it mainly for AmigaOS 4.1 emulation, the M2 Max costs about as much as a X5000, the M2 Ultra twice as much.

Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@joergQuote:
joerg wrote:@Maijestro
Quote:
Since no Amiga NG x5000 comes into question for me (too expensive)
...
I've also played with the idea to buy the new MacStudio with M2 Max or M2 Ultra, on such a hardware AmigaOs4.1 would probably be even faster as it already is.
Doesn't make sense if you want to use it mainly for AmigaOS 4.1 emulation, the M2 Max costs about as much as a X5000, the M2 Ultra twice as much.


But it makes sense, the MacStudio, I use mainly for working with MacOs it is my main system I use. AmigaOs4.1 is currently used as a 2 system.

I also don't have room for additional hardware, so I went for something very powerful that takes up as little space as possible. I don't like the clunky computers.

I already had an AmigaOneXE 20 years ago, but for the fact that I boot AmigaOs4.1 only 2-3 times a day, this space would be wasted for me and it would be a pity for the hardware that then just stands around and is not used.

2 systems on one machine would be perfect, of course. AmigaOs4.1 did not run much better on real hardware than under Qemu, and I am a bit suspicious if things have improved. At that time AmigaOs4 was still pre-release.

The NG Amiga x5000 was released in 2016 has 2 cores, which unfortunately is not supported by the AmigaOs4.1 kernel until today. For God's sake I don't want to talk bad, but the further development of AmigaOs4.1 is unfortunately very slow, as much as I love this system otherwise I wouldn't have bothered with it again after years.

I do not want to go into this topic any further either. AmigaOs4.1 is a great system for me and with a x 5000 you will of course have much more fun than with Qemu and AmigaOs4.1.


Edited by Maijestro on 2023/7/26 18:58:20
Edited by Maijestro on 2023/7/26 19:02:58
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


See User information
Unfortunately, at the moment Qemu is never going to work properly on my Mac Mini. The sound doesn't work with my USB Audi Interface and I don't want to route all the sound through the Mini's internal speaker to get round it. This is kind of a known thing. At one point Qemu couldn't even start a linux VM as it would kernel panic and shut off prior to login. Switch off the audio interface and it was OK. This was "UTM" but I believe it was Qemu behind the scenes.

Qemu is fine on my laptop for a bit of tinkering about but the GPU is the sticking factor there. And not the resolution, 1440x900(x2) is the native resolution of the screen but developing games is a non-starter.

So, the GPU passthrough stuff is a bit of fun to play about with but that will reach a pause when my X5000 arrives as I'll need the case the "passthrough machine" is in, not to mention the GPU.


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@MartinWQuote:

So, the GPU passthrough stuff is a bit of fun to play about with but that will reach a pause when my X5000 arrives as I'll need the case the "passthrough machine" is in, not to mention the GPU.


To be honest I don't think much of this GPU passthrough story under Qemu. Because this setup is very heavy and not user friendly. A suitable driver for this emulation would be far more effective.

However, the information was very helpful for real Pegasos 2 hardware where it might be possible in the future to use RadeonHD and RX cards across bridges, even if this hardware is very old they would be up to date.

You contributed a lot and did it really well and I know how much time testing alone takes, I've been dealing with the Qemu emulation and AmigaOs4.1 for a year when I started testing Qemu was on mine Machine completely unusable. No sound, no network, broken graphics etc.

Congratulations on the purchase of the x5000, maybe you will also develop some software for AmigaOs4.1 in the future. I can well imagine that with them....

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


See User information
@Maijestro

Quote:
To be honest I don't think much of this GPU passthrough story under Qemu. Because this setup is very heavy and not user friendly. A suitable driver for this emulation would be far more effective


When it works, it should work very well. I used to run all my Windows games in a Windows VM using GPU (and USB) passthrough. Ideally there will need to be ways to switch monitor inputs and keyboard / mouse (or pass them through too). It's all possible but obviously needs extra work.

Of course, I agree that OS4 drivers is also a nice way to go and I'd see the benefit there too on my laptop.

Quote:
maybe you will also develop some software for AmigaOs4.1 in the future


I am part of a team that has created a sort of game engine but it was never completed. I intend to look to se if it could be brought to OS4 and maybe the goals re-aligned a bit so it could be completed. No public info yet and potentially may never be.


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Just can't stay away
Just can't stay away


See User information
@MartinW

You're a nice guy, I'll keep an eye on you

As soon as your x5000 has arrived and you have set up an AmigaOs4.1 system and all that entails I would appreciate if you could give some feedback on how things are going with this machine, it would be interesting to know.

MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne A1222plus AmigaOs4.1 FE
Go to top
Re: What the fastest possible x64 emulation way of OS4 today ?
Not too shy to talk
Not too shy to talk


See User information
@balaton

I've spent some time tonight looking at PCI Passthrough for 5450 GFX. BBoot 0.4, Qemu Master. I can't get it to work. Boot hangs before workbench even starts to load and leaves me with a grey sceen with the text "Workbench" in the top left in an old PAL-like resolution.

Hopefully I've not omitted any info. Let me know if I have.

I've compared bboot output from using pegasos rom with my manual forth patch:

BBoot 0.4 (24.7.2023)
/
pci@80000000io fe000000/10000 mem 80000000/40000000
/pci@80000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 0
/pci@80000000/ethernet:    0:1.0     10ec:8139 20000 813910ec 0109 0
  1000810        0 fe001100         0      100  
00001101
  2000814        0 80000000         0      100  
80000000
  2000830        0 80040000         0    40000  
80040000
/pci@80000000/display:    0:2.0     1234:1111 38000 11111234 0009 0
 42001010        0 81000000         0  1000000  
81000008
  2001018        0 80001000         0     1000  
80001000
/pci@80000000/display:    0:3.0     1002:68e1 30000 68e11002 0109 0
 42001810        0 90000000         0 10000000  
9000000c
  2001818        0 80020000         0    20000  
80020004
  1001820        0 fe001200         0      100  
00001201
  2001830        0 80080000         0    20000  
80080000
/pci@80000000/isa:    0:c.0     1106:8231 60100 82311106 0000 f
/pci@80000000/ide:    0:c.1     1106:0571 1018f 05711106 010e 87
  1006110        0 fe001000         0        8  
00001001
  1006114        0 fe00100c         0        4  
0000100d
  1006118        0 fe001010         0        8  
00001011
  100611c        0 fe00101c         0        4  
0000101d
  1006120        0 fe001020         0       10  
00001021
/pci@80000000/usb:    0:c.2     1106:3038 c0300 30381106 0409 7
  1006220        0 fe001040         0       20  
00001041
/pci@80000000/usb:    0:c.3     1106:3038 c0300 30381106 0409 7
  1006320        0 fe001060         0       20  
00001061
/pci@80000000/other:    0:c.4     1106:8235 68000 82351106 0009 0
/pci@80000000/sound:    0:c.5     1106:3058 40100 30581106 0309 4
  1006510        0 fe001300         0      100  
00001301
  1006514        0 fe001030         0        4  
00001031
  1006518        0 fe001034         0        4  
00001035
/pci@80000000/pci1106,3068:    0:c.6     1106:3068 78000 30681106 0309 30
/pci@c0000000io f8000000/10000 mem c0000000/20000000
/pci@c0000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 7


To the same through bboot:

BBoot 0.4 (24.7.2023)
/
pci@80000000io fe000000/10000 mem 80000000/40000000
/pci@80000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 7
Added assigned
-addresses
/pci@80000000/pci10ec,8139:    0:1.0     10ec:8139 20000 813910ec 0100 0
Fixed ROM BAR
Added assigned
-addressesset interrupt 0109
  
1000810        0 fe001200         0      100  00000001 00001201
  2000814        0 80000000         0      100  
00000000 80000000
  2000830        0 80040000         0    40000  
00000000 80040000
/pci@80000000/pci1234,1111:    0:2.0     1234:1111 38000 11111234 0000 0
Added assigned
-addressesset interrupt 0009
 
42001010        0 81000000         0  1000000  | 00000008 ! 81000008
  2001018        0 82000000         0     1000  
00000000 82000000
/pci@80000000/pci1002,68e1:    0:3.0     1002:68e1 30000 68e11002 01ff 0
Fixed ROM BAR
Added assigned
-addressesset interrupt 0109
 
42001810        0 90000000         0 10000000  0000000c 9000000c
  2001818        0 a0000000         0    20000  
00000004 a0000004
  1001820        0 fe001300         0      100  
00000001 00001301
  2001830        0 a0020000         0    20000  
00000000 a0020000
/pci@80000000/isa:    0:c.0     1106:8231 60100 82311106 0000 8
Added assigned
-addresses
/pci@80000000/ide:    0:c.1     1106:0571 1018f 05711106 010e 87
Added assigned
-addresses
  1006110        0 fe001000         0        8  
00000001 00001001
  1006114        0 fe001008         0        4  
00000001 ! 00001009
  
1006118        0 fe001010         0        8  00000001 00001011
  100611c        0 fe001018         0        4  
00000001 ! 00001019
  
1006120        0 fe001020         0       10  00000001 00001021
/pci@80000000/usb:    0:c.2     1106:3038 c0300 30381106 0409 7
Added assigned
-addresses
  1006220        0 fe001040         0       20  
00000001 00001041
/pci@80000000/usb:    0:c.3     1106:3038 c0300 30381106 0409 7
Added assigned
-addresses
  1006320        0 fe001060         0       20  
00000001 00001061
/pci@80000000/other:    0:c.4     1106:8235 68000 82351106 0009 0
Added assigned
-addresses
/pci@80000000/sound:    0:c.5     1106:3058 40100 30581106 0309 4
Added assigned
-addresses
  1006510        0 fe001100         0      100  
00000001 00001101
  1006514        0 fe001030         0        4  
00000001 00001031
  1006518        0 fe001034         0        4  
00000001 00001035
/pci@80000000/pci1106,3068:    0:c.6     1106:3068 78000 30681106 0309 30
Added assigned
-addresses
/pci@c0000000io f8000000/10000 mem c0000000/20000000
/pci@c0000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 7
Added assigned
-addresses


Unless you can spot anything, the only thing I could really see was that the command for bus 0:0.0 was 0 when using pegasos firmware and 7 with bboot. In addition, we know we are adding an empty assigned addresses property when there are no addresses.

I modified my bboot to match the command on PCI bus 0 but it didn't change anything:

BBoot 0.4 ('"unreleased"')
/
pci@80000000io fe000000/10000 mem 80000000/40000000
/pci@80000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 0
/pci@80000000/pci10ec,8139:    0:1.0     10ec:8139 20000 813910ec 0100 0
Fixed ROM BAR
Added assigned
-addressesset interrupt 0109
  
1000810        0 fe001200         0      100  00000001 00001201
  2000814        0 80000000         0      100  
00000000 80000000
  2000830        0 80040000         0    40000  
00000000 80040000
/pci@80000000/pci1234,1111:    0:2.0     1234:1111 38000 11111234 0000 0
Added assigned
-addressesset interrupt 0009
 
42001010        0 81000000         0  1000000  | 00000008 ! 81000008
  2001018        0 82000000         0     1000  
00000000 82000000
/pci@80000000/pci1002,68e1:    0:3.0     1002:68e1 30000 68e11002 01ff 0
Fixed ROM BAR
Added assigned
-addressesset interrupt 0109
 
42001810        0 90000000         0 10000000  0000000c 9000000c
  2001818        0 a0000000         0    20000  
00000004 a0000004
  1001820        0 fe001300         0      100  
00000001 00001301
  2001830        0 a0020000         0    20000  
00000000 a0020000
/pci@80000000/isa:    0:c.0     1106:8231 60100 82311106 0000 8
/pci@80000000/ide:    0:c.1     1106:0571 1018f 05711106 010e 87
Added assigned
-addresses
  1006110        0 fe001000         0        8  
00000001 00001001
  1006114        0 fe001008         0        4  
00000001 ! 00001009
  
1006118        0 fe001010         0        8  00000001 00001011
  100611c        0 fe001018         0        4  
00000001 ! 00001019
  
1006120        0 fe001020         0       10  00000001 00001021
/pci@80000000/usb:    0:c.2     1106:3038 c0300 30381106 0409 7
Added assigned
-addresses
  1006220        0 fe001040         0       20  
00000001 00001041
/pci@80000000/usb:    0:c.3     1106:3038 c0300 30381106 0409 7
Added assigned
-addresses
  1006320        0 fe001060         0       20  
00000001 00001061
/pci@80000000/other:    0:c.4     1106:8235 68000 82351106 0009 0
/pci@80000000/sound:    0:c.5     1106:3058 40100 30581106 0309 4
Added assigned
-addresses
  1006510        0 fe001100         0      100  
00000001 00001101
  1006514        0 fe001030         0        4  
00000001 00001031
  1006518        0 fe001034         0        4  
00000001 00001035
/pci@80000000/pci1106,3068:    0:c.6     1106:3068 78000 30681106 0309 30
/pci@c0000000io f8000000/10000 mem c0000000/20000000
/pci@c0000000/host:    0:0.0     11ab:6460 60000 646011ab 0000 7


I did also do a further test with the empty assigned addresses removed just in case this was confusing OS4 in some way. Again, no change.

At this point I'm not really sure where else to look!


Amiga x5040 ı 16GB ı RX580
GB-A1000 060@100,
A1200 PiStorm32-Lite CM4
Go to top

  Register To Post
« 1 ... 53 54 55 (56) 57 58 59 ... 75 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project