30990
|
1 framebuffer driver for ATI Radeon chipset video boards
|
|
2 ======================================================
|
22691
|
3
|
|
4 These files are replacement for linux-2.4.x-ac.y drivers.
|
|
5 To use this driver you should have at least linux-2.4.5-ac.1
|
|
6 then simply replace linux/drivers/video/radeon* with files
|
|
7 from this directory.
|
|
8 Note: since linux-2.4.10 this driver was moved from -ac to
|
|
9 Linus distribution.
|
|
10
|
|
11 Alternative way:
|
|
12 ~~~~~~~~~~~~~~~~
|
|
13 Simply type two commands in this directory:
|
|
14 make
|
|
15 make install
|
|
16
|
|
17 Anyway you should have 'framebuffer support' compiled into linux-kernel
|
|
18 and at least '8bpp packed pixel support' compiled and installed as module.
|
|
19 (But if you plan to use this module with MPlayer you also should have
|
|
20 16bpp, 24bpp and 32bpp pixel support compiled as modules).
|
|
21
|
|
22
|
|
23 Radeon video overlay
|
30990
|
24 ====================
|
22691
|
25
|
|
26 It was designed for MPlayer and currently can be used only by MPlayer.
|
|
27 It's RGB-YUV BES for Radeon cards (althrough there is experimental
|
|
28 support for Rage128 / Rage128pro chips).
|
|
29
|
|
30 rage128_vid is contained within radeon_vid.c. As for a Rage128 framebuffer -
|
|
31 use the one from your Linux distribution.
|
|
32
|
|
33 Installation:
|
|
34 ~~~~~~~~~~~~~
|
|
35
|
|
36 Simply type two commands in this directory:
|
|
37 make
|
|
38 make install
|
|
39
|
|
40 Using with MPlayer:
|
|
41 ~~~~~~~~~~~~~~~~~~~
|
|
42
|
|
43 Currently there is only one way to use ATI's drivers:
|
|
44 mplayer -vo vesa:lvo:/dev/radeon_vid -<your vesa's options> filename
|
|
45 or
|
|
46 mplayer -vo vesa:lvo:/dev/rage128_vid -<your vesa's options> filename
|
|
47
|
|
48 For YV12 formats you can use also:
|
|
49 mplayer -vo mga:/dev/radeon_vid -<your mga's option> filename
|
|
50
|
|
51 but in this case you should load at least radeonfb driver from
|
|
52 this package.
|
|
53
|
|
54 Configuring:
|
|
55 ~~~~~~~~~~~~
|
|
56
|
|
57 You can tune some parameters with the following trick:
|
|
58 echo "parameter=value" > /dev/radeon_vid
|
|
59 Example (disables adaptive deinterlacing):
|
|
60 echo "deinterlace=off" > /dev/radeon_vid
|
|
61
|
|
62 To know more about these parameters - try reading the /dev/radeon_vid file ;)
|
|
63 For example:
|
|
64 cat /dev/radeon_vid
|
|
65
|
|
66 List of parameters:
|
|
67 ~~~~~~~~~~~~~~~~~~~
|
|
68 If you have Rage128 chip:
|
|
69 brightness=decval (-64:+63) changes brightness
|
|
70 saturation=decval (0:+31) changes saturation 0 == grayscale mode
|
|
71 else - if you have Radeon:
|
|
72 brightness=decval (-1000:+1000) -1000 == black screen
|
|
73 saturation=decval (-1000:+1000) -1000 == grayscaled mode
|
|
74 contrast=decval (-1000:+1000) -1000 == black screen
|
|
75 hue=decval (-1000:+1000) -1000 == +1000 (full circle)
|
|
76 all other values are within this range
|
|
77 Note: 0 is the default value for every parameter on Radeons.
|
|
78 WARNING: This driver violates the rule: "no float in the kernel".
|
|
79 So if you have problems then don't use color correction.
|
|
80
|
|
81 double_buff=on/off enables/disables double buffering
|
|
82 deinterlace=on/off enables/disables adaptive deinterlacing
|
|
83 deinterlace_pattern=hexval defines deinterlacing pattern
|
|
84
|
|
85 Driver parameters:
|
|
86 ~~~~~~~~~~~~~~~~~~
|
|
87
|
|
88 You can use some additional parameters during module loading:
|
|
89 Example:
|
|
90 modprobe radeon_vid swap_fourcc=1
|
|
91
|
|
92 List of driver parameters:
|
|
93 ~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
94 mtrr=1/0 Configures MTRR (if available), default = 1.
|
|
95 swap_fourcc=1/0 Performs byte swapping of passed fourcc.
|
30990
|
96 (It's required for compatibility with -vo mga.)
|
22691
|
97
|
|
98 To know more about driver parameters execute:
|
|
99 modinfo radeon_vid
|
|
100 or
|
|
101 modinfo rage128_vid
|
|
102
|
|
103 Note:
|
|
104 ~~~~~
|
|
105 For command line of MPlayer:
|
|
106 You can pass only options with can be recognized by vo_vesa driver.
|
|
107 (Indeed radeon_vid and rage128_vid are stupid things and can only create
|
|
108 video overlay. Mode switching and other adjustments are performed by the
|
|
109 vo_vesa driver. This mean that they use the VESA BIOS as graphics server.)
|
|
110
|
|
111 Conclusion:
|
|
112 ~~~~~~~~~~~
|
|
113 This stuff (radeon(rage128)_vid) currently doesn't support any standards.
|
|
114
|
|
115 Full example:
|
|
116 ~~~~~~~~~~~~~
|
|
117 modprobe radeon_vid mtrr=1
|
|
118 echo "deinterlace_pattern=F0055555" > /dev/radeon_vid
|
|
119 mplayer -vo vesa:lvo:/dev/radeon_vid -fs -zoom -bpp 32 filename
|
|
120
|
|
121 Enjoy!
|