search for: scalers

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

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

On Sun, 26 May 2019 at 08:41, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > 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 >

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:

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

Hello, I'm relatively new to R. I've read the intro guide, but I can't quite figure out how to: I have a function: Jcost <- function (theta, in, out) { a <- output - input %*% theta 1/2 * t(a) %*% a } where "theta" is a 2x1 matrix "in" is a 20x2 matrix "out" is a 20x1 matrix return value is a scaler This works well when I only want to

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

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

From: Hans de Goede <hdegoede at redhat.com> [ Upstream commit 37a68eab4cd92b507c9e8afd760fdc18e4fecac6 ] 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

From: Hans de Goede <hdegoede at redhat.com> [ Upstream commit 37a68eab4cd92b507c9e8afd760fdc18e4fecac6 ] 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

From: Hans de Goede <hdegoede at redhat.com> [ Upstream commit 37a68eab4cd92b507c9e8afd760fdc18e4fecac6 ] 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

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, All I am using is.integer function to examine whether an object is an integer or not, but I get such results, > x<-3 > is.integer(x) [1] FALSE > x<-3:4 > x [1] 3 4 > is.integer(x) [1] TRUE Seems that the is.integer cannot handle scalers, > is.integer(5) [1] FALSE > is.integer(5:6) [1] TRUE Is this a bug in R or I made some mistakes? I am using R 2.2.1 under Windows XP Thanks a lot! Leon [[alternative HTML version deleted]]

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 is pre-release of the ATI driver aimed at 7.3. It doesn't contain randr1.2 support it does however contain a major re-write of the output mappings from what was known as Alex's superpatch. Please logs all regressions into bugzilla so we can fix them before the 6.7 release. Adam Jackson: Undo unintended configure.ac change.

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

This patch makes windows zoom in and out of a zero point on create/unmap. I've cleaned up the formatting/style to be consistent with the rest of compiz (eg adding spaces around operators, tabifying, using C style comments). This patch could use some more work. It should only apply to decorated toplevels, but right now it also affects XUL menus (I guess because they are not unmanaged like

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