amigawiki

User Tools

    ~~ RM: keiner ~~ UI: ---start--- ~~ IP:3.22.63.154~~

Site Tools

(??) You are here: start » en » expansion » av » picasso_iv

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:expansion:av:picasso_iv [2015/10/06 19:03] – Tobias Seileren:expansion:av:picasso_iv [2024/09/22 00:28] (current) – external edit 127.0.0.1
Line 1: Line 1:
-<awbox translate>FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)//</awbox> 
- 
 ====== Picasso IV ====== ====== Picasso IV ======
  
Line 20: Line 18:
  
 It has a scan doubler and [[wp>Flicker fixer]] built-in . That means that the Amigas own video signal will be captured by the Picasso IV and changed in a way that it can be displayed on a standard VGA CRT or LCD display. It has a scan doubler and [[wp>Flicker fixer]] built-in . That means that the Amigas own video signal will be captured by the Picasso IV and changed in a way that it can be displayed on a standard VGA CRT or LCD display.
-Expansion of this kind where already available for the Amiga at this time. +Expansions of this kind where already available for the Amiga at this time. 
-But the Picasso IV made a difference in how this was done.+But the Picasso IV made a difference in how it was done.
  
-Conventional flicker fixers temporarily save the picture data of the Amiga line by line in an fast video memory and read them again at double the speed to increase the display frequency of the picture.+Conventional flicker fixers temporarily save the picture data of the Amiga line by line in a fast video memory and read them again at double the speed to increase the display frequency of the picture.
  
 The Picasso IV uses its graphics controller. This controller has the ability to capture digital video streams into its frame buffer memory. The Picasso IVs flicker fixer is just generating the needed control signals for the graphic controller capture port which is writing the picture data directly into the frame buffer memory to directly output them on the VGA port. The Picasso IV uses its graphics controller. This controller has the ability to capture digital video streams into its frame buffer memory. The Picasso IVs flicker fixer is just generating the needed control signals for the graphic controller capture port which is writing the picture data directly into the frame buffer memory to directly output them on the VGA port.
Line 30: Line 28:
 Unfortunately its not possible to synchronize the output display rate and the input rate. Unfortunately its not possible to synchronize the output display rate and the input rate.
 For that it might happen you see some screen tearing with moving pictures (( [[wp>Screen tearing]] )). For that it might happen you see some screen tearing with moving pictures (( [[wp>Screen tearing]] )).
-The flicker fixers is only able to work in standard PAL or NTSC mode since the capture port of the graphics controller is not able work at higher data rates.+The flicker fixer is only able to work in standard PAL or NTSC mode since the capture port of the graphics controller is not able work at higher data rates.
  
 The PicassoIV has several expansion connectors for which some modules have been developed. The PicassoIV has several expansion connectors for which some modules have been developed.
Line 40: Line 38:
 The cards manual also mentions a 3D, an MPEG and a PowerPC processor modul. Those where not built/developed for different reasons. The cards manual also mentions a 3D, an MPEG and a PowerPC processor modul. Those where not built/developed for different reasons.
  
-[{{ :de:expansion:av:klaus_vt.jpg?200|Klaus Burkert † 04.04.2001}}]+[{{ :de:expansion:av:klaus_vt.jpg?200|Klaus Burkert, *02.03.1967; †04.04.2001}}]
  
-The 3D module was planned to have a Voodoo Graphics chipset just like the Macintosh version the 3D Overdrive (( [[wp>3dfx_Interactive#Voodoo_Graphics_PCI]] )) and 8MB of memory (( 4MB frame buffer/ 4MB texture and 3D data )). It 'just' would have needed a pcb relayout to make the module fit the local PCI connector of the Picasso IV.+The 3D module was planned to have a Voodoo Graphics (( [[wp>3dfx_Interactive#Voodoo_Graphics_PCI]] )) chipset just like the Macintosh version the 3D Overdrive  and 8MB of memory (( 4MB frame buffer/ 4MB texture and 3D data )). It 'just' would have needed a pcb relayout to make the module fit the local PCI connector of the Picasso IV.
  
 To have a better idea of peoples interest in purchasing such a card a poll was started online on Village Tronics website. 500 people declared their interest and the cards layout was done by an external developer. To have a better idea of peoples interest in purchasing such a card a poll was started online on Village Tronics website. 500 people declared their interest and the cards layout was done by an external developer.
 At the same time the Macintosh market was getting more difficult to handle and new products in this field drew time and money onto them. At the same time the Macintosh market was getting more difficult to handle and new products in this field drew time and money onto them.
  
-Then Amiga main developer Klaus Burkert left the company, like many others at this point. He bought out all of the companies Amiga hard and software and the associated intelectual property.+Then Amiga main developer [[en:​history:​kburkert|Klaus Burkert]] left the company, like many others at this point. He bought out all of the companies Amiga hard and software and the associated intelectual property.
 Soon he started to work at [[wpde>Metabox]] AG. Soon he started to work at [[wpde>Metabox]] AG.
  
Line 112: Line 110:
 \\ \\
 **Software:** Picasso96 or CyberGraphX 3/4\\ **Software:** Picasso96 or CyberGraphX 3/4\\
-**additional requirements:** 68020-Prozessor, Kickstart 3.x (flicker fixer works from Kick 1.3)\\+**additional requirements:** 68020-processor, Kickstart 3.x (flicker fixer working from Kick 1.3)\\
 **note:** Linux/NetBSD support\\ **note:** Linux/NetBSD support\\
 **known problems:** --\\ **known problems:** --\\
Line 152: Line 150:
 |2 |First workaround for the Fusion40 (ignore function codes for Z2) (also for some Hardital boards), which is violating the A2000 CPU-Slot specs, it doesn't drive functions codes (see MC68k spec). It had a couple of other problems and wasn't released though..| |2 |First workaround for the Fusion40 (ignore function codes for Z2) (also for some Hardital boards), which is violating the A2000 CPU-Slot specs, it doesn't drive functions codes (see MC68k spec). It had a couple of other problems and wasn't released though..|
 |3 |Adressing the "Zorro-III DMA problem" which in fact is a bug in Buster -11 which cripples some CPU-initiated cycles clearly violating the Z3 Spec. As this forced major changes in the implementation of the Zorro-Interface, it took some time and had a lot of bug-ridden interim versions that didn't leave the lab.| |3 |Adressing the "Zorro-III DMA problem" which in fact is a bug in Buster -11 which cripples some CPU-initiated cycles clearly violating the Z3 Spec. As this forced major changes in the implementation of the Zorro-Interface, it took some time and had a lot of bug-ridden interim versions that didn't leave the lab.|
-|4 |Final one. In fact, it's a revision bump for clear identification from the last Rev 3 which was finally working according to specs and had no bugs found. As of the latest production run this was the factory standard. Due to internal changes, it requires FlashROM 7.1 or above (the boards come with 7.x) it definately drives you into problems, when running ( or trying to) a Rev 4 bridge with a FlashROM below 7.x. If it gets up at all with a Flash below 7.x, it may report a Rev 2 for the bridge because of internal reassignments... (It cured all known-until-then problems (and I don't know of others that revealed themselves after).|+|4 |Final one. In fact, it's a revision bump for clear identification from the last Rev 3 which was finally working according to specs and had no bugs found. As of the latest production run this was the factory standard. Due to internal changes, it requires FlashROM 7.1 or above (the boards come with 7.x) it definately drives you into problems, when running ( or trying to) a Rev 4 bridge with a FlashROM below 7.x. If it gets up at all with a Flash below 7.x, it may report a Rev 2 for the bridge because of internal reassignments... .|
 \\ \\
-===== FlickerFixer Revisionen =====+===== FlickerFixer revisions =====
 ^Ver.^ ^ ^Ver.^ ^
 |1 |First working version used in-house in v1.1 prototype PCBs. They never (with some exceptions) shipped.| |1 |First working version used in-house in v1.1 prototype PCBs. They never (with some exceptions) shipped.|
Last modified: 2024/09/21 23:40

Page Tools

Unless otherwise specified, the content of this wiki is published under the following license:
Attribution - Share Alike 3.0 Unported (CC BY-SA 3.0) CC Attribution-Share Alike 3.0 Unported
about   Driven by DokuWiki   Data Protection