Mailinglist Archive: radeonhd (699 mails)

< Previous Next >
[radeonhd] xf86-video-radeonhd:initial-randr: 2 commit(s)
  • From: mhopf@xxxxxxxxxxxxxxxxxxxxxx (Matthias Hopf)
  • Date: Fri, 16 Nov 2007 11:35:44 -0800 (PST)
  • Message-id: <20071116193544.6232210096@xxxxxxxxxxxxxxxxxxxxxx>
Reporting from xf86-video-radeonhd: Radeon HD video driver

Please visit:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd
Or get your own copy by using:
git-clone git://anongit.freedesktop.org/xorg/driver/xf86-video-radeonhd

2 commits against initial-randr at df5487f9...:
src/rhd_randr.c | 197 ++++++++++++++++++++++++++++++++++++++++++++------------
1 file changed, 155 insertions(+), 42 deletions(-)


commit dce9ffc402511d0820c0fcdd7228e1f2ce8571fc
Author: Matthias Hopf <mhopf@xxxxxxx>
Date: Fri Nov 16 20:33:40 2007 +0100

Add potential RandR 1.3 output properties.

This adds the following (immutable) properties to every output, as partially
described for discussion in an randrproto.txt diff on xorg-devel:

RANDR_SIGNAL_FORMAT
Type: string
Range/List: unknown VGA TMDS LVDS FBAS SVideo
YPbPr DisplayPort
Signal format / physical protocol format that is used for the
specified output.
A driver MAY change this property of an output if the
underlying hardware indicates a protocol change (e.g. TV
formats).

RANDR_CONNECTOR_TYPE
Type: string
Range/List: unknown VGA DVI DVI-I DVI-A DVI-D HDMI
internal TV TV-FBAS TV-SVideo TV-YPbPr
TV-SCART TV-C4 DisplayPort

Connector type, as far as known to the driver. Values with
dashes (TV-FBAS) describe more specific versions of the base
values (TV). The former SHOULD be used if the connector is not
capable of producing other signal formats. The later SHOULD be
used if the exact connector is unknown, or the connector is a
multi-format connector that is not described otherwise.
'internal' describes laptop-internal (normally LVDS) displays.
'TV' and 'TV-SCART' with signal format 'VGA' are valid
combinations and describe RGB TV signals.

RANDR_CONNECTOR_NUMBER
Type: int32
Range/List: 0-

Outputs that route their signal to the same connector MUST
have the same connector number. Outputs with the same
connector number MUST route their signal to the same
connector, except if it is 0, which indicates unknown
connectivity. 1 is called the primary connector, 2 the
secondary. 3 is often a TV connector, but that is completely
driver / hardware dependent.
Outputs with the same connector number SHOULD have the same
connector type. Meaning and client behavior for mismatching
connector types is undefined at the moment.

RANDR_OUTPUT_NUMBER
Type: int32
Range/List: 0-

A card may route one internal output to several connectors.
Connectors that are driven by the same output cannot be driven
by different Crtcs and are thus only allowed to be used in
clone mode. The driver SHOULD emit an error message and
continue as gracefully as possible if using different Crtcs for
the same internal output is requested.
Internal outputs are numbered from 1, 0 indicates that output
routing is unknown.

diffstat:
src/rhd_randr.c | 145 +++++++++++++++++++++++++++++++++++++++++++++++-----
1 file changed, 132 insertions(+), 13 deletions(-)

gitweb url:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=commit;h=dce9ffc4


commit e4c4c44bd61e72c00a8769ceebc0e3bdc15742b8
Author: Matthias Hopf <mhopf@xxxxxxx>
Date: Fri Nov 16 18:03:18 2007 +0100

Cleanup.

Also documented one of the more exotic error messages.

diffstat:
src/rhd_randr.c | 58 +++++++++++++++++++++++-----------------------------
1 file changed, 26 insertions(+), 32 deletions(-)

gitweb url:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=commit;h=dce9ffc4


--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx

< Previous Next >