RE: [Linux-fbdev-users] Frambeffer to TV troubles

[Hihn, J. <Jas...@ve...>]

That is correct... Had it worked immediately, I'd not have bothered to
post ;-)

With the adjusted pixel clock, I am able to select between 640x480x16bpp
and 800x600x16bpp (perhaps others) using the vesa modes, without
trouble.  The weirdest thing was that fbset would change the patterns on
the TV, so I thought it was working. It looks like everything was
changing except the pixel clock...

=09

-----Original Message-----
From: Geert Uytterhoeven [mailto:ge...@li...]=20
Sent: Tuesday, March 09, 2004 5:17 AM
To: Hihn, Jason
Cc: lin...@li...
Subject: Re: [Linux-fbdev-users] Frambeffer to TV troubles

On Mon, 8 Mar 2004, Hihn, Jason wrote:
> I've got a ATI Graphics Expression+ PC2TV (ATI MACH64/Rage II GT) and
I
> finally got TV out to work. The perplexing thing was it's boot up and
> you could see output on the TV (using composite out), but when asked
for
> a video mode  it's lose it after that. I played around with fbset,
> getting the monitor to do all kinds of funky things, but never a
> picture.  (I was playing with resolutions and timings) Oh, and I was
> using the Vesa driver
>
>
>
> Then I went into include/linux/fb.h and made the default videomode's
> timings as I wanted: 20330, 128, 32, 32, 8, 128, 5 (NTSC) which
worked!
> Now I use mode 0x311 and I can get a picture. It seems that the
pixclock
> is hardcoded to some non-NTSC compatible values.

So if you pass these values using fbset, it doesn't work?

Strange...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
ge...@li...

In personal conversations with technical people, I call myself a hacker.
But
when I'm talking to journalists I just say "programmer" or something
like that.
							    -- Linus
Torvalds