From mint-bounce@lists.fishpool.fi Tue Jan 19 04:24:33 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=sALhrhAihw+Nuj+PqZEe4sx7geXQ6jpVfVpHAVH/eeU=; b=H+q88eNC+AbCrDgrmLASN1dQzLkCX5WqNayNcc6QOlXcQsp/qobISpAZ1QJax2/3Bb 7K5d7AbuqlOOmMXtkcp+6KMwWp1AymufdIQnbVSIaO4y/ocR29nSQ0VPeCMxnAAZOEOy sEPfPdLXKsA9bLyl6RkSNUVpciwpxtcI9pLR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=b6fxjJ+bcOg8NsjtxOSulf2qOQQZ2GGv95JmapXD06gieifAkSwnEAjQFLOmPuf6IG O1cBdPiymU8ui6kG8weyxjznmPE+c2ZRUVhr6ehz6o2QZ42l7q7xG0mtE1JiSEIY+RLJ 4QyRj4O9nHv6k6r7PGlNbeumXLj5DaE5zPAwM= Message-ID: <4B546705.7090907@atari.org> Date: Mon, 18 Jan 2010 14:49:57 +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 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] libgem16: vs_color References: <4B542D75.6080103@freesbee.fr> <4B543E5D.30600@atari.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Approved-By: tjhukkan@fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: oskancke@gmail.com 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. >