search for: dfps

Displaying 10 results from an estimated 10 matches for "dfps".

Did you mean: deps
2020 Aug 20
2
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
...ed, by also handling the DP_DETAILED_CAP_INFO_AVAILABLE=0/1 cases. The wording is a bit unclear, but as I understand the Standard only calls for the above: """ A DP upstream device shall read the capability from DPCD Addresses 00080h through 00083h. A DP Branch device with multiple DFPs shall report the detailed capability information of the lowest DFP number to which a downstream device is connected, consistent with the DisplayID or legacy EDID access routing policy of an SST-only DP Branch device as described in Section 2.1.4.1. """ > > From section 5.3.3....
2016 Dec 19
0
[ANNOUNCE] xf86-video-qxl 0.1.5
...upport for a --numheads option to the Xspice script. XSpice: allow the udcs socket to be specified, rather than hard coded. Revise Xspice --auto to use a temporary directory. XSpice: auto generate temp files for the vdagent process. Provide an implementation for put_image in dfps mode. Optimize dfps mode to send updates only for the primary pixmap. Marc-André Lureau (2): kms: initialize primary surface to screen virtual size kms: do not overwrite screen virtualX/Y Owen W. Taylor (1): Check for either xfont.pc or xfont2.pc Uri Lublin (1): uxa...
2020 Aug 21
0
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
...ng any real problems as of now > > The wording is a bit unclear, but as I understand the Standard only > calls for the above: > > """ > A DP upstream device shall read the capability from DPCD Addresses 00080h > through 00083h. A DP Branch device with multiple DFPs shall report the > detailed > capability information of the lowest DFP number to which a downstream device > is connected, consistent with the DisplayID or legacy EDID access routing > policy > of an SST-only DP Branch device as described in Section 2.1.4.1. > """...
2020 Aug 19
3
[RFC 13/20] drm/i915/dp: Extract drm_dp_downstream_read_info()
On Tue, Aug 11, 2020 at 04:04:50PM -0400, Lyude Paul wrote: > We're going to be doing the same probing process in nouveau for > determining downstream DP port capabilities, so let's deduplicate the > work by moving i915's code for handling this into a shared helper: > drm_dp_downstream_read_info(). > > Note that when we do this, we also do make some functional
2014 Dec 09
2
DCB 4.1 spec update
On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: >> Hi, > Hey Andy, > >> >> The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. >> I've posted an updated DCB spec here: >> >>
2014 Dec 14
1
DCB 4.1 spec update
...NONE, so you'll need > to program NV_PDISP_CLK_REM_LINK_CTRL to drive any SORs not set up by > the VBIOS. > > Looking at the DCB spec, bits 24-27 in the Display Path Information > entry will indicate which Macro the entry is talking about: > > For Internal and External DFPs we can use any of the available SORs > but the Pad Macro is fixed per Device Entry. > Bit 0 = Pad Macro 0 (Pad Links A and B) > Bit 1 = Pad Macro 1 (Pad Links C and D) > Bit 2 = Pad Macro 2 (Pad Links E and F) > Bit 3 = Pad Macro 3 (Pad Link G) &gt...
2014 Dec 13
0
DCB 4.1 spec update
...ink to SOR Sublink assignment is NONE, so you'll need to program NV_PDISP_CLK_REM_LINK_CTRL to drive any SORs not set up by the VBIOS. Looking at the DCB spec, bits 24-27 in the Display Path Information entry will indicate which Macro the entry is talking about: For Internal and External DFPs we can use any of the available SORs but the Pad Macro is fixed per Device Entry. Bit 0 = Pad Macro 0 (Pad Links A and B) Bit 1 = Pad Macro 1 (Pad Links C and D) Bit 2 = Pad Macro 2 (Pad Links E and F) Bit 3 = Pad Macro 3 (Pad Link G) (AIUI, only one bit will be...
2020 Jul 07
3
[PATCH][next] drm/nouveau: Use fallthrough pseudo-keyword
...4 --- a/drivers/gpu/drm/nouveau/nouveau_connector.c +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c @@ -331,7 +331,7 @@ nouveau_conn_attach_properties(struct drm_connector *connector) case DRM_MODE_CONNECTOR_VGA: if (disp->disp.object.oclass < NV50_DISP) break; /* Can only scale on DFPs. */ - /* Fall-through. */ + fallthrough; default: drm_object_attach_property(&connector->base, dev->mode_config. scaling_mode_property, @@ -446,7 +446,7 @@ nouveau_connector_ddc_detect(struct drm_connector *connector) case DCB_OUTPUT_LVDS: switcheroo_ddc = !!(vga_sw...
2020 Jul 08
0
[PATCH][next] drm/nouveau: Use fallthrough pseudo-keyword
...rivers/gpu/drm/nouveau/nouveau_connector.c > @@ -331,7 +331,7 @@ nouveau_conn_attach_properties(struct drm_connector *connector) > case DRM_MODE_CONNECTOR_VGA: > if (disp->disp.object.oclass < NV50_DISP) > break; /* Can only scale on DFPs. */ > - /* Fall-through. */ > + fallthrough; > default: > drm_object_attach_property(&connector->base, dev->mode_config. > scaling_mode_property, > @@ -446,7 +446,7 @@ nouveau_...
2008 Jun 12
0
[ANNOUNCE] xf86-video-ati 6.8.191
...location of scissor regs AVIVO: make sure we select the right LUT for each crtc R300/R400: bump up the clip limits for textured video R300: fix up magic numbers in fragment program R500: fragment program clean up and magic number conversion AVIVO: disable dithering on DFPs RS6xx: fix typos in previous commit RS6xx: rework output parsing AVIVO: save/restore scaler regs fix off-by-one in last commit R5xx: fix register count when sending fragment program for textured video AVIVO: disable pageflipping on avivo chips until we have prope...