Got this lockdep warning straightaway during boot:
[7.435890] =
[7.435891] [ INFO: possible recursive locking detected ]
[7.435893] 3.8.0-next-20130204+pcipatch-xeon+lockdep #20130204+pcipatch Not
tainted
[7.435893] -
at can be use as inspiration?
Was the discussion about handling one device from multiple drivers
concluded/implemented? It sounds very much what we are trying to do? Or
this was just some f2f discussion?
BR
Marcus Mobile
-- next part --
An HTML attachment was scrubbed...
URL:
On 02/12/2013 11:03 PM, Jiri Slaby wrote:
> On 02/12/2013 10:55 PM, Jiri Slaby wrote:
>> --- a/drivers/gpu/drm/drm_gem.c
>> +++ b/drivers/gpu/drm/drm_gem.c
>> @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
>> spin_lock(&dev->object_name_lock);
>> if (!ob
On 02/12/2013 10:55 PM, Jiri Slaby wrote:
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
> spin_lock(&dev->object_name_lock);
> if (!obj->name) {
> ret = idr_alloc(&dev
tachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/a3c8cbaa/attachment-0001.html>
On 02/12/2013 10:58 PM, Tejun Heo wrote:
> Hello, Jiri.
>
> On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote:
>> this commit in -next causes my KDE to get stuck while starting. I see
>> only the splash screen. If I disable effects by alt-shift-f12, it continues.
>>
>> I bisected it to th
2013/2/12 Sylwester Nawrocki :
> On 02/12/2013 02:17 PM, Inki Dae wrote:
>> Applied and will go to -next.
>> And please post the document(in
>> Documentation/devicetree/bindings/gpu/) for it later.
>
> There is already some old patch applied in the devicetree/next tree:
>
> http://git.secretlab.ca/
Hi,
this commit in -next causes my KDE to get stuck while starting. I see
only the splash screen. If I disable effects by alt-shift-f12, it continues.
I bisected it to this commit:
commit 430440fce7da4ad52c2af06a04a5132e5d19faaf
Author: Tejun Heo
Date: Thu Feb 7 12:31:37 2013 +1100
drm: c
next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/d0eff0e3/attachment-0001.html>
Applied and will go to -next.
And please post the document(in
Documentation/devicetree/bindings/gpu/) for it later.
Thanks,
Inki Dae
2013/2/6 Sachin Kamat :
> From: Ajay Kumar
>
> This patch adds device tree match table for Exynos G2D controller.
>
> Signed-off-by: Ajay Kumar
> Signed-off-by: S
:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/3fb92703/attachment.html>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/b544dafb/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=53391
--- Comment #11 from Marcin Slusarz 2013-02-12
21:36:52 ---
Created an attachment (id=93171)
--> (https://bugzilla.kernel.org/attachment.cgi?id=93171)
quirk v3
maybe this one?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.c
From: YoungJun Cho
This patch releases allocated resources properly when
exynos_user_fb_create() is failed.
Signed-off-by: YoungJun Cho
Signed-off-by: Inki Dae
Signed-off-by: Kyungmin Park
---
drivers/gpu/drm/exynos/exynos_drm_fb.c | 51 +---
1 files changed, 27
>
> just 3 nouveau fixes, all user visible issues, I have one radeon
> regression fix I'm hoping to send tomorrow once I'm happy with it.
Okay I've added the radeon regression fix on top as well
The following changes since commit ff7c60c580d9722f820d85c9c58ca55ecc1ee7c4:
drm/ttm: fix fence loc
From: YoungJun Cho
This patch fixes wrong pointer access issue to filp->f_op and
filp->private_data.
The exynos_drm_gem_mmap_ioctl() changes filp->f_op and
filp->private_data temporarily and restore them to use
original ones in exynos_drm_gem_mmap_buffer() but there
was no lock between the chang
ote that I'm not trying to say that the full-bus approach
doesn't work. My "brain just doesn't accept it" as you said above, which
could be because I'm so accustomed to a certain way of seeing this whole
display bus thing. So please continue with this approach, and prove my
worries wrong =).
Tomi
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/46a819ca/attachment-0001.pgp>
Dave/Bjorn,
On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote:
> Hi,
>
> Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
> following build error:
>
> CC drivers/gpu/drm/drm_pci.o
> drivers/gpu/drm/drm_pci.c: In function ?drm_pcie_get_speed_cap_mas
https://bugzilla.kernel.org/show_bug.cgi?id=49981
J?r?me Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130212/3c69df66/attachment.html>
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/db891721/attachment.html>
On 02/12/2013 04:53 PM, Tomi Valkeinen wrote:
> On 2013-02-12 17:04, Marcus Lorentzon wrote:
>
>> Now we have some different types of panels which are attached on a
>> combination of busses:
>>
>> a) control:DBI, data:DBI
>> b) control:I2C/SPI, data:I2C/SPI
>> c) control:static setup, data:DPI
>> d
on-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/12f58e3d/attachment-0001.pgp>
Heaven is still
black.
--
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/20130212/a8317e11/attachment.html>
https://bugs.freedesktop.org/show_bug.cgi?id=59592
Jerome Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=53391
--- Comment #12 from Stijn Tintel 2013-02-13
00:53:57 ---
Still not good, the 2nd monitor is initialized first, both by nouveaufb and X.
It is recognized as DVI-I-2 though.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?ta
On Tuesday 12 February 2013, Greg KH wrote:
> On Tue, Feb 12, 2013 at 11:20:04PM +0100, Marcus Lorentzon wrote:
> > Den 12 feb 2013 23:02 skrev "Greg KH" :
> > >
> > > On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> > > > 3) Daniel V hinted that multiple parents (or multiple bus
Hi Greg,
at FOSDEM we had a session on CDF (Common Display Framework). You can
read more details about this in the posts from Laurent Pinchart on dridevel:
http://lists.freedesktop.org/archives/dri-devel/2012-November/030888.html
http://lists.freedesktop.org/archives/dri-devel/2013-February/034576
On Tue, Feb 5, 2013 at 2:27 PM, Laurent Pinchart
wrote:
> Hello,
>
> We've hosted a CDF meeting at the FOSDEM on Sunday morning. Here's a summary
> of the discussions.
>
> I would like to start with a big thank to UrLab, the ULB university hacker
> space, for providing us with a meeting room.
>
>
On 02/11/13 21:30, Lennart Poettering wrote:
[?]
> Of course, doing this via the command line is not user-frienldy, but
> maybe this will one day get fixed and somebody writes a proper UI for
> it...
>
Regarding 'loginctl attach seat0 ', the only thing really missing
is the 'sys' path completion,
Hi,
Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
following build error:
CC drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function ?drm_pcie_get_speed_cap_mask?:
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of
function
you apply the patches, run make check from src/gallium/drivers/r300 and
make sure it passes and then re-test Heaven.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.or
If the -M parameter is specific, modetest will use the requested device
name instead of trying its builtin list of device names.
Signed-off-by: Laurent Pinchart
Reviewed-by: Jani Nikula
---
tests/modetest/modetest.c | 41 -
1 file changed, 28 insertions(+
The current mostly random sort order hinders code readability. Sort the
options alphabetically in the code, and by group in the help message.
Signed-off-by: Laurent Pinchart
Reviewed-by: Jani Nikula
---
tests/modetest/modetest.c | 49 ++-
1 file chang
Those variables are declared in unistd.h, there's no need to redeclare
them here.
Signed-off-by: Laurent Pinchart
Reviewed-by: Jani Nikula
---
tests/modetest/modetest.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
index 1081c78..92c7
Enable all standard automake warnings except for -Wpointer-arith (as the
test pattern generation code uses void pointer arithmetics) and fix
them.
Signed-off-by: Laurent Pinchart
---
tests/modetest/Makefile.am | 4 +++-
tests/modetest/buffers.c | 13 +++--
tests/modetest/buffers.h |
Hello,
Here's the third version of a small patch set that adds an argument to the
modetest command line to specify the driver name instead of using the builtin
list of drivers. This is particularly handy during development of new DRM/KMS
drivers.
This version enables compiler warnings for modetes
On Tue, Feb 12, 2013 at 11:20:04PM +0100, Marcus Lorentzon wrote:
> Den 12 feb 2013 23:02 skrev "Greg KH" :
> >
> > On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> > > 3) Daniel V hinted that multiple parents (or multiple busses) is
> > > something that has been discussed as a l
On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> 3) Daniel V hinted that multiple parents (or multiple busses) is
> something that has been discussed as a limitation of device driver
> model before. And that maybe now was the time to fix that or at
> least sort out how to handle
On 2013-02-12 19:06, Marcus Lorentzon wrote:
> Maybe in most cases, like a modern mobile phone. But for DBI and DSI you
> can have many devices or endpoints on the same bus. On DSI you can even
DBI supports two devices and DSI supports four, if I recall right. But
for DSI you need an external hub
Hi Sylwester,
On Wednesday, 6 February 2013, Sachin Kamat wrote:
> This patch adds device tree based discovery support to G2D driver
>
> Signed-off-by: Sachin Kamat
> ---
> Based on for_v3.9 branch of below tree:
> git://linuxtv.org/snawrocki/samsung.git
>
> Changes since v1:
> * Addressed revie
On Tuesday, 12 February 2013, Inki Dae wrote:
> Applied and will go to -next.
Thanks.
> And please post the document(in
> Documentation/devicetree/bindings/gpu/) for it later
Already posted (1).
(1) http://patches.linaro.org/14640/
--
With warm regards,
Sachin
___
On Tue, Feb 5, 2013 at 2:27 PM, Laurent Pinchart
wrote:
> Hello,
>
> We've hosted a CDF meeting at the FOSDEM on Sunday morning. Here's a summary
> of the discussions.
>
> I would like to start with a big thank to UrLab, the ULB university hacker
> space, for providing us with a meeting room.
>
>
On 02/11/13 21:09, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130211:
>
when CONFIG_PCI is not enabled (on x86_64):
CC [M] drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration
Hi Marcus,
On 2013-02-12 17:04, Marcus Lorentzon wrote:
> Now we have some different types of panels which are attached on a
> combination of busses:
>
> a) control:DBI, data:DBI
> b) control:I2C/SPI, data:I2C/SPI
> c) control:static setup, data:DPI
> d) control:I2C/SPI, data:DPI
> e) control:DS
On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote:
> On 02/11/13 21:09, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130211:
> >
>
>
> when CONFIG_PCI is not enabled (on x86_64):
>
> CC [M] drivers/gpu/drm/drm_pci.o
> drivers/gpu/drm/drm_pci.c: In function 'drm_pci
On Tue, Feb 12, 2013 at 07:20:30PM -0200, Fabio Estevam wrote:
> Dave/Bjorn,
>
> On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote:
> > Hi,
> >
> > Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
> > following build error:
> >
On 02/12/2013 02:17 PM, Inki Dae wrote:
> Applied and will go to -next.
> And please post the document(in
> Documentation/devicetree/bindings/gpu/) for it later.
There is already some old patch applied in the devicetree/next tree:
http://git.secretlab.ca/?p=linux.git;a=commitdiff;h=09495dda6a62c7
On Tue, Feb 12, 2013 at 11:20:04PM +0100, Marcus Lorentzon wrote:
> Den 12 feb 2013 23:02 skrev "Greg KH" :
> >
> > On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> > > 3) Daniel V hinted that multiple parents (or multiple busses) is
> > > something that has been discussed as a l
Den 12 feb 2013 23:02 skrev "Greg KH" :
>
> On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> > 3) Daniel V hinted that multiple parents (or multiple busses) is
> > something that has been discussed as a limitation of device driver
> > model before. And that maybe now was the time
+dri-devel ML
>
>
> On 12 February 2013 07:20, wrote:
>>
>> From: John Sheu
>>
>> Callers to dma_buf_mmap expect to fput() the vma struct's vm_file
>> themselves on failure. Not restoring the struct's data on failure
>> causes a double-decrement of the vm_file's refcount.
>>
>> Signed-off-by: Jo
ves/dri-devel/attachments/20130212/dfe19f90/attachment.html>
.linaro.org/>* **? *Open source software for ARM SoCs*
***
Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> |
Twitter<http://twitter.com/#!/linaroorg>
| Blog <http://www.linaro.org/linaro-blog/>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/fe3d741f/attachment.html>
Hello, Jiri.
On Tue, Feb 12, 2013 at 11:08:41PM +0100, Jiri Slaby wrote:
> > Oh my, maybe: return ret < 0 ? ret : 0... Let's try.
>
> Bull's eye.
Aieee
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -459,6 +459,7 @@ drm_gem_flink_ioctl(struct drm_device *dev, void
Hello, Jiri.
On Tue, Feb 12, 2013 at 11:08:41PM +0100, Jiri Slaby wrote:
> > Oh my, maybe: return ret < 0 ? ret : 0... Let's try.
>
> Bull's eye.
Aieee
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -459,6 +459,7 @@ drm_gem_flink_ioctl(struct drm_device *dev, void
On 02/12/2013 11:03 PM, Jiri Slaby wrote:
> On 02/12/2013 10:55 PM, Jiri Slaby wrote:
>> --- a/drivers/gpu/drm/drm_gem.c
>> +++ b/drivers/gpu/drm/drm_gem.c
>> @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
>> spin_lock(&dev->object_name_lock);
>> if (!ob
ch the full output from configure and make.
--
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/20130212/1863f608/attachment-0001.html>
xt part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/eb306ccb/attachment.html>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/a347e0fe/attachment.html>
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #6 from n...@detonation.org ---
The patch seems to fix the problem indeed. I've been trying more than half an
hour to get the GPU to lock up without result. Thank you very very much!
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=60073
--- Comment #5 from Jordan Justen ---
Please retest with 496928a4, as this commit reverts
this change for desktop GL. (The behavior is retained
for GLES3.)
--
You are receiving this mail because:
You are the assignee for the bug.
__
On 02/12/2013 10:55 PM, Jiri Slaby wrote:
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -453,7 +453,8 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
> spin_lock(&dev->object_name_lock);
> if (!obj->name) {
> ret = idr_alloc(&dev
On Tue, Feb 12, 2013 at 04:04:53PM +0100, Marcus Lorentzon wrote:
> 3) Daniel V hinted that multiple parents (or multiple busses) is
> something that has been discussed as a limitation of device driver
> model before. And that maybe now was the time to fix that or at
> least sort out how to handle
On 02/12/2013 10:58 PM, Tejun Heo wrote:
> Hello, Jiri.
>
> On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote:
>> this commit in -next causes my KDE to get stuck while starting. I see
>> only the splash screen. If I disable effects by alt-shift-f12, it continues.
>>
>> I bisected it to th
Hello, Jiri.
On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote:
> this commit in -next causes my KDE to get stuck while starting. I see
> only the splash screen. If I disable effects by alt-shift-f12, it continues.
>
> I bisected it to this commit:
> commit 430440fce7da4ad52c2af06a04a513
Hello, Jiri.
On Tue, Feb 12, 2013 at 10:55:37PM +0100, Jiri Slaby wrote:
> this commit in -next causes my KDE to get stuck while starting. I see
> only the splash screen. If I disable effects by alt-shift-f12, it continues.
>
> I bisected it to this commit:
> commit 430440fce7da4ad52c2af06a04a513
Hi,
this commit in -next causes my KDE to get stuck while starting. I see
only the splash screen. If I disable effects by alt-shift-f12, it continues.
I bisected it to this commit:
commit 430440fce7da4ad52c2af06a04a5132e5d19faaf
Author: Tejun Heo
Date: Thu Feb 7 12:31:37 2013 +1100
drm: c
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/700fbfb6/attachment.html>
On Tue, Feb 12, 2013 at 08:06:00AM -0800, Randy Dunlap wrote:
> On 02/11/13 21:09, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20130211:
> >
>
>
> when CONFIG_PCI is not enabled (on x86_64):
>
> CC [M] drivers/gpu/drm/drm_pci.o
> drivers/gpu/drm/drm_pci.c: In function 'drm_pci
https://bugzilla.kernel.org/show_bug.cgi?id=44341
--- Comment #11 from Alex Deucher 2013-02-12
13:42:26 ---
Created an attachment (id=93151)
--> (https://bugzilla.kernel.org/attachment.cgi?id=93151)
remove overzealous warning
This patch should fix the issue.
--
Configure bugmail: https:
https://bugzilla.kernel.org/show_bug.cgi?id=53391
--- Comment #11 from Marcin Slusarz 2013-02-12
21:36:52 ---
Created an attachment (id=93171)
--> (https://bugzilla.kernel.org/attachment.cgi?id=93171)
quirk v3
maybe this one?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.c
On Tue, Feb 12, 2013 at 07:20:30PM -0200, Fabio Estevam wrote:
> Dave/Bjorn,
>
> On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote:
> > Hi,
> >
> > Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
> > following build error:
> >
Dave/Bjorn,
On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote:
> Hi,
>
> Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
> following build error:
>
> CC drivers/gpu/drm/drm_pci.o
> drivers/gpu/drm/drm_pci.c: In function ‘drm_pcie_get_speed_cap_mas
On Tue, Feb 12, 2013 at 8:40 AM, wrote:
> From: Alex Deucher
>
> hdmi audio works fine. The warning just confuses users.
>
> fixes:
> https://bugzilla.kernel.org/show_bug.cgi?id=44341
>
> Signed-off-by: Alex Deucher
Reviewed-by: Jerome Glisse
> Cc: stable at vger.kernel.org
> ---
> drivers/g
https://bugzilla.kernel.org/show_bug.cgi?id=53391
--- Comment #10 from Stijn Tintel 2013-02-12
12:54:22 ---
Unfortunately with the first patch and #if 0 -> #if 1 nouveau and X start on
the 2nd monitor again (with DVI cables). shall I test with vga cables again too
?
--
Configure bugmail:
Hi Daniel,
Thanks for the patch. Just one last small comment.
On Tuesday 05 February 2013 22:43:48 Daniel Vetter wrote:
> Now that the fbdev helper interface for drivers is trimmed down,
> update the kerneldoc for all the remaining exported functions.
>
> I've tried to beat the DocBook a bit by
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/f004115f/attachment.html>
se:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130212/209828d6/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=49981
Jérôme Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=60236
Jerome Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #5 from Jerome Glisse ---
Created attachment 74707
--> https://bugs.freedesktop.org/attachment.cgi?id=74707&action=edit
Mesa fix
Please try if attached mesa patch fix it
--
You are receiving this mail because:
You are the assigne
list->map is struct drm_local_map *, not struct drm_map_list *.
Signed-off-by: Jani Nikula
---
Found this small snippet laying around, I guess it fell between the cracks.
---
drivers/gpu/drm/drm_gem.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_ge
On Tue, Feb 12, 2013 at 8:40 AM, wrote:
> From: Alex Deucher
>
> hdmi audio works fine. The warning just confuses users.
>
> fixes:
> https://bugzilla.kernel.org/show_bug.cgi?id=44341
>
> Signed-off-by: Alex Deucher
Reviewed-by: Jerome Glisse
> Cc: sta...@vger.kernel.org
> ---
> drivers/gpu/
Hi,
Building imx_v6_v7_defconfig on linux-next 20130212 gives me the
following build error:
CC drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function ‘drm_pcie_get_speed_cap_mask’:
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration of
function
On Mon, 11 Feb 2013, Laurent Pinchart
wrote:
> On Monday 11 February 2013 21:13:45 Laurent Pinchart wrote:
>> If the -M parameter is specific, modetest will use the requested device
>> name instead of trying its builtin list of device names.
>>
>> Signed-off-by: Laurent Pinchart
>> ---
>> test
(cc'ing Andrew)
Hello,
On Sun, Feb 10, 2013 at 03:49:05PM +0400, Artem Savkov wrote:
> Added missing idr_preload_end calls in drm_gem_flink_ioctl().
> Without those preemption stays disabled resulting in lots of "scheduling while
> atomic" BUGs.
>
> Introduced in 4e486fae707d9a79c76f1be6dcacffc4
https://bugs.freedesktop.org/show_bug.cgi?id=60503
--- Comment #10 from Pavel Ondračka ---
(In reply to comment #9)
> (In reply to comment #8)
> > Created attachment 74525 [details]
> > RADEON_DEBUG=fp log with patch v2 applied
> >
> > (In reply to comment #7)
> > > Created attachment 74520 [det
(cc'ing Andrew)
Hello,
On Sun, Feb 10, 2013 at 03:49:05PM +0400, Artem Savkov wrote:
> Added missing idr_preload_end calls in drm_gem_flink_ioctl().
> Without those preemption stays disabled resulting in lots of "scheduling while
> atomic" BUGs.
>
> Introduced in 4e486fae707d9a79c76f1be6dcacffc4
On Mon, Feb 11, 2013 at 4:34 PM, Tim Gardner
wrote:
> Smatch anlysis:
>
> drivers/gpu/drm/radeon/atom.c:1242 atom_index_iio() error: potential null
> dereference 'ctx->iio'. (kzalloc returns null)
>
> Also cleaned up some checks before calls to kfree(). kfree(NULL) is OK.
>
> Cc: David Airlie
On 02/12/2013 04:53 PM, Tomi Valkeinen wrote:
On 2013-02-12 17:04, Marcus Lorentzon wrote:
Now we have some different types of panels which are attached on a
combination of busses:
a) control:DBI, data:DBI
b) control:I2C/SPI, data:I2C/SPI
c) control:static setup, data:DPI
d) control:I2C/SPI, d
From: Alex Deucher
hdmi audio works fine. The warning just confuses users.
fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=44341
Signed-off-by: Alex Deucher
Cc: stable at vger.kernel.org
---
drivers/gpu/drm/radeon/r600_hdmi.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
dif
On 02/11/13 21:09, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130211:
>
when CONFIG_PCI is not enabled (on x86_64):
CC [M] drivers/gpu/drm/drm_pci.o
drivers/gpu/drm/drm_pci.c: In function 'drm_pcie_get_speed_cap_mask':
drivers/gpu/drm/drm_pci.c:485:2: error: implicit declaration
https://bugs.freedesktop.org/show_bug.cgi?id=60503
--- Comment #9 from Tom Stellard ---
(In reply to comment #8)
> Created attachment 74525 [details]
> RADEON_DEBUG=fp log with patch v2 applied
>
> (In reply to comment #7)
> > Created attachment 74520 [details]
> > Fix v2
> >
> > This should fi
Hi Greg,
at FOSDEM we had a session on CDF (Common Display Framework). You can
read more details about this in the posts from Laurent Pinchart on dridevel:
http://lists.freedesktop.org/archives/dri-devel/2012-November/030888.html
http://lists.freedesktop.org/archives/dri-devel/2013-February/0345
On 02/11/13 21:30, Lennart Poettering wrote:
[…]
> Of course, doing this via the command line is not user-frienldy, but
> maybe this will one day get fixed and somebody writes a proper UI for
> it...
>
Regarding 'loginctl attach seat0 ', the only thing really missing
is the 'sys' path completion,
https://bugs.freedesktop.org/show_bug.cgi?id=60723
Michel Dänzer changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=60723
--- Comment #4 from Vincenzo Abate ---
It didn't worked. I attached logs from configure and make as asked...
(In reply to comment #1)
> Does it work if you add --enable-shared-glapi to the configure arguments? If
> not, please attach the full ou
https://bugs.freedesktop.org/show_bug.cgi?id=60723
--- Comment #3 from Vincenzo Abate ---
Created attachment 74683
--> https://bugs.freedesktop.org/attachment.cgi?id=74683&action=edit
make log
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=60723
--- Comment #2 from Vincenzo Abate ---
Created attachment 74682
--> https://bugs.freedesktop.org/attachment.cgi?id=74682&action=edit
configure log
--
You are receiving this mail because:
You are the assignee for the bug.
_
On Mon, Feb 11, 2013 at 4:34 PM, Tim Gardner wrote:
> Smatch anlysis:
>
> drivers/gpu/drm/radeon/atom.c:1242 atom_index_iio() error: potential null
> dereference 'ctx->iio'. (kzalloc returns null)
>
> Also cleaned up some checks before calls to kfree(). kfree(NULL) is OK.
>
> Cc: David Airlie
>
1 - 100 of 128 matches
Mail list logo
