Hi Petr,
all good with the palette handling.
There is another issue I ran into while testing atafb's handling of 16
bit video modes though:
When specifying non-default video modes, the kernel parameter
video=atafb:R320;240;16
is used (as an example). Using this in ARAnyM, the command line ends on
video=atafb:R320
and anything specified past the video option on the command line is lost
(along with xres and depth).
The same mode option is passed on to the kernel correctly by ataboot on
my Falcon.
Could you look into what in ARAnyMs parsing of the config file or the
'Args' config item causes truncation of the kernel options?
This can be trivially worked around by using another token separator,
and Geert is the only one who ever tried 16 bit video modes as far as
I've seen, so nothing urgent ...
Cheers,
Michael
Am 15.02.2022 um 22:16 schrieb Petr Stehlík:
On Út, 2022-02-15 at 09:11 +0100, Geert Uytterhoeven wrote:
Now what would cause us to miss every other palette update or depth
change?
That's a good question! Why does ARAnyM sometimes decide to use the
Falcon palette, and sometimes the STe palette, and not only with
bpp == 2, but also with other color depths?
just wanted to let you know that I'm following you. If you happen to
identify any bug in ARAnyM I'll try to fix it ASAP.
Thanks,
Petr
