<html><body>Hi Joerg,<br><br>Using palettes would utilise memory while offering more colours. This would also possibly bring it close to Ceres-2. The two procedures bellow taken from Display.Def of Ceres-2 project, do they imply the use of a colour map (palette)?<br><br>PROCEDURE SetColor*(col, red, green, blue: INTEGER);<br>
PROCEDURE GetColor*(col: INTEGER; VAR red, green, blue: INTEGER);<br><br>From H/W point of view, coudl it be more difficult to implement in Verilog?<br><br>Tomas<br><br><p>---------- Původní zpráva ----------<br>Od: Jörg Straube <joerg.straube@iaeth.ch><br>Komu: ETH Oberon and related systems <oberon@lists.inf.ethz.ch><br>Datum: 20. 4. 2016 8:30:11<br>Předmět: Re: [Oberon] RGB display in Oberon RISC5</p><br><blockquote>Hi Magnus<br><br>Thx for preparing VID.v<br>As the original ProjectOberon has only 1M of memory, it's a pity to waste 25% of your 4 bit color layout. Basically, we could use 16 colors instead of 8.<br>Instead of mapping the bits directly to RGB, I would rather use the 4 bits as index into a color palette.<br><br>Display.Mod has to be adapted accordingly.<br><br>Jörg<br><br>> Am 18.04.2016 um 21:59 schrieb Magnus Karlsson <magnus@saanlima.com>:<br>> <br>> I have made an updated version of VID.v with support for an RGB video buffer.<br>> <br>> The video buffer is now 4x larger (about 40% of the total 1 MB RAM) and video refresh will use up about 40% of the memory bandwidth.<br>> <br>> See http://saanlima.com/forum/viewtopic.php?f=14&p=1786#p1783 for Verilog code and bit files for Pepino_LX9 and Pepino_LX25.<br>> <br>> Magnus<br>> --<br>> Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems<br>> https://lists.inf.ethz.ch/mailman/listinfo/oberon--<br>Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems<br>https://lists.inf.ethz.ch/mailman/listinfo/oberon</blockquote></body></html>