similar to: Individuals interested in VESA memberships?

Looking at both i915 and nouveau DP drivers, both are setting the first LTTPR (if found) in transparent mode first and then in non-transparent mode, just like the DP v2.0 specification mentions in section 3.6.6.1. Being part of the standard, setting the LTTPR in a specific operation mode can be easily moved in the generic framework. So do that by adding a new helper. Then, the msm DP driver is

Looking at both i915 and nouveau DP drivers, both are setting the first LTTPR (if found) in transparent mode first and then in non-transparent mode, just like the DP v2.0 specification mentions in section 3.6.6.1. Being part of the standard, setting the LTTPR in a specific operation mode can be easily moved in the generic framework. So do that by adding a new helper. Then, the msm DP driver is

Looking at both i915 and nouveau DP drivers, both are setting the first LTTPR (if found) in transparent mode first and then in non-transparent mode, just like the DP v2.0 specification mentions in section 3.6.6.1. Being part of the standard, setting the LTTPR in a specific operation mode can be easily moved in the generic framework. So do that by adding a new helper. Then, the msm DP driver is

I just got a new monitor for my desktop system (the old one died after *many* years of service). The new monitor is a high res 16:9 monitor, but the VESA video driver insists on using 1024x768 (which was the resolution of the *old* monitor). It does seem to detect higher, 16:9 resolutions but it is not using them. I *think* I need to set some low-level video mode thing, but it has been a

Well, I got my user back to being able to use his system, but I've still got one issue: it's running on the VESA driver - there is *no* Catalyst build for this monitor, for CentOS 7. From a lot of googling, nothing's been done since the summer of '14 (lspci reports it as a FirePro V3900). Any thoughts, or pointers, as to if/how I can get X - he's running KDE - to see the full

On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote: > According to the DisplayPort standard, LTTPRs have two operating > modes: > - non-transparent - it replies to DPCD LTTPR field specific AUX > requests, while passes through all other AUX requests > - transparent - it passes through all AUX requests. > > Switching between this two modes is done by the DPTX by

Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort 1.4a specification. As the name suggests, these PHY repeaters are capable of adjusting their output for link training purposes. According to the DisplayPort standard, LTTPRs have two operating modes: - non-transparent - it replies to DPCD LTTPR field specific AUX requests, while passes through all other AUX requests -

Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort 1.4a specification. As the name suggests, these PHY repeaters are capable of adjusting their output for link training purposes. According to the DisplayPort standard, LTTPRs have two operating modes: - non-transparent - it replies to DPCD LTTPR field specific AUX requests, while passes through all other AUX requests -

On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote: > +/** > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode > + * @aux: DisplayPort AUX channel > + * @enable: Enable or disable transparent mode > + * > + * Returns 0 on success or a negative error code on failure. > + */ > +int drm_dp_lttpr_set_transparent_mode(struct drm_dp_aux *aux, bool

"H. Peter Anvin" <hpa at zytor.com> writes: > On 06/03/2014 02:59 AM, Ady wrote: > >> Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, >> boot: vesa.c32 >> Undef symbol FAIL: luaL_checklstring >> Failed to load COM32 file vesa.c32 >> boot: >> >> Is there a Lua-related issue? >> >> Is vesa.c32 expecting some kind of

Testing Syslinux 6.03-pre13 in a BIOS 32-bit VM, boot: vesa.c32 Undef symbol FAIL: luaL_checklstring Failed to load COM32 file vesa.c32 boot: Is there a Lua-related issue? Is vesa.c32 expecting some kind of argument? TIA, Ady.

According to the DisplayPort standard, LTTPRs have two operating modes: - non-transparent - it replies to DPCD LTTPR field specific AUX requests, while passes through all other AUX requests - transparent - it passes through all AUX requests. Switching between this two modes is done by the DPTX by issuing an AUX write to the DPCD PHY_REPEATER_MODE register. Add a generic helper that allows

The Vesa driver works fine with CentOS 4.4. I have an NVidia 6200 video adapter. I go to Applications | System Settings | Display | Hardware tab and find my video adapter in the list and set it. The dialog tells me I have to log out for it to take effect, so I duly do that. I then getting a message from a non-graphics screen saying that the attempt to switch to the video adapter failed. When

On Mon, Dec 30, 2024 at 03:18:35PM +0200, Jani Nikula wrote: > On Thu, 26 Dec 2024, Abel Vesa <abel.vesa at linaro.org> wrote: > > On 24-12-11 15:42:27, Johan Hovold wrote: > >> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote: > >> > >> > +/** > >> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode >

On Thu, 26 Dec 2024, Abel Vesa <abel.vesa at linaro.org> wrote: > On 24-12-11 15:42:27, Johan Hovold wrote: >> On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote: >> >> > +/** >> > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode >> > + * @aux: DisplayPort AUX channel >> > + * @enable: Enable or disable

I have noticed anything using ANSI escape sequences to color text does not work if syslinux is in VESA mode. It only works if the \1#, \2#, or \3# are used. This means that libmenu which relies on csprint fails to render colors in VESA mode. I noticed the default color table has a complete table generated at runtime for all VGA color combinations, which csprint also does but from VGA attributes on

On Fri, Jan 03, 2025 at 02:58:17PM +0200, Abel Vesa wrote: > LTTPRs operating modes are defined by the DisplayPort standard and the > generic framework now provides a helper to switch between them, which > is handling the explicit disabling of non-transparent mode and its > disable->enable sequence mentioned in the DP Standard v2.0 section > 3.6.6.1. > > So use the new drm

Jan, List: Is there any way we can compile a kernel to include the VESA Video Modes for 1440x900 resolution so that we can pass grub VGA=867 for 1440x900. This will all me to work in runlevel 3 without the screen resolution being stretched from 1024x768 to 1440x900. The stretch causes everything to be distorted. The necessary VESA modes and numbers are: 1440x900 (dec;

On 24-12-11 15:42:27, Johan Hovold wrote: > On Wed, Dec 11, 2024 at 03:04:12PM +0200, Abel Vesa wrote: > > > +/** > > + * drm_dp_lttpr_set_transparent_mode - set the LTTPR in transparent mode > > + * @aux: DisplayPort AUX channel > > + * @enable: Enable or disable transparent mode > > + * > > + * Returns 0 on success or a negative error code on failure.

LTTPRs operating modes are defined by the DisplayPort standard and the generic framework now provides a helper to switch between them, which is handling the explicit disabling of non-transparent mode and its disable->enable sequence mentioned in the DP Standard v2.0 section 3.6.6.1. So use the new drm generic helper instead as it makes the code a bit cleaner. Acked-by: Imre Deak <imre.deak