On Mon, 19 Jan 2015, Deucher, Alexander wrote:
> > -Original Message-
> > From: Nicholas Mc Guire [mailto:der.herr at hofr.at]
> > Sent: Monday, January 19, 2015 8:11 AM
> > To: Deucher, Alexander
> > Cc: Koenig, Christian; David Airlie; dri-devel at lists.freedesktop.org;
> > linux-
> >
+0100
winsys/radeon: increase the size of buffer cache
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/dbda1
On Sat, Jan 17, 2015 at 08:46:05AM -0500, Rob Clark wrote:
> On Fri, Jan 16, 2015 at 11:06 PM, Daniel Vetter wrote:
> > On Thu, Jan 15, 2015 at 08:46:46AM -0500, Rob Clark wrote:
> >> On Wed, Jan 14, 2015 at 7:55 PM, Daniel Vetter wrote:
> >> > On Tue, Jan 13, 2015 at 05:18:04PM -0500, Stephane V
On Mon, Jan 19, 2015 at 08:40:24AM -0800, Matt Roper wrote:
> On Mon, Jan 19, 2015 at 11:04:04AM +, Chris Wilson wrote:
> > On Mon, Jan 19, 2015 at 11:51:43AM +0100, Daniel Vetter wrote:
> > > There's also an issue in (most) X drivers which exaberates this
> > > issues: When changing the cursor
On Mon, Jan 19, 2015 at 10:45:09AM -0800, Rodrigo Vivi wrote:
> Thanks for the fix.
>
> Tested-by: Rodrigo Vivi
>
> On Mon, Jan 19, 2015 at 8:31 AM, Matt Roper
> wrote:
> > When commiting a plane update where the framebuffer doesn't change, we
> > can skip the prepare_fb/cleanup_fb steps. Thi
Hi,
I just discovered almost 100 of the following entries in my log:
[drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before
interrupt
Those were accumulated in about 12 hours of operation. I also have one that says
i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogu
https://bugzilla.kernel.org/show_bug.cgi?id=91581
Bug ID: 91581
Summary: Desktop freeze: Nouveau still angry after 101 spins
Product: Drivers
Version: 2.5
Kernel Version: 3.18.x, 3.19-rc5
Hardware: All
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=91581
--- Comment #1 from Maxim Britov ---
My mistake, due bugs.freedesktop.org and bugs.freedesktop.org is still same
site.
Right url https://bugs.freedesktop.org/show_bug.cgi?id=87244
--
You are receiving this mail because:
You are watching the assi
https://bugzilla.kernel.org/show_bug.cgi?id=91581
Maxim Britov changed:
What|Removed |Added
URL||https://bugs.freedesktop.or
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20150120/5bdafebd/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=90741
--- Comment #11 from Maarten Lankhorst ---
Created attachment 163871
--> https://bugzilla.kernel.org/attachment.cgi?id=163871&action=edit
Restore old fence wait behavior
Ok the only difference I can see is the fence wait function being differen
On Tue, Jan 20, 2015 at 01:17:10AM -0600, Larry Finger wrote:
> Hi,
>
> I just discovered almost 100 of the following entries in my log:
>
> [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before
> interrupt
>
> Those were accumulated in about 12 hours of operation. I also hav
817721c79774
Libdrm: eca91cf163d50090db36d0b2abbffcff813a2adf
piglit: 25ac42dbd654daee3d5a0cf09a4212c5144eb74b
--
You are receiving this mail because:
You are the assignee for the bug.
------ next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/61e118a4/attachment-0001.html>
On Thu, Jan 15, 2015 at 06:34:21PM -0800, Matt Roper wrote:
> Add a transitional helper for planes' .set_property() entrypoint,
> similar to what we already have for .update_plane() and
> .disable_plane(). This allows drivers that are still in the process of
> transitioning to implement and exerci
On Thu, Jan 15, 2015 at 06:34:22PM -0800, Matt Roper wrote:
> drm_plane_helper_{update,disable} are not specific to primary planes;
> fix some copy/paste summaries to avoid confusion.
>
> Cc: dri-devel at lists.freedesktop.org
> Signed-off-by: Matt Roper
Applied to my topic/atomic-core branch.
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/aba9fbed/attachment.html>
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/ee9d2832/attachment.html>
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/9100b221/attachment.html>
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/dd345681/attachment-0001.html>
From: Thierry Reding
This series converts the Tegra DRM driver to atomic mode-setting. The
size of the is somewhat misleading, because a bunch of preparatory work
is included.
The first patch adds a new function to the clk API that allows checking
that setting a parent clock can succeed. This is
From: Thierry Reding
This new function is similar to clk_set_parent(), except that it doesn't
actually change the parent. It merely checks that the given parent clock
can be a parent for the given clock.
A situation where this is useful is to check that a particular setup is
valid before switchi
From: Thierry Reding
There is no use-case where it would be useful for drivers not to
implement this function and the transitional plane helpers already
require drivers to provide an implementation.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_atomic_helper.c | 2 +-
1 file changed, 1
From: Thierry Reding
In order to prevent drivers from having to perform the same checks over
and over again, add an optional ->atomic_disable callback which the core
calls under the right circumstances.
v2: pass old state and detect edges to avoid calling ->atomic_disable on
already disabled pla
From: Thierry Reding
This callback can be used instead of the legacy ->mode_fixup() and is
passed the CRTC and connector states. It can thus use these states to
validate the modeset and cache values in the state to be used during
the actual modeset.
Signed-off-by: Thierry Reding
---
drivers/gp
From: Thierry Reding
This function is useful to obtain the state of the CRTC that a plane is
being attached to.
Signed-off-by: Thierry Reding
---
include/drm/drm_atomic.h | 21 +
1 file changed, 21 insertions(+)
diff --git a/include/drm/drm_atomic.h b/include/drm/drm_atomi
From: Thierry Reding
All output drivers have open-coded variants of this function, so export
it to remove some code duplication.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 2 +-
drivers/gpu/drm/tegra/drm.h | 1 +
drivers/gpu/drm/tegra/dsi.c | 6 ++
drivers/gpu/drm/t
From: Thierry Reding
When disabling the display controller, stop it and wait for it to become
idle. Doing so ensures that no further accesses to the framebuffer occur
and the buffers can be safely unmapped or freed.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 70
From: Thierry Reding
Previously output drivers would all stop the display controller in their
disable path. However with the transition to atomic modesetting the
display controller needs to be kept running until all planes have been
disabled so that software can properly determine (using VBLANK c
From: Thierry Reding
This structure will be extended using non-framebuffer related callbacks
in subsequent patches, so it should move to a more central location.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 15 +++
drivers/gpu/drm/tegra/drm.h | 4
drivers/g
From: Thierry Reding
The DRM core should take care of disabling all unneeded planes, so there
is no need to do this explicitly.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/gpu/drm/tegra/dc.c b/drivers/g
From: Thierry Reding
The output layer was initially designed to help reduce the amount of
code duplicated in output drivers. An unfortunate side-effect of that
was that it turned into a midlayer and it became difficult to make the
output drivers work without bending over backwards to fit into the
From: Thierry Reding
This is a small helper that performs the basic steps required by all
output drivers to prepare the display controller for use with a given
encoder.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 20
drivers/gpu/drm/tegra/drm.h | 2 ++
From: Thierry Reding
Implement encoder and connector within the RGB driver itself using the
Tegra output helpers rather than using the Tegra output as midlayer. By
doing so one level of indirection is removed and output drivers become
more flexible while keeping the majority of the advantages pro
From: Thierry Reding
Implement encoder and connector within the HDMI driver itself using the
Tegra output helpers rather than using the Tegra output as midlayer. By
doing so one level of indirection is removed and output drivers become
more flexible while keeping the majority of the advantages pr
From: Thierry Reding
Implement encoder and connector within the DSI driver itself using the
Tegra output helpers rather than using the Tegra output as midlayer. By
doing so one level of indirection is removed and output drivers become
more flexible while keeping the majority of the advantages pro
From: Thierry Reding
Implement encoder and connector within the eDP driver itself using the
Tegra output helpers rather than using the Tegra output as midlayer. By
doing so one level of indirection is removed and output drivers become
more flexible while keeping the majority of the advantages pro
From: Thierry Reding
The debugfs cleanup code never fails, so no error is returned. Therefore
the functions can all return void instead.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dsi.c | 12 +++-
drivers/gpu/drm/tegra/hdmi.c | 13 +++--
drivers/gpu/drm/tegra/sor.
From: Thierry Reding
In order to transition output drivers to using the struct tegra_output
as a helper rather than midlayer, make this callback optional. Instead
drivers should implement the equivalent as part of ->mode_fixup(). For
the conversion to atomic modesetting a new callback ->atomic_ch
From: Thierry Reding
The tegra_output midlayer is now completely gone and output drivers use
it purely as a helper library.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 52
drivers/gpu/drm/tegra/drm.h| 39 ---
drivers/gpu/drm/tegra/d
From: Thierry Reding
The tegra_output_exit() and tegra_output_remove() functions cannot fail,
so make them return void.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/drm.h| 4 ++--
drivers/gpu/drm/tegra/dsi.c| 6 +-
drivers/gpu/drm/tegra/hdmi.c | 6 +-
drivers/gp
From: Thierry Reding
Commit 9c0127004ff4 ("drm/tegra: dc: Add powergate support") changed the
driver's ->probe() implementation to deassert the module reset, and with
there being nobody else to assert it until ->remove() there is no need
to deassert again later on.
Signed-off-by: Thierry Reding
From: Thierry Reding
Implement initial atomic state handling. Hook up the CRTCs, planes' and
connectors' ->atomic_destroy_state() callback to ensure that the atomic
state objects don't leak.
Furthermore the CRTC now implements the ->mode_set_nofb() callback that
is used by new helpers to impleme
From: Thierry Reding
Hook up the default ->reset() and ->atomic_duplicate_state() helpers.
This ensures that state objects are properly created and framebuffer
reference counts correctly maintained.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 12
drivers/gpu/d
From: Thierry Reding
Switch out the regular plane helpers for the atomic plane helpers. Also
use the default atomic helpers to implement the ->atomic_check() and
->atomic_commit() callbacks. The driver now exclusively uses the atomic
interfaces.
Signed-off-by: Thierry Reding
---
drivers/gpu/dr
From: Thierry Reding
This allows the clock setup to be separated from the clock programming
and better matches the expectations of the atomic modesetting where no
code paths must fail during modeset.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 76 +++
From: Thierry Reding
The implementation of the ->atomic_check() callback precomputes all
parameters to check if the given configuration can be applied. If so the
precomputed values are stored in the atomic state object for the encoder
and applied during modeset. In that way the modeset no longer
From: Thierry Reding
The implementation of the ->atomic_check() callback precomputes all
parameters to check if the given configuration can be applied. If so the
precomputed values are stored in the atomic state object for the encoder
and applied during modeset. In that way the modeset no longer
From: Thierry Reding
The implementation of the ->atomic_check() callback precomputes all
parameters to check if the given configuration can be applied. If so the
precomputed values are stored in the atomic state object for the encoder
and applied during modeset. In that way the modeset no longer
From: Thierry Reding
The implementation of the ->atomic_check() callback precomputes all
parameters to check if the given configuration can be applied. If so the
precomputed values are stored in the atomic state object for the encoder
and applied during modeset. In that way the modeset no longer
From: Thierry Reding
All clock state is now stored in the display controller's atomic state,
so the output drivers no longer need to call back into the display
controller driver to set up the clock. This is also required to make
sure no hardware changes are made before validating a configuration.
From: Thierry Reding
Replace drm_crtc_helper_set_config() by drm_atomic_helper_set_config().
All drivers have now been converted to use ->atomic_check() to set the
atomic state, therefore the atomic mode setting helpers can be used.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c
From: Thierry Reding
Provide a custom ->atomic_commit() implementation which supports async
commits. The generic atomic page-flip helper can use this to implement
page-flipping.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 129
dr
From: Thierry Reding
All output drivers have now been converted to use the ->atomic_check()
callback, so the ->mode_fixup() callbacks are no longer used.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dsi.c | 87
drivers/gpu/drm/tegra/hdmi
From: Thierry Reding
Wrap struct drm_crtc_state in a driver-specific structure and add the
planes field which keeps track of which planes are updated or disabled
during a modeset. This allows atomic updates of the the display engine
at ->atomic_flush() time.
Signed-off-by: Thierry Reding
---
d
From: Thierry Reding
Previously output drivers would enable continuous display mode and power
up the display controller at various points during the initialization.
This is suboptimal because it accesses display controller registers in
output drivers and duplicates a bit of code.
Move this code
From: Thierry Reding
Tracking these in the plane state allows them to be computed in the
->atomic_check() callback and reused when applying the configuration in
->atomic_update().
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 127 ++--
On Mon, Jan 19, 2015 at 10:35 PM, Javier Martinez Canillas
wrote:
> Hello Thierry,
>
> On 01/19/2015 05:30 PM, Thierry Reding wrote:
>>>
>>> I know you probably are very busy but it would be great if you can take a
>>> look
>>> to this series to avoid another kernel release to be missed since we
On Tue, Jan 20, 2015 at 11:48:23AM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> This callback can be used instead of the legacy ->mode_fixup() and is
> passed the CRTC and connector states. It can thus use these states to
> validate the modeset and cache values in the state to be used
On Tue, Jan 20, 2015 at 11:48:24AM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> This function is useful to obtain the state of the CRTC that a plane is
> being attached to.
>
> Signed-off-by: Thierry Reding
> ---
> include/drm/drm_atomic.h | 21 +
> 1 file change
On Tue, Jan 20, 2015 at 11:48:21AM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> There is no use-case where it would be useful for drivers not to
> implement this function and the transitional plane helpers already
> require drivers to provide an implementation.
>
> Signed-off-by: Thie
On Tue, Jan 20, 2015 at 11:48:22AM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> In order to prevent drivers from having to perform the same checks over
> and over again, add an optional ->atomic_disable callback which the core
> calls under the right circumstances.
>
> v2: pass old st
On Tue, Jan 20, 2015 at 11:48:53AM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Wrap struct drm_crtc_state in a driver-specific structure and add the
> planes field which keeps track of which planes are updated or disabled
> during a modeset. This allows atomic updates of the the displ
https://bugzilla.kernel.org/show_bug.cgi?id=83461
Christian König changed:
What|Removed |Added
Attachment #156211|0 |1
is obsolete|
aps the subject should be updated to something like:
drm/tegra: Track changed planes in CRTC state
?
Thierry
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/bb37a1ae/attachment.sig>
On Tue, Jan 20, 2015 at 5:48 AM, Thierry Reding
wrote:
> From: Thierry Reding
>
> There is no use-case where it would be useful for drivers not to
> implement this function and the transitional plane helpers already
> require drivers to provide an implementation.
>
> Signed-off-by: Thierry Reding
ee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/24dc263d/attachment.html>
HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/da5e2bfa/attachment-0001.html>
https://bugzilla.kernel.org/show_bug.cgi?id=91571
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
https://bugzilla.kernel.org/show_bug.cgi?id=91571
--- Comment #2 from Alex Deucher ---
Both fglrx and radeon support dynamic power management so this does not likely
have anything to do with power management. It looks like a plain old GPU hang.
I'd suggest updating your mesa stack in the case o
On Mon, Jan 19, 2015 at 6:00 AM, Chris Wilson
wrote:
> For BufferAge support, we just have to guarrantee that we were not using
> the DRI2Buffer->flags field for anything else (i.e. it is always 0) and
> then to make sure that we exchange the flags field after buffer
> exchanges. radeon does not
On Sun, Jan 18, 2015 at 10:23 AM, Oded Gabbay wrote:
> From: Ben Goz
>
> Signed-off-by: Ben Goz
> Signed-off-by: Oded Gabbay
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_module.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd
On Tue, Jan 13, 2015 at 6:19 AM, Oded Gabbay wrote:
> This patch-set continues to prepare amdkfd so it could support VI APU. it
> prepares DQM and KQ modules to support more than one ASIC.
>
> Note: there is no change in the IOCTLs.
Series is:
Reviewed-by: Alex Deucher
>
> Oded
>
> Ben
On Thu, Jan 15, 2015 at 5:46 AM, Oded Gabbay wrote:
> This small patch-set fixes a corner-case bug in kernel queue handling, which
> was caused by using a function called sync_with_hw().
>
> The patch-set removes this function, as it is not needed anymore. As a result,
> we need to replace cpu_rel
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/600fead0/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=91571
Alberto Salvia Novella changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Since drm_helper_probe_single_connector_modes_merge_bits() and other
places also update connector->status, the output_poll_execute() and/or
drm_helper_hpd_irq_event() logic can get confused and forget to send
a HPD event.
There are two possible solutions: (1) keep track of state at last HPD
check
On Tue, Jan 20, 2015 at 1:02 PM, Mike Turquette
wrote:
> Quoting Thierry Reding (2015-01-20 02:48:20)
>> From: Thierry Reding
>>
>> This new function is similar to clk_set_parent(), except that it doesn't
>> actually change the parent. It merely checks that the given parent clock
>> can be a par
On 01/19/2015 03:00 AM, Chris Wilson wrote:
> Available since the inclusion of dri2proto 1.4 is a DRI2 request to
> query and set certain parameters about the X/DDX configuration. This
> implements the getter request.
>
> Signed-off-by: Chris Wilson
This patch is
Reviewed-by: Ian Romanick
> -
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/525f71dc/attachment.html>
--- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/f2f02368/attachment.html>
Based on broonie/ASoC
v10:
- add the generic dt-card
- define the audio ports from a DT graph of ports (Russell King)
- reuse HDMI constants (Andrew Jackson - Jyri Sarha)
- alloc rate_constraints in codec (Jyri Sarha)
- fix bad number of channels (Jyri Sarha
Two kinds of ports may be declared in a DT graph of ports: video and audio.
This patch accepts the port value from a video port as an alternative
to the video-ports property.
It also accepts audio ports in the case the transmitter is not used as
a slave encoder.
The new file include/sound/tda998x.h
The device drvdata is used for component bind, but points to the
encoder/connector structure which is hidden from the slave encoder.
For audio extension, the slave encoder private data must be accessible,
so, this patch changes drvdata to the slave encoder private data and
sets it in case of slave
The tda998x CODEC maintains the audio format and rate constraints according
to the HDMI device parameters (EDID) and sets dynamically the input ports
in the TDA998x I2C driver on start/stop audio streaming.
Signed-off-by: Jean-Francois Moine
---
drivers/gpu/drm/i2c/tda998x_drv.c | 124 ++
With I2S input, the CTS_N predivider depends on the audio sample width.
Signed-off-by: Jean-Francois Moine
---
drivers/gpu/drm/i2c/tda998x_drv.c | 21 ++---
include/sound/tda998x.h | 4 +++-
sound/soc/codecs/tda998x.c| 5 +++--
3 files changed, 24 insertions(+
snd_soc_get_dai_name() may be used to define a sound card with
a different syntax from the one of the simple-card.
Signed-off-by: Jean-Francois Moine
---
include/sound/soc.h | 2 ++
sound/soc/soc-core.c | 5 +++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/sound/soc.
To create simple cards, the syntax of the simple-card does not follow
the common binding of the device graphs
(Documentation/devicetree/bindings/graph.txt).
dt-card devices are created by audio controllers with themselves as the
root of the graph. The sound card is created according to the paramet
On 01/19/2015 03:00 AM, Chris Wilson wrote:
> As the SBC from the reply from SwapBuffers is not used immediately and
> can be easily determined by counting the new of SwapBuffers requests
> made by the client, we can defer the synchronisation point to the
> pending GetBuffers round trip. (We force
...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/5b38d045/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=90741
--- Comment #12 from Gustaw Smolarczyk ---
This hack, when applied on top of 3.19-rc5, seems to fix the problem.
--
You are receiving this mail because:
You are watching the assignee of the bug.
eceiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/4936f95c/attachment.html>
u are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/71d9e8f9/attachment.html>
On 01/19/2015 03:00 AM, Chris Wilson wrote:
> Within the DRI2GetBuffers return packet there is a 4-byte field that is
> currently unused by any driver, i.e. flags. With the co-operation of a
> suitably modified X server, we can pass the last SBC on which the buffer
> was defined (i.e. the last Swap
On 01/19/2015 03:00 AM, Chris Wilson wrote:
> Since the introduction of DRI2GetBuffersWithFormat, the old
> DRI2GetBuffers interface would always recreate all buffers all the time
> as it was no longer agnostic to the format value being set by the DDXes.
> This causes an issue with clients intermix
On 01/20/2015 12:35 PM, Ian Romanick wrote:
> On 01/19/2015 03:00 AM, Chris Wilson wrote:
>> + DRI2Buffer *buffers;
>> +
>> + for (i = 0; i < priv->bufferCount; i++)
>> + attachments[i] = priv->buffers[i].attachment;
>> +
>> + buffers = DRI2GetBuffers(priv->base.psc-
On 01/19/2015 03:00 AM, Chris Wilson wrote:
> In order for X/DDX to reuse a driver specific field of the DRI2GetBuffers
> reply, we need to declare the change in semantics. To indicate that the
> flags field now continues the last swap buffers count instead, we
> introduce the has-buffer-age parame
:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150120/0dc9dc2e/attachment.html>
On 01/19/2015 06:29 AM, Chris Wilson wrote:
> Allow mesa/dri2 to implement GLX_EXT_buffer_age by reporting the sbc of
> when the current back buffer was defined. As this may require ddx
> support, only set the value if enabled by the ddx and report the new
> semantics via a DRI2GetParam request.
>
Not a new type exposed to userspace, just a standard way to create
them since between range, bitmask and enum there's 3 different ways to
pull out a boolean prop.
Also add the kerneldoc for the recently added new prop types, which
Rob forgot all about.
Cc: Rob Clark
Signed-off-by: Daniel Vetter
This is the infrastructure for DPMS ported to the atomic world.
Fundamental changes compare to legacy DPMS are:
- No more per-connector dpms state, instead there's just one per each
display pipeline. So if you clone either you have to unclone first
if you only want to switch off one screen, or
1 - 100 of 135 matches
Mail list logo
