Op 11-10-12 21:26, Thomas Hellstrom schreef:
> On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
>
>>
>>> Anyway, if you plan to remove the fence lock and protect it with reserve,
>>> you must
>>> make sure that a waiting reserve is never done in a destruction path. I
>>> think this
>>> mostly
On 10/11/2012 09:26 PM, Thomas Hellstrom wrote:
> On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
> I can't see how the waiting reserve in ttm_bo_cleanup_refs would cause
> a deadlock,
> because the buffer about to be reserved is always *last* in a
> reservation sequence, and the
> reservation
ment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/155b6671/attachment-0001.pgp>
Hi Rob,
On Wednesday 12 September 2012 22:49:47 Rob Clark wrote:
> From: Rob Clark
>
> The 'atomic' mechanism allows for multiple properties to be updated,
> checked, and commited atomically. This will be the basis of atomic-
> modeset and nuclear-pageflip.
>
> The basic flow is:
>
>
On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
>
>> Anyway, if you plan to remove the fence lock and protect it with reserve,
>> you must
>> make sure that a waiting reserve is never done in a destruction path. I
>> think this
>> mostly concerns the nvidia driver.
> Well I don't think any
From: Rob Clark
Replace references to and remove the connector property fxns, which
have been superseded with the more general object property fxns:
+ drm_connector_attach_property -> drm_object_attach_property
+ drm_connector_property_set_value -> drm_object_property_set_value
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i2c/ch7006_drv.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/i2c/ch7006_drv.c b/drivers/gpu/drm/i2c/ch7006_drv.c
index 599099f..b865d07 100644
---
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/udl/udl_connector.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/udl/udl_connector.c
b/drivers/gpu/drm/udl/udl_connector.c
index d568aa4..4faf39c 100644
---
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/shmobile/shmob_drm_crtc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/shmobile/shmob_drm_crtc.c
b/drivers/gpu/drm/shmobile/shmob_drm_crtc.c
index 3ecb702..698b0cd 100644
---
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/radeon/radeon_connectors.c | 62 ++--
1 file changed, 31 insertions(+), 31 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_connectors.c
b/drivers/gpu/drm/radeon/radeon_connectors.c
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/nouveau/nouveau_connector.c | 22 +++---
drivers/gpu/drm/nouveau/nv17_tv.c | 16
2 files changed, 19 insertions(+), 19 deletions(-)
diff --git
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/gma500/cdv_device.c |4 ++--
drivers/gpu/drm/gma500/cdv_intel_dp.c|2 +-
drivers/gpu/drm/gma500/cdv_intel_hdmi.c |6 +++---
drivers/gpu/drm/gma500/cdv_intel_lvds.c | 10 +-
From: Rob Clark
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/intel_display.c |2 +-
drivers/gpu/drm/i915/intel_dp.c |2 +-
drivers/gpu/drm/i915/intel_hdmi.c|2 +-
drivers/gpu/drm/i915/intel_lvds.c|2 +-
drivers/gpu/drm/i915/intel_modes.c |4
From: Rob Clark
It was suggested by Laurent Pinchart to clean up the legacy connector
property functions, as they are no longer needed. This patchset
replaces references to and remove the connector property fxns, which
have been superseded with the more general object property
Op 11-10-12 18:57, Thomas Hellstrom schreef:
> On 10/11/2012 04:50 PM, Maarten Lankhorst wrote:
>> I was trying to clean ttm up a little so my changes would be less invasive,
>> and simplify
>> the code for debuggability. During testing I noticed the following
>> weirdnesses:
>> -
From: Rob Clark
A helper that drivers can use to send vblank event after a pageflip.
If the driver doesn't support proper vblank irq based time/seqn then
just pass -1 for the pipe # to get do_gettimestamp() behavior (since
there are a lot of drivers that don't use
On 10/11/2012 04:50 PM, Maarten Lankhorst wrote:
> I was trying to clean ttm up a little so my changes would be less invasive,
> and simplify
> the code for debuggability. During testing I noticed the following
> weirdnesses:
> - ttm_mem_evict_first ignores no_wait_gpu if the buffer is on the
Daniel Vetter writes:
> On Thu, Oct 11, 2012 at 4:13 PM, Bj?rn Mork wrote:
>> Let me know if you want ot have more details about these warnings.
>> Otherwise I'll just keep ignoring them ;-)
>
> The drm-intel-fixes branch from
> http://cgit.freedesktop.org/~danvet/drm-intel has a patch to fix
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20121011/01eec3e1/attachment.html>
On Thu, Oct 11, 2012 at 4:13 PM, Bj?rn Mork wrote:
> Let me know if you want ot have more details about these warnings.
> Otherwise I'll just keep ignoring them ;-)
The drm-intel-fixes branch from
http://cgit.freedesktop.org/~danvet/drm-intel has a patch to fix some
of the already reported
On Thu, Oct 11, 2012 at 3:19 PM, Rob Clark wrote:
>> Should the documenation be updated to mark those functions as deprecated for
>> new drivers and explain how to handle IRQ (un)registration manually ?
They're not deprecated, since for most drivers they're good enough.
Maybe just make it clear
I was trying to clean ttm up a little so my changes would be less invasive, and
simplify
the code for debuggability. During testing I noticed the following weirdnesses:
- ttm_mem_evict_first ignores no_wait_gpu if the buffer is on the ddestroy list.
If you follow the code, it will effectively
Hi Rob,
Thanks for the patch.
On Monday 08 October 2012 14:50:39 Rob Clark wrote:
> From: Rob Clark
>
> A helper that drivers can use to send vblank event after a pageflip.
> If the driver doesn't support proper vblank irq based time/seqn then
> just pass -1 for the pipe # to get
Hello,
from time to time, I see the following warning on resume:
[ 7022.245347] PM: Syncing filesystems ... done.
[ 7022.271923] PM: Preparing system for mem sleep
[ 7022.324107] [ cut here ]
[ 7022.324154] WARNING: at drivers/gpu/drm/i915/intel_display.c:1225
vel/attachments/20121011/3dea0994/attachment.html>
Hi Hans,
On Thursday 11 October 2012 13:36:45 Hans Verkuil wrote:
> On Thu 11 October 2012 13:34:07 Alan Cox wrote:
> > > The whole purpose of this API is to let DRM and V4L drivers share
> > > buffers for zero-copy pipelines. Unfortunately it is a fact that
> > > several popular DRM drivers are
On Thu, 2012-10-11 at 12:32 +0200, Laurent Pinchart wrote:
> Hi Imre,
>
> On Friday 05 October 2012 16:36:58 Imre Deak wrote:
> > This is needed to make applications depending on vblank/page flip
> > timestamps independent of time ajdustments.
> >
> > I've tested these with an updated
Hi,
On Thu, 2012-10-11 at 12:29 +0200, Laurent Pinchart wrote:
> (CC'ing linux-media)
>
> On Friday 05 October 2012 16:36:58 Imre Deak wrote:
> > This is needed to make applications depending on vblank/page flip
> > timestamps independent of time ajdustments.
>
> We're in the process to
On Thu 11 October 2012 13:36:45 Hans Verkuil wrote:
> On Thu 11 October 2012 13:34:07 Alan Cox wrote:
> > > The whole purpose of this API is to let DRM and V4L drivers share buffers
> > > for
> > > zero-copy pipelines. Unfortunately it is a fact that several popular DRM
> > > drivers
> > > are
On Wednesday 05 September 2012 15:27:24 Daniel Vetter wrote:
> On Wed, Sep 05, 2012 at 01:53:44AM +, Liu, Chuansheng wrote:
> > This patch is for introducing the irq thread support in drm_irq.
> >
> > Why we need irq thread in drm_irq code?
> > In our GPU system, the gpu interrupt handler
On Thu 11 October 2012 13:34:07 Alan Cox wrote:
> > The whole purpose of this API is to let DRM and V4L drivers share buffers
> > for
> > zero-copy pipelines. Unfortunately it is a fact that several popular DRM
> > drivers
> > are closed source. So we have a choice between keeping the export
Hi David,
On Thursday 11 October 2012 12:41:43 David Herrmann wrote:
> On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart wrote:
> > Hi David,
> >
> > Would you have time to document the master_set operation in
> > Documentation/DocBook/drm.tmpl ? :-)
>
> I have actually some drafts for
Hi Kristian,
Could you please update Documentation/DocBook/drm.tmpl with render nodes
documentation ?
On Friday 28 September 2012 12:35:56 Kristian H?gsberg wrote:
> Here's the patch to implement render nodes as discussed in the "DRM2"
> talk at XDC:
>
>
>> On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox
>> wrote:
>> > On Wed, 10 Oct 2012 08:56:32 -0700
>> > Robert Morell wrote:
>> >
>> >> EXPORT_SYMBOL_GPL is intended to be used for "an internal implementation
>> >> issue, and not really an interface". The dma-buf infrastructure is
>> >> explicitly
Hi Laurent
On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart
wrote:
> Hi David,
>
> Would you have time to document the master_set operation in
> Documentation/DocBook/drm.tmpl ? :-)
I have actually some drafts for "drmSetMaster/drmDropMaster" man-pages
for libdrm on my machine. However, I am
nced we would like to start using it.
> -Chad
>
--
// Tapani
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/50da2ddf/attachment-0001.pgp>
> > So, developers implicitly or explicitly copied in this thread that might be
> > considering the usage of dmabuf on proprietary drivers should consider
> > this email as a formal notification of my viewpoint: e. g. that I consider
> > any attempt of using DMABUF or media core/drivers together
Hi David,
Would you have time to document the master_set operation in
Documentation/DocBook/drm.tmpl ? :-)
On Sunday 07 October 2012 19:53:26 David Herrmann wrote:
> We link every DRM "file_priv" to a "drm_master" structure. Currently, the
> drmSetMaster() call returns 0 when there is _any_
> The whole purpose of this API is to let DRM and V4L drivers share buffers for
> zero-copy pipelines. Unfortunately it is a fact that several popular DRM
> drivers
> are closed source. So we have a choice between keeping the export symbols GPL
> and forcing those closed-source drivers to make
Hi Imre,
On Friday 05 October 2012 16:36:58 Imre Deak wrote:
> This is needed to make applications depending on vblank/page flip
> timestamps independent of time ajdustments.
>
> I've tested these with an updated intel-gpu-test/flip_test and will send
> the update for that once there's no
> As long as dmabuf uses EXPORT_SYMBOL_GPL that is definitely correct. Does your
> statement also hold if dmabuf would use EXPORT_SYMBOL? (Just asking)
Yes. The GPL talks about derivative works (as does copyright law).
Alan
(CC'ing linux-media)
On Friday 05 October 2012 16:36:58 Imre Deak wrote:
> This is needed to make applications depending on vblank/page flip
> timestamps independent of time ajdustments.
We're in the process to switching to CLOCK_MONOTONIC timestamps in V4L2. The
reason why we're using
Em Thu, 11 Oct 2012 08:47:15 -0500
Rob Clark escreveu:
> On Thu, Oct 11, 2012 at 6:13 AM, Mauro Carvalho Chehab
> wrote:
> > Em Thu, 11 Oct 2012 09:20:12 +0200
> > Hans Verkuil escreveu:
> >
> >> > my understaning is
> >> > that the drivers/media/ authors should also ack with this licensing
>
;
>> include $(LOCAL_PATH)/intel/Android.mk
>>
>
--
// Tapani
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/9eebd7e2/attachment.pgp>
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/a919d792/attachment.html>
Op 11-10-12 09:51, Hans Verkuil schreef:
>>> my understaning is
>>> that the drivers/media/ authors should also ack with this licensing
>>> (possible) change. I am one of the main contributors there. Alan also has
>>> copyrights there, and at other parts of the Linux Kernel, including the
>>>
Hello Ben Skeggs,
The patch ebb945a94bba: "drm/nouveau: port all engines to new engine
module format" from Jul 20, 2012, leads to the following warning:
drivers/gpu/drm/nouveau/nouveau_abi16.c:264
nouveau_abi16_ioctl_channel_alloc()
warn: should '1 << init->channel' be a 64 bit type
On Thu 11 October 2012 09:20:12 Hans Verkuil wrote:
> On Thu October 11 2012 03:11:19 Mauro Carvalho Chehab wrote:
> > Em Thu, 11 Oct 2012 09:22:34 +1000
> > Dave Airlie escreveu:
> >
> > > On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox
> > > wrote:
> > > > On Wed, 10 Oct 2012 08:56:32 -0700
> > >
On Thu, Oct 11, 2012 at 9:19 AM, Laurent Pinchart
wrote:
> Hi Rob,
>
> Thanks for the patch.
>
> On Monday 08 October 2012 14:50:39 Rob Clark wrote:
>> From: Rob Clark
>>
>> A helper that drivers can use to send vblank event after a pageflip.
>> If the driver doesn't support proper vblank irq
On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox wrote:
> On Wed, 10 Oct 2012 08:56:32 -0700
> Robert Morell wrote:
>
>> EXPORT_SYMBOL_GPL is intended to be used for "an internal implementation
>> issue, and not really an interface". The dma-buf infrastructure is
>> explicitly intended as an interface
On Thu October 11 2012 03:11:19 Mauro Carvalho Chehab wrote:
> Em Thu, 11 Oct 2012 09:22:34 +1000
> Dave Airlie escreveu:
>
> > On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox
> > wrote:
> > > On Wed, 10 Oct 2012 08:56:32 -0700
> > > Robert Morell wrote:
> > >
> > >> EXPORT_SYMBOL_GPL is intended
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/5b367a0c/attachment.html>
On Wed October 10 2012 23:02:06 Rob Clark wrote:
> On Wed, Oct 10, 2012 at 1:17 PM, Alan Cox wrote:
> > On Wed, 10 Oct 2012 08:56:32 -0700
> > Robert Morell wrote:
> >
> >> EXPORT_SYMBOL_GPL is intended to be used for "an internal implementation
> >> issue, and not really an interface". The
On Thu, Oct 11, 2012 at 6:13 AM, Mauro Carvalho Chehab
wrote:
> Em Thu, 11 Oct 2012 09:20:12 +0200
> Hans Verkuil escreveu:
>
>> > my understaning is
>> > that the drivers/media/ authors should also ack with this licensing
>> > (possible) change. I am one of the main contributors there. Alan
art --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/dd447ae2/attachment.html>
On Thu, Oct 11, 2012 at 7:07 AM, Laurent Pinchart
wrote:
> On Wednesday 05 September 2012 15:27:24 Daniel Vetter wrote:
>> On Wed, Sep 05, 2012 at 01:53:44AM +, Liu, Chuansheng wrote:
>> > This patch is for introducing the irq thread support in drm_irq.
>> >
>> > Why we need irq thread in
Em Thu, 11 Oct 2012 09:20:12 +0200
Hans Verkuil escreveu:
> > my understaning is
> > that the drivers/media/ authors should also ack with this licensing
> > (possible) change. I am one of the main contributors there. Alan also has
> > copyrights there, and at other parts of the Linux Kernel,
g/archives/dri-devel/attachments/20121011/59441c92/attachment.html>
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/f6a27a6b/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20121011/e365f9a5/attachment.html>
Hello Ben Skeggs,
The patch ebb945a94bba: drm/nouveau: port all engines to new engine
module format from Jul 20, 2012, leads to the following warning:
drivers/gpu/drm/nouveau/nouveau_abi16.c:264
nouveau_abi16_ioctl_channel_alloc()
warn: should '1 init-channel' be a 64 bit type
262
On Wed October 10 2012 23:02:06 Rob Clark wrote:
On Wed, Oct 10, 2012 at 1:17 PM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
On Wed, 10 Oct 2012 08:56:32 -0700
Robert Morell rmor...@nvidia.com wrote:
EXPORT_SYMBOL_GPL is intended to be used for an internal implementation
issue, and not
On Thu October 11 2012 03:11:19 Mauro Carvalho Chehab wrote:
Em Thu, 11 Oct 2012 09:22:34 +1000
Dave Airlie airl...@gmail.com escreveu:
On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
On Wed, 10 Oct 2012 08:56:32 -0700
Robert Morell rmor...@nvidia.com wrote:
On Thu 11 October 2012 09:20:12 Hans Verkuil wrote:
On Thu October 11 2012 03:11:19 Mauro Carvalho Chehab wrote:
Em Thu, 11 Oct 2012 09:22:34 +1000
Dave Airlie airl...@gmail.com escreveu:
On Thu, Oct 11, 2012 at 4:17 AM, Alan Cox a...@lxorguk.ukuu.org.uk
wrote:
On Wed, 10 Oct
https://bugs.freedesktop.org/show_bug.cgi?id=55047
--- Comment #1 from Chris Wilson ch...@chris-wilson.co.uk ---
Created attachment 68428
-- https://bugs.freedesktop.org/attachment.cgi?id=68428action=edit
dmesg drm.debug=6
--
You are receiving this mail because:
You are the assignee for the
On 10/10/2012 08:01 PM, Chad Versace wrote:
Is the only difference between v2 and v1 of this patch the removal of the
Change-ID tag?
yep that is the diff (sorry for not noting it), there is the v3 as well
where I've removed the [] comment per Oliver's suggestion.
On 10/08/2012 02:23 AM,
Op 11-10-12 09:51, Hans Verkuil schreef:
my understaning is
that the drivers/media/ authors should also ack with this licensing
(possible) change. I am one of the main contributors there. Alan also has
copyrights there, and at other parts of the Linux Kernel, including the
driver's
core,
https://bugs.freedesktop.org/show_bug.cgi?id=55047
--- Comment #2 from Daniel Vetter dan...@ffwll.ch ---
Created attachment 68431
-- https://bugs.freedesktop.org/attachment.cgi?id=68431action=edit
fixup ch7 get hw state callback
Let's hope this works ...
--
You are receiving this mail
On 10/10/2012 08:05 PM, Chad Versace wrote:
On 10/07/2012 10:50 PM, Tapani Pälli wrote:
Upstreaming old set of patches here to enable Android support in libdrm.
Some little rebasing was required for the first one.
Chad Versace (2):
libdrm,intel: Factor source file lists into sources.mk
(CC'ing linux-media)
On Friday 05 October 2012 16:36:58 Imre Deak wrote:
This is needed to make applications depending on vblank/page flip
timestamps independent of time ajdustments.
We're in the process to switching to CLOCK_MONOTONIC timestamps in V4L2. The
reason why we're using
Hi Imre,
On Friday 05 October 2012 16:36:58 Imre Deak wrote:
This is needed to make applications depending on vblank/page flip
timestamps independent of time ajdustments.
I've tested these with an updated intel-gpu-test/flip_test and will send
the update for that once there's no objection
Hi David,
Would you have time to document the master_set operation in
Documentation/DocBook/drm.tmpl ? :-)
On Sunday 07 October 2012 19:53:26 David Herrmann wrote:
We link every DRM file_priv to a drm_master structure. Currently, the
drmSetMaster() call returns 0 when there is _any_ active
Hi Laurent
On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi David,
Would you have time to document the master_set operation in
Documentation/DocBook/drm.tmpl ? :-)
I have actually some drafts for drmSetMaster/drmDropMaster man-pages
for libdrm on
This patch adds drm-exynos and drm-exynos-hdmi device registration to the
drm driver. It was happening in machine init code earlier which is not
acceptable for dt enabled platforms.
Patch which cleans the respective code from arch/arm is arm: exynos:
removing exynos-drm device registration from
This patch moved the exynos-drm platform device registration to the drm driver.
When DT is enabled, platform devices needs to be registered within the driver
code. This patch fits the requirement of both DT and Non DT based drm drivers.
Signed-off-by: Rahul Sharma rahul.sha...@samsung.com
---
Hi Kristian,
Could you please update Documentation/DocBook/drm.tmpl with render nodes
documentation ?
On Friday 28 September 2012 12:35:56 Kristian Høgsberg wrote:
Here's the patch to implement render nodes as discussed in the DRM2
talk at XDC:
Hi David,
On Thursday 11 October 2012 12:41:43 David Herrmann wrote:
On Thu, Oct 11, 2012 at 12:35 PM, Laurent Pinchart wrote:
Hi David,
Would you have time to document the master_set operation in
Documentation/DocBook/drm.tmpl ? :-)
I have actually some drafts for
https://bugs.freedesktop.org/show_bug.cgi?id=55047
--- Comment #3 from Chris Wilson ch...@chris-wilson.co.uk ---
Created attachment 68433
-- https://bugs.freedesktop.org/attachment.cgi?id=68433action=edit
After dvo get_state patch.
Doesn't appear to be the solution. :(
--
You are receiving
Hi,
On Thu, 2012-10-11 at 12:29 +0200, Laurent Pinchart wrote:
(CC'ing linux-media)
On Friday 05 October 2012 16:36:58 Imre Deak wrote:
This is needed to make applications depending on vblank/page flip
timestamps independent of time ajdustments.
We're in the process to switching to
So, developers implicitly or explicitly copied in this thread that might be
considering the usage of dmabuf on proprietary drivers should consider
this email as a formal notification of my viewpoint: e. g. that I consider
any attempt of using DMABUF or media core/drivers together with
On Thu 11 October 2012 13:34:07 Alan Cox wrote:
The whole purpose of this API is to let DRM and V4L drivers share buffers
for
zero-copy pipelines. Unfortunately it is a fact that several popular DRM
drivers
are closed source. So we have a choice between keeping the export symbols
On Wednesday 05 September 2012 15:27:24 Daniel Vetter wrote:
On Wed, Sep 05, 2012 at 01:53:44AM +, Liu, Chuansheng wrote:
This patch is for introducing the irq thread support in drm_irq.
Why we need irq thread in drm_irq code?
In our GPU system, the gpu interrupt handler need some
On Thu 11 October 2012 13:36:45 Hans Verkuil wrote:
On Thu 11 October 2012 13:34:07 Alan Cox wrote:
The whole purpose of this API is to let DRM and V4L drivers share buffers
for
zero-copy pipelines. Unfortunately it is a fact that several popular DRM
drivers
are closed source. So
Hi Hans,
On Thursday 11 October 2012 13:36:45 Hans Verkuil wrote:
On Thu 11 October 2012 13:34:07 Alan Cox wrote:
The whole purpose of this API is to let DRM and V4L drivers share
buffers for zero-copy pipelines. Unfortunately it is a fact that
several popular DRM drivers are closed
On Thu, Oct 11, 2012 at 7:07 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
On Wednesday 05 September 2012 15:27:24 Daniel Vetter wrote:
On Wed, Sep 05, 2012 at 01:53:44AM +, Liu, Chuansheng wrote:
This patch is for introducing the irq thread support in drm_irq.
Why we
Em Thu, 11 Oct 2012 09:20:12 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
my understaning is
that the drivers/media/ authors should also ack with this licensing
(possible) change. I am one of the main contributors there. Alan also has
copyrights there, and at other parts of the Linux
On Thu, Oct 11, 2012 at 6:13 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
Em Thu, 11 Oct 2012 09:20:12 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
my understaning is
that the drivers/media/ authors should also ack with this licensing
(possible) change. I am one of the main
Hi Rob,
Thanks for the patch.
On Monday 08 October 2012 14:50:39 Rob Clark wrote:
From: Rob Clark r...@ti.com
A helper that drivers can use to send vblank event after a pageflip.
If the driver doesn't support proper vblank irq based time/seqn then
just pass -1 for the pipe # to get
On Thu, Oct 11, 2012 at 9:19 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Rob,
Thanks for the patch.
On Monday 08 October 2012 14:50:39 Rob Clark wrote:
From: Rob Clark r...@ti.com
A helper that drivers can use to send vblank event after a pageflip.
If the driver
I was trying to clean ttm up a little so my changes would be less invasive, and
simplify
the code for debuggability. During testing I noticed the following weirdnesses:
- ttm_mem_evict_first ignores no_wait_gpu if the buffer is on the ddestroy list.
If you follow the code, it will effectively
https://bugs.freedesktop.org/show_bug.cgi?id=55047
Daniel Vetter dan...@ffwll.ch changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |dan...@ffwll.ch
On Thu, Oct 11, 2012 at 3:19 PM, Rob Clark robdcl...@gmail.com wrote:
Should the documenation be updated to mark those functions as deprecated for
new drivers and explain how to handle IRQ (un)registration manually ?
They're not deprecated, since for most drivers they're good enough.
Maybe just
On Thu, Oct 11, 2012 at 4:13 PM, Bjørn Mork bj...@mork.no wrote:
Let me know if you want ot have more details about these warnings.
Otherwise I'll just keep ignoring them ;-)
The drm-intel-fixes branch from
http://cgit.freedesktop.org/~danvet/drm-intel has a patch to fix some
of the already
On 10/11/2012 04:50 PM, Maarten Lankhorst wrote:
I was trying to clean ttm up a little so my changes would be less invasive, and
simplify
the code for debuggability. During testing I noticed the following weirdnesses:
- ttm_mem_evict_first ignores no_wait_gpu if the buffer is on the ddestroy
On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
Anyway, if you plan to remove the fence lock and protect it with reserve, you
must
make sure that a waiting reserve is never done in a destruction path. I think
this
mostly concerns the nvidia driver.
Well I don't think any lock should ever
On 10/11/2012 09:26 PM, Thomas Hellstrom wrote:
On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
I can't see how the waiting reserve in ttm_bo_cleanup_refs would cause
a deadlock,
because the buffer about to be reserved is always *last* in a
reservation sequence, and the
reservation is
On Mon, Oct 08, 2012 at 09:49:21AM +0200, Steffen Trumtrar wrote:
On Mon, Oct 08, 2012 at 10:07:45AM +0300, Tomi Valkeinen wrote:
On Thu, 2012-10-04 at 19:59 +0200, Steffen Trumtrar wrote:
[...]
+
+ disp-num_timings = 0;
+
+ for_each_child_of_node(timings_np, entry) {
+
On Thu, Oct 11, 2012 at 9:34 PM, Alan Cox a...@lxorguk.ukuu.org.uk wrote:
The whole purpose of this API is to let DRM and V4L drivers share buffers for
zero-copy pipelines. Unfortunately it is a fact that several popular DRM
drivers
are closed source. So we have a choice between keeping the
Op 11-10-12 21:26, Thomas Hellstrom schreef:
On 10/11/2012 08:42 PM, Maarten Lankhorst wrote:
Anyway, if you plan to remove the fence lock and protect it with reserve,
you must
make sure that a waiting reserve is never done in a destruction path. I
think this
mostly concerns the nvidia
1 - 100 of 120 matches
Mail list logo