Re: machfb (sort of) working on Mach64 GX

[Michael <macallan%NetBSD.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On May 3, 2011, at 8:17 AM, John D. Baker wrote:

> On Thu, 28 Apr 2011, Michael wrote:
>
> > There is one way to find out if the mode setting code is the  
> > culprit ( it probably is ).
> > In mach4_attach() look for this:
> > if (setmode)
> >         mach64_modeswitch(sc, sc->sc_my_mode);
> >
> > and comment it out.
>
> I did this, and it didn't make any difference.  The display behavior
> with machfb is the same as I described previously.

Yeah, according to your previous mail machfb picked the right timing  
from the EDID info. There goes that theory.

> dsp_precision = 4, dsp_loop_latency = 10,
> mclk_fb_div = 228, vclk_fb_div = 181,
> mclk_post_div = 2, vclk_post_div = 2
>
> /* above is the last legible line printed at the bottom of the  
> screen */
> /* everything from this point forward is compressed into the upper- 
> left */
> /* 1/16th of the screen (1/4 width, 1/4 height).  As such it is just  
> an */
> /* illegible jumble of gray and white vertical bars littered with  
> pixel */
> /* garbage that would be the screen text. */

Does the line above remain visible / readable? If it does then the  
mode setting code is actually doing the right thing and we screw up  
somewhere initialising the drawing engine.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBTb/7dMpnzkX8Yg2nAQJMaggArmn3RcNfoTVZs9u1++sXSYPAg0rAbO9h
dOU6WlX/I41uFxa/zbkXM4NShIUxbP7PgrFGIYsHgTJEJIg0PFLeOtAtwPdxht5Q
r0CkhU3l0XbwOegD83ZesNZZR4eP5EOHI81z+8b3uQL0XQPjIVF1D6Gdhvtt6vHX
vuvipcZvQLihNBKXieHLj5LcLDw9A6qNfU+9uB3D9zPNMvtMOrdyNQjzB2QwyFGX
M/bUrYENjtIsfdSDj72wSHWLtZdILMWWzUxhxDJRyJyiolSrjcb+uqfbEU8LD7aS
GlyMh0+OMnX9oetHBBhensD803FXIjLeyzPeasNbnbWzsAkhwWAUwg==
=buyb
-----END PGP SIGNATURE-----