Re: [hatari-devel] TT palette issue |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] TT palette issue
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Mon, 15 Feb 2016 08:15:41 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1455520541; l=1380; s=domk; d=seimet.de; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Subject:To:From:Date; bh=4P+pQgFweEox+kBS2CEJsVqTMBBFqWhWFD0mWA6CEwc=; b=vVkxMLBvsZrkKWzND/f3HF7Fy3fU65h+1eJbwfwdvp10yITiQz2msknRs6C+rmgJiWM fQS3RZa57LyeiekMFqxgEK/UGf6nZ6C3RasDQSrJm+BCYFO0eF9uHLLTEH+S4kDrd/kS3 HECIeo8V+h1Ts5193vzqH5klQ1Rj4LgzuOo=
Hi all,
This may belong to this thread: Just like some months ago the color
white in TT high is not really white anymore, but rather a very light
shade of grey. Some days ago this was still fine.
Take care
Uwe
> On 12 Feb 2016 at 0:08, Eero Tamminen wrote:
> >
> > According to Hatari code:
> > --------------------------
> > * Write to video shifter palette registers (0xff8240-0xff825e)
> > *
> > * When writing only to the upper byte of the color reg
> > * (instead of writing 16 bits at once with .W/.L).
> > * In that case, the byte written to address x is automatically written
> > * to address x+1 too (but we shouldn't copy x in x+1 after masking x ;
> > * we apply the mask at the end)
> > * Similarly, when writing a byte to address x+1, it's also written
> > * to address x
> > * So : move.w #0,$ff8240 -> color 0 is now $000
> > * move.b #7,$ff8240 -> color 0 is now $707 !
> > * move.b #$55,$ff8241 -> color 0 is now $555 !
> > * move.b #$71,$ff8240 -> color 0 is now $171
> > * (bytes are first copied, then masked)
> > --------------------------
> >
> >
> > If somebody could do similar test also on Falcon, that
> > would be appreciated too. Current Videl emulation code
> > has that functionality commented out, with a TODO...
> >
> The Falcon behaves the same as described above, tested on my Falcon.
>
> Roger
>
>
>