Quoting Bernd Ernesti (28-Jun-00 09:50:16):

> [..]
>> However even with CV_AGGRESSIVE_TIMING, I get an pixelclock too
>> high error with modes 12 and 13. These modi work fine with AmigaOS.
>> Do I have to live with these errors? It's a pity because mode 12 is
>> the ony I would like to work with.
>> 
>> Here my /etc/grfmodes:
> [..]
>>   10  100000000 1152  870  16 1152 1184 1312 1456  870  873  876 
>>   915 default
>>   11  100000000 1152  900  16 1152 1184 1312 1456  900  903  906 
>>   945 default
>>   12  110000000 1280 1024  16 1280 1352 1480 1688 1024 1025 1026
>>   1066 default
>>   13  108000000 1152  864  16 1152 1184 1312 1520  864  867  870 
>>   909 default
>> # 24-Bit Modes.
>>   14  32000000   640  480  24  640  656  720  840  480  481  484 
>>   500 default
>>   15  50000000   800  600  24  800  816  896 1056  600  601  604 
>>   625 default
>>   16  53000000  1024  768  24 1024 1048 1144 1208  768  769  772 
>>   789 default
>> ----- cut here -----
>> 
>> Without CV_AGGRESSIVE_TIMING, I get errors with modes 10, 11, 12,
>> 13 and 16.

> Mode  MHz
> (bit) without overlocking with overclocking (CV_AGGRESSIVE_TIMING)

> 8 135         135
> 15/16  80         100
> 24/32  50          55

> This are the chip limits, so even CV_AGGRESSIVE_TIMING is 25% over
> the limit for the 16bit mode.

Do I harm the CV64 in any respect (hardware wise) when I use modes
which go above this 25% increase limit? I can use these modi under
AmigaOS without any problem.

> And your mode #12 is 37.5% over the chip limit.

And mode #13 is 35% above.

TIA

-- 
Cu  Georges Heinesch, Luxembourg
    geohei@geohei.lu
    http://www.geohei.lu
    PGP 2.6.3i / 5.1i public key on request and on public servers

... like a virgin ...