On Tue, 3 May 2011, Michael wrote:
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.
Yes. The lines between the "screen goes black, these lines scroll up" comment and the above comment block remain readable as long as the machine is running. Console/ttyEn output makes the pixels dance in the upper-left region of the screen as noted. Now that I've got more noise from the driver, one additional thing I'm going to try is to see if any of the reported information is different once I let MacOS X touch the hardware. As I noted in the past, if MacOS X is allowed to boot first, rebooting with NetBSD sees machfb display just fine. Any other suggestions for where to poke? -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645