#ez80 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ez80, aggregated by home.social.
-
Time for another image viewer for #AgonLight #Console8 - this time, PCX format. There are a number of reasons why I chose to display this format on the Agon/Console8.
* It is an already existing format
* The format is supported by modern tools, including #GIMP
* It uses a very simple form of compression ideal for 8 bit CPUs
* The specific choice of 16 colours has additional benefits:
* The 16 colours are chosen from within the available 64 colour palette
* The 16 colours allows the image to be sent to the VDP with 2 pixels per byte, speeding up the transfer
I've attached a sample here to show just the quality of the resolution and colour depth. #z80 source code and binary is at:
https://github.com/sijnstra/agon-projects/tree/main/PCXview
#retrocomputing #image #viewer #ez80 -
Oh great, NOW this gets some attention right as I’m ripping out the custom mnemonics for standard ones :P Too much for users to mind-map on top of learning #eZ80 when I add it. I will say though that even if you don’t use #v80, the source code is the most heavily commented and described assembly you will likely ever see. If you want to know how to write a real CP/M and/or #Z80 application, look no further.
-
Repórter Retro 108
https://retropolis.com.br/2024/10/31/reporter-retro-108/
#ReprterRetro #68000 #68000EUmaNoites #8BitShowAndTell #AdrianBlack #AppleII #AppleIIc #BASIC #BBC #BBS #biblioteca #cartuchos #Ceefax #CERN #Commodore64 #CommodoreSX64 #CompuServe #DriveDeDisquete #elite #EUA #eZ80 #FORTRAN #Galaxian #GEOS #GeoWorks #Hackaday #HDMI #InterfaceGrfica #JecelMattosDeAssumpoJr #Livros #Macintosh #MacintoshII #MacintoshIIcx #MSDOS #namco #NES #Nintendo #PlacaDeVdeo #RC2014 #ReinoUnido #
-
Attempting a rewrite of my 8-bit multi-platform, multi-ISA, assembler's instruction parser. #v80 uses a static tree for mapping instructions into opcodes (2nd image) which is very fast and efficient but hairy to write.
The new approach (1st image), uses an alphabetical list of instructions with a byte to state how many chars of the previous entry are re-used since alphabetically, the left-most chars repeat the most.
There's no guarantee this will even save space (#Z80 ISA is currently 4KB, #MOS6502 is about 1.7KB) and it will likely be slower as more lines will need to be skipped vs. a char-by-char branching approach, but it may help for very large ISAs, the size of which can balloon drastically with lots of shared prefixes, something I'm worried about with adding #eZ80 support. The alternative is adding 'macro' characters for shared-prefixes, but that bloats the native code that needs to be ported between architectures.