similar to: making custom function compute/return multiple items

Prefer the parsed results for is_hdmi and has_audio in display info over calling drm_detect_hdmi_monitor() and drm_detect_monitor_audio(), respectively. Conveniently, this also removes the need to use edid_blob_ptr. Cc: Karol Herbst <kherbst at redhat.com> Cc: Lyude Paul <lyude at redhat.com> Cc: Danilo Krummrich <dakr at redhat.com> Cc: nouveau at lists.freedesktop.org

Hello, This is an attempt at providing generic support for underscan connector props. We already have 3 drivers defining the same underscan, underscan vborder and underscan hborder properties (amd, radeon and nouveau) and I am about to add a new one, hence my proposal to put the prop parsing code in the core and add ->underscan fields to drm_connector_state. In this v2, I also converted the

Higher layers tend to add a lot of modes not actually in the EDID, such as the standard DMT modes. Changing this would be extremely intrusive to everyone, so just force the scaler more often. There are no practical cases we're aware of where a LVDS/eDP panel has multiple resolutions exposed, and i915 already does it this way. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110660

On Fri, Jan 12, 2024 at 11:50?AM Jani Nikula <jani.nikula at intel.com> wrote: > > Prefer the parsed results for is_hdmi and has_audio in display info over > calling drm_detect_hdmi_monitor() and drm_detect_monitor_audio(), > respectively. > > Conveniently, this also removes the need to use edid_blob_ptr. > > Cc: Karol Herbst <kherbst at redhat.com> > Cc:

THIS IS UNTESTED for anything other than i915. Use previously parsed EDID where possible for display audio/hdmi detection. This in turn reduces edid_blob_ptr usage in a number of places. Further reduce edid_blob_ptr usage, and document that it should not be used by drivers directly. BR, Jani. Cc: Alain Volmat <alain.volmat at foss.st.com> Cc: Alex Deucher <alexander.deucher at

Hi I think this is mostly a question of preference for my part, but I think it would give an overall better quality feel. What I'm talking about is mostly the movement it uses. As I've come to understand, it uses velocity and direction, and a target point. This means that it updates it velocity and direction every X seconds (timestep), and gives it the possibility to be

https://bugs.freedesktop.org/show_bug.cgi?id=94817 Bug ID: 94817 Summary: Nearest neighbor scaling? Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: enhancement Priority: medium Component: Driver/nouveau Assignee: nouveau at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This release adds some new product names to the list, fixes startup hangs on a couple of GPUs, and adds an option -- AllowDualLinkModes -- to enable validation of dual-link DVI modes. Note that not all GPUs are configured at boot to support dual-link modes, so enable this option at your own risk. - -- Aaron Aaron Plattner (8): Bug #14885:

Place the declaration of struct nouveau_conn_atom above that of struct nouveau_connector. This commit makes no changes to the moved block what so ever, it just moves it up a bit. This is a preparation patch to fix some issues with connector handling on pre nv50 displays (which do not use atomic modesetting). Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

Place the declaration of struct nouveau_conn_atom above that of struct nouveau_connector. This commit makes no changes to the moved block what so ever, it just moves it up a bit. This is a preparation patch to fix some issues with connector handling on pre nv50 displays (which do not use atomic modesetting). Signed-off-by: Hans de Goede <hdegoede at redhat.com> ---

Hi I'm just wondering what the status is on the new movement architecture that I think David mentioned a few months ago. The point was to get more predictable and accurate movement in the plugins. Since the current method recomputes speed and direction every "timestep". So the movemnt is actually computed on the fly, instead of having a predetermined path which is

Dear I am very new to tinc and would like to ask any advice regarding tinc's throughput. I have been using OpenVPN for several years and found tinc as a simpler/scaler VPN using TUN/TAP device. I have tried to use tinc on WindowsXP and measured throughput in contrast to OpenVPN. My test revealed that tinc is faster in PING response (almost half of OpenVPN). However, when I tested with

From: Colin Ian King <colin.king at canonical.com> Currently the uninitialized values in the array reply are printed out when exec is false and nvkm_pmu_send has not updated the array. Avoid confusion by only dumping out these values if they have been actually updated. Detected by CoverityScan, CID#1271291 ("Uninitialized scaler variable") Fixes: ebb58dc2ef8c

When I try to plot two lines ( or scatterplots) with different scales, this is what I have been doing: Suppose: I have y1 and y2 in a very different scale y1 = 1:100 y2 = c(100:1)*10 To plot them on top of each other and denote by different colors: I have to figure out the correct scale '10' and corresponding tick.vector and lables. Then do: plot(1:100, y1) # I can have

Dear listers: I have an idea to do the outlier detection and I need to use R to implement it first. Here I hope I can get some input from all the guru's here. I select distance-based approach--- step 1: calculate the distance of any two rows for a dataframe. considering the scaling among different variables, I choose mahalanobis, using variance as scaler. step 2: Let k be the number of

Hi, I read on http://nouveau.freedesktop.org/wiki/TestersWanted that you're looking for information for the integrated tvout functionality. I'm the author of nvtv, and I know some bits and pieces about that subject, so maybe we can pool efforts. The TV encoder used in the NVidia GPUs may be a Zoran CVE IP core, http://www.zoran.com/products/literature/index.html For the GF4 MX,

A couple of minor points about the odesolve package (which I am otherwise enjoying very much): 1. "scalar" is misspelled as "scaler" in the definitions of the rtol and atol parameters 2. it is possible to crash R by doing something dumb, e.g failing to read the documentation carefully enough and (a) returning only a vector of derivatives and not a list of (derivatives,

On 2018-05-07 12:19 PM, Boris Brezillon wrote: > On Mon, 7 May 2018 18:01:44 +0300 > Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > >> On Mon, May 07, 2018 at 04:44:32PM +0200, Boris Brezillon wrote: >>> We have 3 drivers defining the "underscan", "underscan hborder" and >>> "underscan vborder" properties (radeon, amd

On Mon, May 07, 2018 at 04:44:32PM +0200, Boris Brezillon wrote: > We have 3 drivers defining the "underscan", "underscan hborder" and > "underscan vborder" properties (radeon, amd and nouveau) and we are > about to add the same kind of thing in VC4. > > Define generic underscan props and add new fields to the drm_connector > state so that the

Dear list, I would like to make a comment how to solve the X11 font problem under SuSE Linux (9.0) when you get the message: "X11 font at size 16 could not be loaded". After having modified /etc/X11/XF86config as root (see below) you have to run 'SuSEconfig' as root as well else nothing might be changed in the X-Server. After that no further messages should appear. HTH,