Moderators: Mug UK, Steem Authors, Moderator Team
FedePede04 wrote:it still need skilled to take and use other things, sometimes it is a lot harder.
i don't think i want to guess how many hour you must have spend on STeem. but it must be MAAAAANY.
so I would like to thank you, for continue you work to improve Steem.
Steven Seagal wrote:FedePede04 wrote:it still need skilled to take and use other things, sometimes it is a lot harder.
Of course, but in this case I would say figuring out the correct YM2149 (AY8910 in fact) behaviour was harder. Couldn't have done it myself.i don't think i want to guess how many hour you must have spend on STeem. but it must be MAAAAANY.
so I would like to thank you, for continue you work to improve Steem.
Oh yeah, many hours in the chopper back from missions, but it's a passion, sometimes I prefer it to martial arts!
Code: Select all
PC 146C6 read.w FA0346 = 0
PC 146C6 read.w FA03B4 = 0
PC 146C6 read.w FA048C = 0
PC 146C6 read.w FA051A = 0
PC 146C6 read.w FA0556 = 0
PC 146C6 read.w FA04F4 = 0
PC 146C6 read.w FA050E = 0
PC 146C6 read.w FA056A = 0
PC 146C6 read.w FA053C = 0
PC 146C6 read.w FA0516 = 0
PC 146C6 read.w FA05A6 = 0
Steven Seagal wrote:Thx, I'll look at it.
But I guess you mean BLIT mode (hog bit=0)?
Cyprian wrote:How it works: in a BLIT mode the BLiTTER counts every memory access used by the CPU. And after 64th it takes the control over the bus if I remember correctly for 65 bus cycles (1 cycle for bus mastering, 63 for data operations and 1 for bus mastering), later it releases the bus and again counts every memory access used by the CPU, after 64th it takes the control... and so on
Following code uses exactly 64 bus cycles, and it delays the BLiTTER pass by about 8.5 raster lines (about 4456 CPU cycles):Code: Select all
move.w d6,(a3) ; red to $FFFF8240 8 CPU cycles / 2 bus cycles
move.w d3,(a3) ; white to $FFFF8240 8 CPU cycles / 2 bus cycles
REPT 30
move.l D6,D7 4 CPU cycles / 1 bus cycle
divs.w D5,D7 144 CPU cycles / 1 bus cycle
ENDR
Cyprian wrote:Nicolas, that's cool.
I attached binary and source code. Colors changed as you asked ("halftone" label).
Sixteenth halftone register contains "green" color, to show that blitter uses 63 bus cycles for moving data
Cyprian wrote:Nicolas, that's cool.
I attached binary and source code. Colors changed as you asked ("halftone" label).
Sixteenth halftone register contains "green" color, to show that blitter uses 63 bus cycles for moving data
npomarede wrote:Hi cyprian, this test code is very useful and I could use it to emulate accurate cpu/blitter bus sharing under Hatari (not released yet).
Steven Seagal wrote:npomarede wrote:Hi cyprian, this test code is very useful and I could use it to emulate accurate cpu/blitter bus sharing under Hatari (not released yet).
Wonder how you did it? In Steem, if a blit is going on, there's a check at each CPU R/W, which adds overhead.
Steven Seagal wrote:Release of v3.9.3 planned on 30/9 (next Saturday).
Last dev builds just uploaded, I'd appreciate if you could test those.
Users browsing this forum: No registered users and 1 guest