Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/23/22 in all areas

  1. Hello Everyone, I've another update on the VERA design, and this one is important if you are working with VERA interrupts. Please read if you write games, demos, or any program that uses line interrupts. The IRQLINE register now has different read and write semantics. Writing the IRQLINE register (IRQLINE_L / $9F28 and IEN / $9F26 bit 7) still works the same, however reading the IRQLINE register now returns the new SCANLINE register. This is a 9 bit raster line counter that starts at 0 and counts up 511. It will sit at 511 for scan lines 511-524. 511-524 are "scan lines" that happen during VSYNC. In progressive scan mode, 479 is the last visible line. In interlace mode, SCANLINE counts even numbers on even fields and odd numbers on odd fields. This means that bit 0 of the SCANLINE register reports nearly the same thing as bit 7 of the DC_VIDEO register. There is one "trap" here that developers need to be on the lookout for here: it is not safe to set bits in the IEN register using a read-modify-write. Performing a code sequence such as LDA $9F26 / ORA $02 / STA $9F26 or using the W65C02 bit set/clear opcodes has a chance to flip the value of IRQLINE bit 8 depending on the line being drawn when that code executes. Any code writing the IEN register will need to know what the value of IRQLINE[8] should be because it is no longer accessible through the register interface. This was discussed at some length on Discord and the feedback from those present was that the drawbacks from having to take a few extra steps when writing the IEN register was outweighed by the benefits to some types of software being able to poll for a particular line. If anyone feels that we reached the wrong conclusion, please make your case (constructively and with civility!) in this thread so that we know where to find it. More details can be found in the PR implementing this change here: https://github.com/fvdhoef/vera-module/pull/21 Here is sample output from a demo program written by @MooingLemur that changes the background color every scanline.
    1 point
  2. Like the X16 keyboard which costed me over 200€
    1 point
  3. Unfortunately, drivers are often slow to "mature", even Nvidia and AMD take a while to get their drivers in order with generational releases, and even more so with architectural updates. I have a feeling Intel Arc's completely new Xe HPG architecture means it's going to take a while to get good drivers. At least AMD and Nvidia have something to build upon, Intel is doing this from the ground up.
    1 point
  4. Just in case anyone's been looking for information on how to write code for the YM2151, the Offical documentation now has a register reference in the style of the other documentation sections, and also includes a short "getting started" tutorial on the task of communicating with the chip. It doesn't go into FM instrument design theory, as that's beyond the scope of such a document. https://github.com/commanderx16/x16-docs/blob/master/X16 Reference - 09 - Sound Programming.md
    1 point
  5. The kiosk demo at VCF Midwest was almost entirely SD-based (the kiosk code lived in the ROM, but all the demo software was loaded from the SD card). Zero read failures all weekend. Seems pretty stable.
    1 point
×
×
  • Create New...

Important Information

Please review our Terms of Use