English Amiga Board - View Single Post

Thomas Richter · 24 April 2022, 19:17

[QUOTE=hexaae;1542923]MuForce:

Code:

 ----> 64CF5A0E - "LIBS:picasso96/rtg.library"  Hunk 0000 Offset 00024826

This is a call of the rtg.library in bi->GetCompatibleDACFormats() which is only made if the board indicates that DAC switching is possible. This call here comes from the board init phase where the rtg.library calls the driver to find out which modes require mode coercion because pixel resolutions are different. If UAE assumes that at this point video memory is already available or bitmaps are allocated, then this may fail.

Also, this call will go into the wild if UAE has indicated that DAC switching is supported, but the required methods bi->CoerceMode() and bi->GetCompatibleDACFormats() are not available and are NULL-pointers. They need to be available directly after the chip has been initialized as P96 requires them already to fill the display info database (again, for mode coercion purposes).

24 April 2022, 19:17	#15
Thomas Richter Registered User Join Date: Jan 2019 Location: Germany Posts: 3,247	[QUOTE=hexaae;1542923]MuForce: Code: ----> 64CF5A0E - "LIBS:picasso96/rtg.library" Hunk 0000 Offset 00024826 This is a call of the rtg.library in bi->GetCompatibleDACFormats() which is only made if the board indicates that DAC switching is possible. This call here comes from the board init phase where the rtg.library calls the driver to find out which modes require mode coercion because pixel resolutions are different. If UAE assumes that at this point video memory is already available or bitmaps are allocated, then this may fail. Also, this call will go into the wild if UAE has indicated that DAC switching is supported, but the required methods bi->CoerceMode() and bi->GetCompatibleDACFormats() are not available and are NULL-pointers. They need to be available directly after the chip has been initialized as P96 requires them already to fill the display info database (again, for mode coercion purposes).