From: Zhao Yakui yakui.z...@intel.com
Two macro definitions of DRM_DEBUG_KMS/MODE can be used to add the debug
info related with KMS. It is confusing.
So remove the macro definition of DRM_DEBUG_MODE. Instead it can be replaced
by the DRM_DEBUG_KMS.
Signed-off-by: Zhao Yakui yakui.z...@intel.com
Hello Jerome, Keith:
It's hard to review if the interface is sane without knowing what userspace
might need or not.
Maybe VIA can provide some userspace code without putting together an entire
driver.
Can I suggest to verify the DRM source with the X driver which we will
release within 1
From: Zhao Yakui yakui.z...@intel.com
We will have to add a prefix when using the macro defintion of DRM_DEBUG_KMS
/DRM_DEBUG_DRIVER/MODE. It is not convenient. We should use the DRM_NAME
as default prefix.
So remove the prefix in the macro definition of DRM_DEBUG_KMS/DRIVER/MODE.
Signed-off-by:
Hello All:
I understand the requirement. If we submitted for mainline when everything
is ready, I believe it takes very long time. Some of you might know that VIA
has been trying to support community by releasing doc, source and submit for
upstream step by step. As Harald point out, the
From: Zhao Yakui yakui.z...@intel.com
Add the explanation about DRM debug level in the drmP header file. This is to
explain how/where to use the different DRM debug level.
Signed-off-by: Zhao Yakui yakui.z...@intel.com
---
include/drm/drmP.h | 31 +++
1 file
From: Zhao Yakui yakui.z...@intel.com
Add the debug info in generic drm mode by using DRM_DEBUG_KMS
Signed-off-by: Zhao Yakui yakui.z...@intel.com
---
drivers/gpu/drm/drm_crtc.c| 29 +
drivers/gpu/drm/drm_crtc_helper.c | 44
http://bugs.freedesktop.org/show_bug.cgi?id=22528
--- Comment #3 from Fabio fabio@libero.it 2009-07-20 01:55:08 PST ---
Apparently the demos use a protection library not supported by wine:
http://bugs.winehq.org/show_bug.cgi?id=3260
The full game got an updated patch (1.08) that remove
http://bugzilla.kernel.org/show_bug.cgi?id=13776
--- Comment #15 from mailingli...@openelec.tv 2009-07-20 09:47:52 ---
anyone can help me with this?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are
http://bugs.freedesktop.org/show_bug.cgi?id=16772
Mikko C. mikko@gmail.com changed:
What|Removed |Added
Component|Drivers/DRI/r300|Server/general
On Mon, 2009-07-20 at 11:52 +0800, brucech...@via.com.tw wrote:
Hello All:
I understand the requirement. If we submitted for mainline when
everything is ready, I believe it takes very long time. Some of you might
know that VIA has been trying to support community by releasing doc, source
On Mon, 2009-07-20 at 01:44 +0200, Michel Dänzer wrote:
From: Michel Dänzer daen...@vmware.com
The incorrect size caused benchmark results to be inflated by a factor of 4.
Whoops, forgot
Signed-off-by: Michel Dänzer daen...@vmware.com
---
drivers/gpu/drm/radeon/radeon_benchmark.c |4
http://bugs.freedesktop.org/show_bug.cgi?id=22851
Summary: supertuxkart wont start on 7.6-devel
Product: Mesa
Version: CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
http://bugs.freedesktop.org/show_bug.cgi?id=22851
Jakub Orlowski jaku...@hotmail.com changed:
What|Removed |Added
OS/Version|All |Linux (All)
On 201, 07 20, 2009 at 03:38:32PM +0200, Thomas Hellstr?m wrote:
Hi!
It appears that GPL'd DRM drivers for closed-source user-space
clients are becoming more common, and the situation appears to be
causing a lot of unnecessary work from people wanting their drivers
in the mainstream kernel.
* fully functional GPL user-space driver.
How can you argue that something as tailor made as a DRM interface can
be used without it being a derived work?
Our prior policy has been to reject such stuff (both the Intel wireless
driver regulatory daemon and the GMX driver)
Christoph Hellwig wrote:
I think you're just trying to push your agenda.
I think you're just trying to defend your business writing closed source
drivers. Drivers that aren't usable without binary blobs don't have
a business in the kernel tree, and your whining doesn't help it. You'd
http://bugs.freedesktop.org/show_bug.cgi?id=22852
Summary: [r300 KMS] modesetting not accepted by monitor
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
http://bugs.freedesktop.org/show_bug.cgi?id=22852
--- Comment #1 from Arno Schuring aelschur...@hotmail.com 2009-07-20
08:06:45 PST ---
Created an attachment (id=27850)
-- (http://bugs.freedesktop.org/attachment.cgi?id=27850)
Xorg.log from (working) 6.12.2 driver
--
Configure bugmail:
Peter Zijlstra wrote:
On Mon, 2009-07-20 at 15:38 +0200, Thomas Hellström wrote:
Politics:
It's true that sometimes some people don't like the code or what it
does. But when this is the underlying cause of NAK-ing a driver I think
it's very important that this is clearly stated, instead
http://bugs.freedesktop.org/show_bug.cgi?id=22852
--- Comment #2 from Arno Schuring aelschur...@hotmail.com 2009-07-20
08:08:00 PST ---
Created an attachment (id=27851)
-- (http://bugs.freedesktop.org/attachment.cgi?id=27851)
Xorg.log with (non-working) 6.12.99 driver
--
Configure
If the common agreement of the linux community is to *NOT* allow these
drivers in, so be it, then be honest and go ahead and tell the driver
writers. Don't make them respin their development trying to fix minor
flaws when their driver won't get in anyway!
The existing policy based on what
http://bugs.freedesktop.org/show_bug.cgi?id=22852
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Attachment #27849|application/octet-stream|text/plain
mime
http://bugs.freedesktop.org/show_bug.cgi?id=22852
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Attachment #27850|application/octet-stream|text/plain
mime
http://bugs.freedesktop.org/show_bug.cgi?id=22852
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Attachment #27851|application/octet-stream|text/plain
mime
On Mon, Jul 20, 2009 at 04:52:26PM +0100, Matthew Garrett wrote:
I think tightly integrated could do with some clarification here.
qcserial was accepted despite not being functional without a closed
userspace component - an open one's since been rewritten to allow it to
work. Do we define
From 3eb4a3493f13c48bee1b2453f5ecead0ba498c51 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 15:45:41 +0300
Subject: [PATCH 05/15] libdrm: Fix drmOpenDevice to take dev_t type as
parameter.
This fixes signed/unsigned comparission between st.st_dev and dev.
From 78bfacedfb3b81968b2171a942101d323b1782cb Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 15:48:48 +0300
Subject: [PATCH 06/15] libdrm: Fix loop index variable type to match
the type of count
---
libdrm/xf86drm.c |4 ++--
1 files changed, 2
From 10a9bf298be4695242bcdb63bcfad720e03bf040 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 16:31:54 +0300
Subject: [PATCH 08/15] libdrm: Make gcc to understand that pointers
are realy pointers.
---
libdrm/xf86drmSL.c |6 +++---
1 files changed, 3
From 7fcfbf715644d2268236b8a19d1f2f83c952d72b Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 16:25:59 +0300
Subject: [PATCH 07/15] libdrm: Fix random number generator to use unsigned seed.
This fixes wanring about unsigned/signed comparision.
Also make it
From 69cad004e5355e4adcee753de4da91c98949d3df Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 16:50:20 +0300
Subject: [PATCH 09/15] libdrm: Make drmAllocCpy static.
---
libdrm/xf86drmMode.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff
From 6ad9d2f1495df9bbdecbe4e7676da75d48ba3719 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 16:55:21 +0300
Subject: [PATCH 10/15] libdrm: Make drmAllocCpy use only single memcpy
call instead of calling memcpy in loop.
---
libdrm/xf86drmMode.c |4 +---
From 9043299720ef5ecac1fe575b0bbda19b81720dd8 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 18:00:43 +0300
Subject: [PATCH 13/15] libdrm/radeon: Remove unussed variables and
make printf happy with explicity void* cast from struct radeon_bo*.
---
From dea4cebdb49556ab06930bd5a4d303ce1c0b85c7 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 17:19:55 +0300
Subject: [PATCH 12/15] intel: Move debug output after setting the value.
---
libdrm/intel/intel_bufmgr_fake.c |4 ++--
1 files changed, 2
From 0c8b7939fc95084d77063eb8de78b0724d3d4058 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 17:00:45 +0300
Subject: [PATCH 11/15] libdrm: Make pci id numbers unsigned for sscanf.
---
libdrm/xf86drmMode.c |3 ++-
1 files changed, 2 insertions(+), 1
From 9c0cd0ba5bb5966498cad2c5a8c69ec24c4c8e34 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 18:40:49 +0300
Subject: [PATCH 15/15] Fix signed/unsigned comparison warning
---
libdrm/radeon/radeon_cs_gem.c | 13 +++--
1 files changed, 7
From 36aef4bf07154ef6d206f15ff1c036a7f8e368a9 Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 18:33:03 +0300
Subject: [PATCH 14/15] libdrm/radeon: Add config.h include to enable
POSIX extensions for strdup call.
---
libdrm/radeon/radeon_track.c |3 +++
Greg still claims that qcserial could be used by rebooting from Windows,
right? In that it would still be extremly borderline to me, but it's
qcserial has a firmware loader app nowdays (someone wrote one in April)
http://www.codon.org.uk/~mjg59/gobi_loader/
indeed Matthew wrote it 8)
http://bugs.freedesktop.org/show_bug.cgi?id=22372
Tilman Sauerbeck til...@code-monkey.de changed:
What|Removed |Added
CC|
On Sun, 28 Jun 2009 21:11:30 +0100
Sitsofe Wheeler sits...@yahoo.com wrote:
On Sun, Jun 07, 2009 at 12:06:18PM +0200, Rafael J. Wysocki wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12765
Subject : i915 VT switch with AIGLX causes X lock up
Submitter :
And then follows fixes for all tests.
From 1cd7a914be3fc5ee8aabdd2297710f5c781b555f Mon Sep 17 00:00:00 2001
From: Pauli Nieminen suok...@gmail.com
Date: Mon, 20 Jul 2009 21:36:57 +0300
Subject: [PATCH 1/4] libdrm/tests: Fix compiler warnings in dristat.c.
---
tests/dristat.c | 12
You obviously got all this completely wrong.
I avoid writing closed source drivers whenever I can, I'm not whining and
I'm not trying to push any of them. The code VIA is trying to submit has not
been written by me nor anybody I know. All VIA code I and the companies I've
worked for has
2009/7/21 Peter Zijlstra pet...@infradead.org:
On Mon, 2009-07-20 at 15:38 +0200, Thomas Hellström wrote:
Politics:
It's true that sometimes some people don't like the code or what it
does. But when this is the underlying cause of NAK-ing a driver I think
it's very important that this is
Stephane Marchesin wrote:
You obviously got all this completely wrong.
I avoid writing closed source drivers whenever I can, I'm not whining and
I'm not trying to push any of them. The code VIA is trying to submit has not
been written by me nor anybody I know. All VIA code I and the companies
On Sun, Jul 19, 2009 at 07:18:55PM +0200, Rafał Miłecki wrote:
Did VIA consider cooperation with distributions? Maybe they could
sponsor some single Mesa developers? What about The Linux Driver
Project: http://linuxdriverproject.org/ ? Maybe they would like to
cooperate? I'm looking for some
Andrey Panin pa...@centrinvest.ru writes:
* Users are still on mercy of binary blob supplier. Will this blob run on
arm ?
Or powerpc ? Or even x86_64 ? Will it be compatible with XOrg X.Y ?
Nobody knows that and there is no gain for users too.
Actually there is a loss - users see the
On Mon, Jul 20, 2009 at 04:16:20PM +0100, Alan Cox wrote:
If the common agreement of the linux community is to *NOT* allow these
drivers in, so be it, then be honest and go ahead and tell the driver
writers. Don't make them respin their development trying to fix minor
flaws when their
On Mon, Jul 20, 2009 at 10:34:09PM +0200, Harald Welte wrote:
On Sun, Jul 19, 2009 at 07:18:55PM +0200, Rafał Miłecki wrote:
Did VIA consider cooperation with distributions? Maybe they could
sponsor some single Mesa developers? What about The Linux Driver
Project:
On Tue, 7 Jul 2009 02:00:46 +0200 (CEST)
Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.29 and 2.6.30.
The following bug entry is on the current list of known regressions
introduced between
2009/7/20 Thomas Hellström tho...@shipmail.org:
Stephane,
Some comments on how these things has been handled / could be handled.
I would like to raise a couple of real-life issues I have in mind:
* First example, let's say VIA gets their Chrome9 DRM merged into the
kernel. Now let's say I
2009/7/21 Stephane Marchesin marche...@icps.u-strasbg.fr:
2009/7/20 Thomas Hellström tho...@shipmail.org:
Stephane,
Some comments on how these things has been handled / could be handled.
I would like to raise a couple of real-life issues I have in mind:
* First example, let's say VIA gets
I think tightly integrated could do with some clarification here.
qcserial was accepted despite not being functional without a closed
userspace component - an open one's since been rewritten to allow it to
It got as far as staging with a good deal of complaint. I am not sure it
would have
On Tue, Jul 21, 2009 at 12:28:35AM +0100, Alan Cox wrote:
I think tightly integrated could do with some clarification here.
qcserial was accepted despite not being functional without a closed
userspace component - an open one's since been rewritten to allow it to
It got as far as
2009/7/20 Greg KH gre...@suse.de:
On Mon, Jul 20, 2009 at 10:34:09PM +0200, Harald Welte wrote:
On Sun, Jul 19, 2009 at 07:18:55PM +0200, Rafał Miłecki wrote:
Did VIA consider cooperation with distributions? Maybe they could
sponsor some single Mesa developers? What about The Linux Driver
53 matches
Mail list logo
