konimaru / waitvid.2048 Goto Github PK

I am using your POC 80x25 RAM 720x400 driver code, I have added the code page 437 'extended ascii' characters to the font. But because the ninth column is always the background, the line or box drawing characters don't connect on the left and right. I believe the IBM monochrome text display adaptor had a nine column character set, and duplicated the last column of every character in the font, that is how they got a nine column cell, with an eight column font. Would it be possible to do this with your code ?

I've tried Marco Maccaferri's 640x400 resolution patches, which solve the problem of the connecting characters by making the displayed character cell 8x16 instead of 9x16, but the timings don't work well on all monitors I've tried, especially the one I am using now, so I'm looking for another way.

In your code, what causes the ninth column to be taken from the background ?

Thank you, your advice here is most appreciated.

Write some code which allows an external cog to display stuff together with the actual driver. This boils down to WHOP synchronization.

Important parameters:

• driver cog ID
• driver frame indicator
• external cog ID

Make sure DDK is updated as well (see issue #5).

Adresszuordnung im IRM (Grafik und Video-RAM)
Mit Hilfe der folgenden Formeln kann man die Speicherzellen, die die Informationen zur Darstellung eines beliebigen Bildpunktes enthalten, ermitteln.
Die Bildinformationen sind im IRM nach folgendem Prinzip abgelegt:
Je 8 horizontal nebeneinander liegende Bildpunkte sind im Pixel-RAM als 1 Byte abgespeichert.
Dieses Byte enthält nur die Vordergrund-Hintergrundinformation der Bildpunkte.
Die Farbinformation ist für jeweils 1 Reihe von 8 Bildpunkten zu einem Byte im COLOR-RAM zusammen gefaßt.
Dieses Byte legt also für 8 Bildpunkte eine Vorder- und eine Hintergrundfarbe fest.
Um das Farb- und das Pixelbyte eines Bildpunktes zu bestimmen, werden die Pixelzeilennummer und die Zeichenspaltennummer, in der sich der Punkt
befindet, hexadezimal verwendet.
Mit der folgenden Formel kann man die Pixel-Byte-Adresse (hRAM) errechnen:
Adresse = 0H + Zeichenspalte * 100H + Pixelzeile
0 =< Zeichenspalte =< 27H
0 =< Pixelzeile =< 0FFH
Mit der folgenden Formel kann man die Farb-Byte-Adresse (hRAM) errechnen:
Adresse = 4000H + Zeichenspalte * 100H + Pixelzeile
0 =< Zeichenspalte =< 27H
0 =< Pixelzeile =< 0FFH

One question, though, now at 480 pixels, I think I'd like to try the
underline cursor at two lines high. The original IBM PC cursor was two
pixels high, I believe. I'll bet that's pretty easy, there may be a
define somewhere. Is that possible ?

• palette resides in hub RAM
• entries must include sync pattern
• NG

The usual what & Co ...

Either that or copy stuff from the DDK (and keep it as a stand-alone demo).

The attached patch allows to run the POC 80x25 RAM driver at a resolution of 640x400@70Hz instead of the current 720x400. With the 8x16 font it looks a bit better, especially if you use the full VGA font, since it doesn't have the 9th background pixel. 640x400 should also be the MS-DOS boot resolution mode.

I'm not sure if this resolution the two cogs are still necessary, or if there is some issue with the timings, it looks good on my monitor but I also have learned that it is very forgiving, so a review is very welcome.

poc-80x25-ram-640x400-driver.patch.txt

The adjustment value (vscl) for the video generator (to get driver and overlay in sync) is currently being latched with an undefined colour (on the way to vertical sync). Inserting a waitvid zero, #0 after its initialisation - as planned - will make me feel better.

The current limit being 128, this requires an update to the actual font file (128-255 either upside down or inverted) and two minor changes to the driver itself (pixel loader).

The screen array has ASCII / attributes bytes swapped compared to the other 80x25 drivers.
Would be possible to make them consistent ?

IIRC there is plenty of time for what needs to be done. Emitter still needs to be unrolled though.

I don't know why but i can't make any of them work on my propboe. VGA is connected from 8-15. i know it works since i could compile a previous version: for instance your driver here works correctly https://forums.parallax.com/discussion/146678/vga-launcher-vga-demos-for-propboe-users

• archive 3-colour version
• review init command sequence

• palette resides in hub RAM
• entries must include sync pattern
• NG

ATM only 8x8 and 8x12 are supported, there is demand for 8x16 as well.

In normal use, an MDA produces an 80x25 text screen. ... Although the characters are 9 pixels wide, the bitmaps in the ROM are only 8 pixels. For characters C0h-DFh, the ninth pixel column is a duplicate of the eighth; for others, it's blank.

This will be based on model NINE, IOW

• external palette (256 entries)
• blink mode (flag in palette entry)

The font will be 8x16. Display behaviour as stated above:

• characters $C0..$DF have their column 8 duplicated
• other characters will display background colour in column 9

footprint (F/P): 4K/0K5, (NINE: 5K/0K5)

This driver definitely needs sync-isolation.

I would love to see some video drivers with sprite support.
I haven't written VGA drivers for the propeller so I don't know how challenging this would be. But here is what I personally would love to have:

High End

• 320x240 resolution
• 40x32 chars

Low End

-256x192 resolution
-32x24 chars

Common

• Each char has dedicated background and foreground color from palette of 64 colors
• 8x8 RAM font

Sprites

• 8x8 resolution
• 16x16 resolution (can choose)
• At least 8 per scanline
• Single color OK...multi color would be great

If I were to start this driver myself, what would be the best driver in this project to use as a template?

Thanks!

Hi

Please help me how to use your vga drivers.

Esspecially 256x192 how to use simple pixel(x,y,color) many thanks little examples.

Kamil

• dual cog design

This had been kicked out during (re)development. In order to keep our 256 palette entries a flag could be stored in the palette entry itself (rather than sacrificing a bit of the index).

Thank you for such a great little video driver!

It's working great, but I was wondering if I could request a specific resolution.

800x480 @ 60
100X60 character and/or 50X30 character

This is for a rc2014 vt100 being used with with a 7" 800x480 ebay special Pi monitor.

Thank you!

Edited character counts because I can't do math

Probably best to grab 100xP.ui and go from there.