2022-04-03.log

my_pc_is_amigaI've been looking at the piccoloSD64.card.asm in the CardDevelop.lha packge from Icomp and see they are using the BoardInfo->MoniSwitch to save the current state00:39
my_pc_is_amigamove.bd0,(a0); Init board control register00:40
my_pc_is_amigamove.bd0,(gbi_MoniSwitch,a2); Save board control register00:40
my_pc_is_amigaand they are using in the SetSwitch and SetInterrupt routines...00:40
my_pc_is_amigaNot seeing a SetInterrupt routine in ZZ9000.card or the usage of the Moniswitch -- not sure if that could be reason for the issue that I am having when switch between 2 RTG cards.  When it switches back to ZZ9000 RTG, I get a mostly black screen (this is with DISPLAYCHAIN=YES)00:42
my_pc_is_amigaright now the SetSwitch uses a enable-1 return and not sure if that is same as saving the current state with Moniswitch....00:44
my_pc_is_amigaCan it be that when I switch from the other RTG back to ZZ9000 RTG, that the switch state changes to Amiga video and so when I go back it trys to restore Amiga Video but there is no screen defined and so mess up (black screen)?00:46
- my_pc_is_amiga (QUIT: Ping timeout: 246 seconds) (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)00:51
+ my_pc_is_amiga (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)00:55
- my_pc_is_amiga (QUIT: Ping timeout: 260 seconds) (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)02:11
_BnuI mean, there's no SetInterrupt routine.02:16
_BnuThere never* will be.02:16
_BnuBut this is an issue (not only) you are having. It works fine for me.02:16
_BnuI cannot debug that which does not not-work for me.02:17
_BnuBut like, you can NOT use DISPLAYCHAIN=YES when doing multi graphics card as far as I know.02:17
_BnuBut I was able to switch between the CV64/3D and the ZZ9000 just fine, no problems at all. I could not get it to fail.02:18
_BnuI can NOT figure out what is wrong with something I can't reproduce.02:18
+ my_pc_is_amiga (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)05:57
my_pc_is_amiga_Bnu: With the CV64/3D and ZZ9000 setup that you have I assume you had DISPLAYCHAIN=NO for CV64/3D and DISPLAYCHAIN=NO for ZZ9000.06:04
my_pc_is_amigaI tried DISPLAYCHAIN=NO in my CVisionPPC monitor and DISPLAYCHAIN=NO for ZZ9000 and with that it works.  Of course in this mode then the flickerfixer on the ZZ9000 is esentially turned off06:05
my_pc_is_amigaNot sure if it helps to send a video out of what is happening or if there is any other debug that I could do to help figure it out as I realize that is hard to fix if you can't reproduce it...06:07
my_pc_is_amigaIf I have a ZZ000 RTG workbench screen and also a Amiga native screen open with DISPLAYCHAIN=YES.  Then I activate a screen on the CVisionPPC card, once it comes back it will have a copy of the Amiga screen on the RTG output..  This is instaed of a black screen (when amiga screen is not enabled that I mentioned before).06:23
my_pc_is_amigaProbably best I try to send a video of the situation.06:24
- my_pc_is_amiga (QUIT: Quit: System rebooting) (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)06:28
_BnuYes, but what I mean is that you actively have to make the choice. Unless I'm completely misunderstanding the operation of DISPLAYCHAIN.08:04
+ my_pc_is_amiga (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)08:04
_BnuIe, with it set to YES, you cannot have multiple RTG outputs active, and with it set to NO, you can't have the internal scandoubler active, because P96 will never tell the ZZ9000 to turn off RTG, which is required for switching to the scandoubler.08:05
_BnuBut I currently have 360 pages or something of comics to letter and a short deadline, so I can't really investigate it.08:08
Jopemy_pc_is_amiga, http://eab.abime.net/showpost.php?p=1493435&postcount=146 did you check this08:15
my_pc_is_amigaThanks Jope and _Bnu -- let me check that.  I had gotten this descriptiion from a EAB post "DISPLAYCHAIN=Yes|No Tells P96 whether the graphics board is part of the display chain, that is, part of a cable running from native Amiga video, through the board, to the monitor. A board that is not part of the display chain i08:19
my_pc_is_amigas understood to have a separate/independent monitor and cannot be switched to the same monitor as the native output. If you want P96 to switch between two monitors, one of the boards cannot be part of the chain and therefore has to have a separate monitor.08:19
my_pc_is_amigaFrom the P96ScreenCx Readme -- "P96 drivers only participate in multi-monitor switching if their08:21
my_pc_is_amigaDISPLAYCHAIN tooltype is set to NO. Otherwise, they are assumed08:21
my_pc_is_amigato be displayed on the same monitor as the native Amiga video, and08:21
my_pc_is_amigathus do not receive their own set of tool types. Placement relative08:21
my_pc_is_amigato "shared" P96 cards in the display chain is indicated by the "Native"08:21
my_pc_is_amigamonitor.08:21
my_pc_is_amigamaybe something that I can try to get more clarifcation with Thomas on EAB...else I could try a PIV card and the CVsionPPC card combo to see how that works.  08:24
_BnuI mean, there's a difference between the native RGB output and the scandoubler.08:25
_BnuWe rely on P96 telling us to turn off the RTG (or the Amiga resetting) to enable the scandoubler.08:25
_BnuAnd when P96 never tells us to turn off the RTG, we never do, because we can't really know.08:25
Jopeyou can only have one displaychain I believe08:30
Jopethe cvisionppc's display chain sucks anyway as it samples chip ram or something like this08:30
Jopeso the cvisionppc should definitely be displaychain=no.. but I admit I don't know what to do with the native driver and zz9000 running on the same machine. the native driver is intended for computers with no rtg board08:31
Jopeif you have a zz9000, you can get the p96 cpu blit benefits already08:31
my_pc_is_amigaIn my case I'm not using a P96 native driver...08:32
Jopeok08:32
my_pc_is_amigait is just native Amiga output...sorry if that was confusing..08:32
Jopeso you have zz9000 and cvppc monitors in devs:monitors?08:32
my_pc_is_amigacorrect08:33
my_pc_is_amigaand ZZ9000 DISPLAYCHAIN=YES and as you mentioned CVISIONPPC has DISPLAYCHAIN=NO 08:34
Joperight08:34
my_pc_is_amigain the EAB post you sent Thomas mentions a chipset->graphics card b->monitor 1  and a  graphics card a->monitor 208:34
my_pc_is_amigawhich is basically what I have...08:34
Jopeyeps.. 08:34
Jopecard b is the zz9000 in this case08:34
Jopenow I wonder if the cvppc has something going on there that thomas is not turning off08:35
my_pc_is_amigayeah I may need to check with Thomas more on that  -- or again I may need to put PIV instead of ZZ9000 to just check behavior....08:36
my_pc_is_amigathough I thought I remember it working with PIV before but been sometime since all of these P96 releases08:37
Jopeyeah.. at least then the drivers are all thor's handicraft08:37
Jopeor not totally but at least he's in charge08:37
my_pc_is_amigayeah08:37
my_pc_is_amigaIt does seem that from this sentence "Now, if the frontmost screen switches from "native" or "grahics card b" to "graphics card a", this means that it is possible to have DISPLAYCHAIN=YES for at least 1 card with mult. graphic cards...just a reply to _Bnu statements...08:39
Jopeyes08:39
my_pc_is_amigabut again ... it is confusing to me in general....08:39
Jopedisplaychain = yes can also hook together several rtg boards.. if you have cv64s for example08:40
my_pc_is_amigaok got it08:40
Jopeand connect scandoubler -> cv641 -> cv642, both cv64s need to have displaychain=yes08:40
Jopemay not be exactly the results you're expecting though :-D08:41
my_pc_is_amigaok ..08:41
Jopewish there was up to date docs in one place for p64 3.x08:42
Jopethere was some lament about how the .guide is so out of date on eab and thor mentioned that he'd prefer to have it in the icomp wiki08:42
Jopeme personally, I'd like to have it in the .guide in case something ever happens to jens08:42
my_pc_is_amigayes -- I saw that...08:43
Jopemore data hoarding needed.. 08:43
my_pc_is_amigaI too would rather have a guide08:43
- my_pc_is_amiga (QUIT: Quit: Client exiting) (~my_pc_is_@c-71-197-66-36.hsd1.ca.comcast.net)08:44
- xet7 (QUIT: Remote host closed the connection) (~xet7@user/xet7)13:32
+ xet7 (~xet7@user/xet7)13:34
+ Jadek (~Jadek@87-207-204-28.dynamic.chello.pl)13:40
- Jadek (QUIT: Client Quit) (~Jadek@87-207-204-28.dynamic.chello.pl)13:42
apolkosnik[m]Haha, they would rather not mess with either the installer script not the guide. 13:58
- xet7 (QUIT: Read error: Connection reset by peer) (~xet7@user/xet7)18:14
+ xet7 (~xet7@user/xet7)18:16
- xet7 (QUIT: Remote host closed the connection) (~xet7@user/xet7)21:40
+ xet7 (~xet7@user/xet7)23:12

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!