the
> check assumes that all other placements are backed by device
> memory or IO. If there are
> any other placements that use system memory, that flag has to be
> OR'ed into the check.
>
> The above patch has no implications on a normal kernel or
another question, you are right.
If the interface is just temporary, it should probably go into
debugfs. That way one can have the code in the kernel proper,
not fear about freezing it, and prevent people from finding it
by accident. And it should be guarded by an "EXPERIMENTAL, DANGER
similar
features.
Hopefully people working on power management interfaces
on intel and radeon can comment on this, like is there
an agreed user interface design yet.
btw. I think max powersaving and no performance loss are
mutually exclusive, since changing power modes is not
free nor instantenou
On Thu, 10 Dec 2009 15:33:13 -0500
"C. Bergström" wrote:
> Pekka Paalanen
>
> > The big question is what we call ctxprogs: binary blobs that are
> > clearly executable, running somewhere in the GPU. No-one seems
> > to know, if those are copyrightable, or if
rietary driver
- install it and load it into the kernel
- activate mmiotrace (if it even is compiled in)
- reconfigure and start X and quit
- analyse the mmiotrace log to extract the ctxprog and ctxvals
- undo all the proprietary setup
I cannot comment on the legal side, but the practise sounds
n recorded from the nvidia
proprietary driver using mmiotrace, and copied verbatim for each
card type.
Would you be willing to pull that kind of stuff into Linux?
I would not even dare sending them to the Linux firmware
repository, since they have some license requirements, too.
--
Pekka Paalane
t; and drm-intel-next, so that the code in drm-next is tested
> better. You should use this tree for testing latest drm stuff
> with an eye to the next Linus kernel.
--
Pekka Paalanen
http://www.iki.fi/pq/
--
J
rmMode.h
and then these two...
So, each of the three drivers have their headers installed
differently, and Nouveau manages to fail even in that. :-)
What should installed header tree look like?
--
Pekka Paalanen
http://www.iki.fi/pq/
Linus' tree, so there is nothing to fix, really.
I've been wondering when the merge happens...
btw. Nouveau does not carry backwards support, so when it does happen,
all Nouveau users need to upgrade too.
Users wishing to mix and
roken, nobody cares.
The merge from drm-next likely introduced some internal API
changes, and nouveau/linux-2.6 being the Nouveau tree, radeon
is not fixed, until 1) radeon fixes get into drm-next, and
2) drm-next gets merged into nouveau/linux-2.6.
If you want to test early radeon code, you sh
blem should be fixed now, we debugged it for a long time. E.g.
https://bugs.freedesktop.org/show_bug.cgi?id=23847
The commit:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=7798546495c04a810db86be34ba1f39e370fd325
"drm/nouveau: fix missized allocation for ttm_bo_global struct&
Fix the error message: this is add, not rm.
Move the closing brace to proper spot: _DRM_GEM branch should not be
included in the block.
Signed-off-by: Pekka Paalanen
---
drivers/gpu/drm/drm_bufs.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm
Several functions in the GEM kernel API used int as handle type, but
user API has it __u32 which is also the intended type.
Replace int with u32.
Signed-off-by: Pekka Paalanen
---
drivers/gpu/drm/drm_gem.c | 11 +--
drivers/gpu/drm/i915/i915_gem.c |3 ++-
include/drm/drmP.h
Cc: Francisco Jerez
Signed-off-by: Pekka Paalanen
---
include/drm/drm_encoder_slave.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/drm/drm_encoder_slave.h b/include/drm/drm_encoder_slave.h
index 821ec40..a8d8053 100644
--- a/include/drm/drm_encoder_slave.h
, when buffer objects are
accessed via wrappers, that work for both kinds of memory addresses:
iomem cookies and kernel virtual.
Signed-off-by: Pekka Paalanen
---
include/drm/ttm/ttm_bo_api.h | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/drm/ttm
Signed-off-by: Pekka Paalanen
---
include/drm/drm_encoder_slave.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/drm/drm_encoder_slave.h b/include/drm/drm_encoder_slave.h
index 821ec40..e5e5c94 100644
--- a/include/drm/drm_encoder_slave.h
+++ b/include/drm
e it to the nouveau/linux-2.6 master branch, we would
have to remember to revert it when submitting Nouveau upstream.
OTOH, we could apply it to master-compat branch for testing.
How's that sound?
Thanks.
--
Pekka Paalanen
http://www.iki.fi/pq/
---
Hi,
some minor comments below.
On Tue, 11 Aug 2009 15:52:06 +1000
Dave Airlie wrote:
> From: Tiago Vignatti
>
> Background:
> Graphic devices are accessed through ranges in I/O or memory space. While most
> modern devices allow relocation of such ranges, some "Legacy" VGA devices
> implemente
>From 8fb4fecbdf912abdde82bfff40443c9a57c32e26 Mon Sep 17 00:00:00 2001
From: Pekka Paalanen
Date: Mon, 10 Aug 2009 19:44:58 +0300
Subject: [PATCH] drm/nouveau: optimize code emission of inline functions
When a call into a static inline function cannot be inlined, the
function is emitted a
On Sun, 02 Aug 2009 20:12:18 +0200
Thomas Hellström wrote:
> Pekka Paalanen skrev:
> > From 5e2851952729b287a82efa002b28a2095404d44d Mon Sep 17 00:00:00 2001
> > From: Thomas Hellstrom
> > Date: Fri, 31 Jul 2009 10:47:51 +0200
> > Subject: [PATCH] ttm: Fix a pote
off-by: Thomas Hellstrom
Signed-off-by: Pekka Paalanen
---
Thomas, you forgot two more of these :-)
Here's a patch that actually compiles on x86_64.
drivers/gpu/drm/ttm/ttm_bo_util.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_b
On Fri, 31 Jul 2009 10:59:57 +0200
Thomas Hellström wrote:
> Pekka Paalanen wrote:
> >> @@ -145,17 +146,35 @@ static int ttm_copy_io_ttm_page(struct ttm_tt *ttm,
> >> void *src,
> >>return -ENOMEM;
> >>
> >>src = (void *)((unsign
prot);
> + } else if (new_iomap == NULL) {
> + pgprot_t prot = ttm_io_prot(new_mem->placement,
> + PAGE_KERNEL);
> + ret = ttm_copy_io_ttm_page(ttm, old_iomap, pag
structions, since
the kernel tree is so big, but there are more than one way to pull updates.
--
Pekka Paalanen
http://www.iki.fi/pq/
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $1
edesktop.org/archives/nouveau/2009-July/003148.html
and the Nouveau wiki.
The nouveau kernel tree was annouced on the wiki front page, and on
the nouveau mailing list. What more should we have done?
--
Pekka Paalanen
http://www.iki.fi/pq/
gt; chmod(DRM_DIR_NAME, DRM_DEV_DIRMODE);
> }
>
> @@ -320,7 +363,7 @@ static int drmOpenDevice(long dev, int minor, int type)
> }
>
> if (drm_server_info) {
> - chown(buf, user, group);
> + chownCheckReturn(buf, user, group);
>
Linus' tree back to drm.git?
Isn't drm.git linux-core dying after all?
Thanks.
--
Pekka Paalanen
http://www.iki.fi/pq/
--
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
red.
Well, rc1 is so near, that we probably won't bother fixing Nouveau in
drm.git. I just wish the transition would have been Nouveau developers'
decision.
Regards, pq
--
Pekka Paalanen
cfbcopyarea.ko
cfbfillrect.ko
cfbimgblt.ko
nouveau.ko
Now the Nouveau DDX should run just fine using the new DRM modules.
Ben, I still don't see any comment from you on this thread :-)
--
Pekka Paalanen
http://www.iki.fi/pq/
#!/bin/bash
# 395e0ddc44005ced5e4fed9bfc
Signed-off-by: Pekka Paalanen
---
linux-core/drmP.h |6 --
linux-core/drm_agpsupport.c | 37 +
linux-core/drm_memory.c |7 ---
linux-core/drm_memory_debug.c |4
4 files changed, 1 insertions(+), 53 deletions
Signed-off-by: Pekka Paalanen
---
linux-core/drm_os_linux.h | 18 --
1 files changed, 0 insertions(+), 18 deletions(-)
diff --git a/linux-core/drm_os_linux.h b/linux-core/drm_os_linux.h
index 8921944..4f1e83b 100644
--- a/linux-core/drm_os_linux.h
+++ b/linux-core
Even 2.6.21 is about two years old now. Drop support for all kernels
before 2.6.21. This kernel version is a nice stopping point, since
it guarantees #define DRM_FULL_MM_COMPAT.
If no-one objects, I can push these into drm.git myself.
Pekka Paalanen (10):
drm: drm_bo_mmap_locked() is static
This also means dropping the DRM_ODD_MM_COMPAT case.
Signed-off-by: Pekka Paalanen
---
linux-core/drm_bo.c | 46
linux-core/drm_bo_move.c | 16 ---
linux-core/drm_compat.c | 272 +
linux-core/drm_compat.h | 82
Signed-off-by: Pekka Paalanen
---
linux-core/drm_bo.c |7 ---
linux-core/drm_compat.c | 104 +--
linux-core/drm_compat.h | 24 +--
linux-core/drm_drv.c|3 -
linux-core/drm_ttm.c|6 ---
5 files changed, 2 insertions
This also means, that DRM_FULL_MM_COMPAT is always defined,
so it is dropped, too.
Signed-off-by: Pekka Paalanen
---
linux-core/drm_compat.c | 164 ---
linux-core/drm_compat.h | 26
linux-core/drm_vm.c |6 +--
3 files changed, 1
Signed-off-by: Pekka Paalanen
---
linux-core/drm_bo.c | 13 -
linux-core/drm_objects.h |4
linux-core/via_dmablit.c | 12
3 files changed, 0 insertions(+), 29 deletions(-)
diff --git a/linux-core/drm_bo.c b/linux-core/drm_bo.c
index 6f083f5..f43480c
Signed-off-by: Pekka Paalanen
---
linux-core/drm_compat.h | 21 -
linux-core/mga_drv.c |2 +-
linux-core/nouveau_drv.c |2 +-
linux-core/r128_drv.c|2 +-
linux-core/radeon_drv.c |2 +-
linux-core/xgi_drv.c |2 +-
6 files changed, 5
Signed-off-by: Pekka Paalanen
---
linux-core/drm_vm.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/linux-core/drm_vm.c b/linux-core/drm_vm.c
index d4d97a4..6de6031 100644
--- a/linux-core/drm_vm.c
+++ b/linux-core/drm_vm.c
@@ -870,8 +870,7 @@ static struct
Signed-off-by: Pekka Paalanen
---
linux-core/drm_compat.c | 45 -
linux-core/drm_compat.h | 11 ---
2 files changed, 0 insertions(+), 56 deletions(-)
diff --git a/linux-core/drm_compat.c b/linux-core/drm_compat.c
index e90338f..ff4085d
Signed-off-by: Pekka Paalanen
---
linux-core/drmP.h |2 --
linux-core/drm_compat.h | 10 --
2 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/linux-core/drmP.h b/linux-core/drmP.h
index bc68bfe..6770282 100644
--- a/linux-core/drmP.h
+++ b/linux-core/drmP.h
is moved out of drm.git, what is left is... Nouveau DRM?
What does this suggestion of "divorce libdrm" mean? Only libdrm itself,
or all the libdrm_* additional libraries too? To a single other repo,
or each (sub-)library to its own repo?
btw. where is Radeon DRM development happening no
>From b4c40cb00c44e65dd2a722f99e88260e0746bc22 Mon Sep 17 00:00:00 2001
From: Pekka Paalanen
Date: Sat, 14 Feb 2009 22:22:39 +0200
Subject: [PATCH] drm_compat: remove kmap_atomic_prot_pfn()
This function is unused, and yet creates build problems: the symbol
init_mm is not exported by the lat
the kernel
to just blit the cursor image on screen (aren't simple blitting engines and
overlays disappearing in the modern development of graphics hardware?).
--
Pekka Paalanen
http://www.iki.fi/pq/
--
This SF.net ema
tem to use the right Makefile, which is
tests/Makefile. {dri,drm}stat are built with libdrm.
This is purely a Gentoo packaging bug.
See
http://cgit.freedesktop.org/mesa/drm/commit/?id=27fae006853647ad0087067adc4eaa8d4ed4594a
--
Pekka Paalanen
http://www.iki.fi/pq/
-
esetting
> fro the other chips maintained?
--
Pekka Paalanen
http://www.iki.fi/pq/
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
ht
> AM_CFLAGS = -I$(top_srcdir)/shared-core
> libdrm_la_SOURCES = xf86drm.c xf86drmHash.c xf86drmRandom.c xf86drmSL.c \
> + xf86drmMode.c libdrm_lists.h
> libdrm_lists.h
>
> libdrmincludedir = ${includedir}
> -libdrminclude_HEADERS = xf86drm.h
> +libdrmin
wire camera to DMA images directly into memory accessible
by the GPU, with probably user space handling the synchronization.
I'm thinking real-time high resolution image processing and machine
vision. And if I could RT-prioritize GPU threads/contexts, it would
sound like th
f sample code missing, makes the drm_driver example
a bit awkward to read.
VBlank event handling:
- the last paragraph "...vblank functions into no-ops." seems
contradicting the previous paragraph.
I'm very much looking forward to the next revision with more
goodie
I have a recollection that TTM would force the command
stream through the kernel, but then again, I'm very new to all this.
Just my 2c.
--
Pekka Paalanen
http://www.iki.fi/pq/
-
This SF.net email is sponsored by: M
>From ee7e21c2cd96ce8b1a31f9013d606ab0ea3699e6 Mon Sep 17 00:00:00 2001
From: Pekka Paalanen <[EMAIL PROTECTED]>
Date: Sun, 20 Apr 2008 20:47:38 +0300
Subject: [PATCH] linux-core Makefile: add GIT_REVISION
This tries to automatically fetch a git revision string and if succeeds,
it
des or how the dirver works in the
> linux. Waiting for your reply thirstily! Thanks a lot!
>yours,
> shadow
>
>
> >From: Pekka Paalanen <[EMAIL
On Tue, 17 Apr 2007 20:15:53 +0100
Richard Hughes <[EMAIL PROTECTED]> wrote:
> Any chance we could get a make dist target for renouveau please? The
> attached patch works for me, and allows me to build automated daily
> snapshots.
I think everyone kind of trusts that the used renouveau version is
On Tue, 23 Jan 2007 18:55:10 -0800
"Alexy Khrabrov" <[EMAIL PROTECTED]> wrote:
> Well, after solving Gentoo-specific masking issues (thanks to folks
> who replied!), libdrm pulled by nouveau fails to build due to the
> build's own issues -- is that Gentoo ebuild of nouveau maintained?
> The refere
53 matches
Mail list logo