From mint-bounce@lists.fishpool.fi Mon Jan 18 14:14:49 2010 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-15; format=flowed X-PMX-Version: 5.5.3.366731, Antispam-Engine: 2.7.0.366912, Antispam-Data: 2010.1.18.185719 Message-id: <4B54B284.5070606@atari.org> Date: Mon, 18 Jan 2010 20:12:04 +0100 From: Odd Skancke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; nb-NO; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] libgem16: vs_color References: <4B542D75.6080103@freesbee.fr> <4B543E5D.30600@atari.org> In-reply-to: X-Antivirus: avast! (VPS 100118-0, 18.01.2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Den 18.01.2010 14:35, skrev Helmut Karlowski: > Am 18.01.2010, 11:56 Uhr, schrieb Odd Skancke : > >> Does this happen with all VDI versions? (Nvdi, no VDI enhancers or >> just fvdi) > > Visual damage appears only with fvdi. I only know NVDI and the > crazy-dots-vdi (a little). I assume NVDI silently clears the LSB or does > use another method to get the values. In fvdi this bit is used as a > flag, and also cleared, but vs_color acts different then. Then I would suggest fixing the problem where the problem is, and not clutter up the XaAES source with #ifdefs to accomodate for faulty software. At least this is the best approach where the sources are available. I have not looked extensively over the ASM you posted yet, but at first glance I cant see anything wrong. If I misunderstood your answer, I'm sorry .. you do say that the corruption of stack/vdipb only happens under fVDI? > > I will check it with NVDI-ET4000 too, but at that stage in libgem the > VDI isn't touched yet. >