michal Wrote:I have to ask. Why are we using Option "ModeValidation" "NoEdidModes" ??
Isn't this what is causing:
Mode is rejected: Modes from the PIONEER_TV (DFP-1)'s EDID are not allowed.
for ALL the supported HDTV modes of my TV? How can it ever be valid as described in the original post if we're excluding all EDID modes in the config? Or is this only for TV's with broken EDID's? Seems counter intuitive.
Should I be safe in creating modelines from the entries reported by the EDID? If I just let X use the modelines it detects I do not get [email protected] or @60 options in XBMC.
That should only occur in situations where the device is supplying invalid EDID's. It would seem logical to assume the "ModeValidation" setting is generating that specific message. Here is a butchered version of what I found off Google:
Quote:For every possible mode, the mode is run through mode validation. The core of mode validation is still performed similarly to traditional XFree86/X.Org mode validation: the mode timings are checked against things such as the valid HorizSync and VertRefresh ranges and the maximum pixelclock. Note that each individual stage of mode validation can be independently controlled through the "ModeValidation" X configuration option.
Invalid modes are discarded; valid modes are inserted into the mode pool.
As validated modes are inserted into the mode pool, duplicate modes are removed, and the mode pool is sorted, such that the "best" modes are at the beginning of the mode pool.
After the mode pool is built for all display devices, the requested modes (as specified in the X configuration file), are looked up from the mode pool. Each requested mode that can be matched against a mode in the mode pool is then advertised to the X server and is available to the user through the X server's mode switching hotkeys (ctrl-alt-plus/minus) and the XRandR and XF86VidMode X extensions.
The driver is just saying the modes as supplied from EDID aren't valid for one reason or another. Not that the device can't handle that resolution, refresh rate, etc. So long as your device supports said resolution and refresh rate then specifying it in a modeline instead of being supplied by EDID should be ok and then available for use by XBMC.