[MPlayer-dev-eng] [demitree at starband.net: Docs: ATI TV-Out Update]

[Nick Kurshev]

Hello, Gabucino!
On Wed, 24 Oct 2001 18:15:37 +0200, you wrote:

> Nick, is this useful?
> 
> -- 
> Gabucino
> 

#Regarding the ATI TV-Out feature, in your current docs you said you
#currently do not support the feature and as of now, havent released any
#information on how to get it working. This might be useful and from what I
#have done, doesn't look to break any copy-protection drivers.

#1) Compile your 2.4.x kernel to support frame buffer support w/ compiled
#fonts
It's not enough since author doesn't point which framebuffer should be selected
If he mean vesafb - I doesn't work on my PC. (I don't know - why)
If he mean radeonfb - this driver doesn't program tv-out ports (0x880, 0x888, 0x88c)
If he mean atyfb or aty128fb - these cards are incompatible with radeons by tv-out ports range.

Anyway it's not enough to have selected support of framebuffer only in kernels.

#2) Connect your TV to the S-Video Out or Coax port
Probably - THEN BOOT YOUR PC ;)

#3) Setup the LILO Boot to set VGA=3D to the appropriate value or simply pass
#VGA=3DASK to get a list of values, or simply pick from the below list:
After debugging kernel on my radeon VE - I've found that
/linux/arch/i386/video.S returns error code on call of ax=4f0a int 10h for Linux.
(But may be I have something wrong configured).

#Colours   640x480 800x600 1024x768 1280x1024 1600x1200
#--------+---------------------------------------------
#256     |  0301    0303     0305     0307      031C
#32,768  |  0310    0313     0316     0319      031D
#65,536  |  0311    0314     0317     031A      031E
#16.8M   |  0312    0315     0318     031B      031F
VESA's things

#4) Framebuffer support will boot using Linux and you will see command line
#on tv
#5) Download XFree86 3.x w/ FrameBuffer support compiled in (I believe XF86
#4.x w/ FrameBuffer compiled should work as well)
Version number don't matter

#6) Use the following XF86Config Script and type 'startx'
#7) X is now on your TV
;)

------------------BEGIN OF XF86Config------------------

[snip]

#Mode "1280x1024-75"
#    # D: 134.880 MHz, H: 79.905 kHz, V: 74.958 Hz
#    DotClock 134.881
#    HTimings 1280 1344 1456 1688
#    VTimings 1024 1025 1028 1066
#    Flags    "+HSync" "+VSync"    # Warning: XFree86 doesn't support accel
#EndMode
#Mode "1280x1024-60"
#    # D: 107.991 MHz, H: 63.976 kHz, V: 60.015 Hz
#    DotClock 107.992
#    HTimings 1280 1328 1440 1688
#    VTimings 1024 1025 1028 1066
#    Flags    "+HSync" "+VSync"    # Warning: XFree86 doesn't support accel
#EndMode

These modes can't be displayed on TV

[snip]

EndSection

#Section "Device"
#    Identifier "Linux/m68k Frame Buffer Device"
#                      ^^^^
#    VideoRam  2048
#EndSection
This guy have non x86 architecture or something wrong here.

[snip]

Conclusion:

I didn't understand him.
If he has PPC (aka m68k) then as I've understand from linux-console.sf.net
main goal of developing framebuffers is get linux console on non-x86 systems
(There are no neither text-mode nor VESA).
As long ago PPC has VESA?
As I know - neither me nor Ani Joshi still don't implement TV-out support in radeonfb.
But if he mean non radeon chips - there maybe everything ;)
And the last:
For x86 users vo_vesa will be much faster than X11 based on vesafb (because - fastmemcpy at least).


Best regards! Nick