[Bug 31615] New: Some textures broken on r600g
https://bugs.freedesktop.org/show_bug.cgi?id=31615 Summary: Some textures broken on r600g Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: di...@betriebsdirektor.de I've been using r600g for quite a while and it was working well. Since commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9 XBMC does not display any fonts in the menus any more (XBMC svn, default skin) - I suspect it's a texture problem. To me it looks like this commit is responsible for this problem: commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9 Author: Keith Whitwell Date: Tue Nov 9 20:08:45 2010 + r600: fix my pessimism about PIPE_TRANSFER_x flags -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31615] Some textures broken on r600g
https://bugs.freedesktop.org/show_bug.cgi?id=31615 Daniel changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #1 from Daniel 2010-11-14 02:58:23 PST --- *** This bug has been marked as a duplicate of bug 31613 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31613] UI Fonts in Blender are not visible with recent Mesa.
https://bugs.freedesktop.org/show_bug.cgi?id=31613 Daniel changed: What|Removed |Added CC||di...@betriebsdirektor.de --- Comment #1 from Daniel 2010-11-14 02:58:23 PST --- *** Bug 31615 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31617] New: Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled
https://bugs.freedesktop.org/show_bug.cgi?id=31617
Summary: Radeon/Compiz: 'failed to attach dri2 front buffer',
error case not handled
Product: Mesa
Version: 7.9
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: daniel.lichtenber...@gmail.com
Created an attachment (id=40267)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40267)
backtrace
System: Fedora 14, Radeon 4850, x86_64.
Using the system's mesa-dri-drivers package Compiz frequently crashes while
resizing windows. The backtrace (attached) and the error message, "failed to
attach dri2 front buffer XX", point to radeon_update_renderbuffers in
radeon_common_context.c around line 745:
bo = radeon_bo_open(...);
if (bo == NULL) {
fprintf(stderr, "failed to attach %s %d\n",
regname, buffers[i].name);
}
ret = radeon_bo_get_tiling(bo, &tiling_flags, &pitch);
An error message is printed when 'bo' could not be allocated, but bo is then
happily dereferenced in radeon_bo_get_tiling afterwards. Working around the
null pointer dereference (e.g. by adding a 'continue' in the "if bo==NULL"
block) fixes the crash for me and I haven't seen visual artifacts yet, although
the error message is printed from time to time while running Compiz.
The same stacktrace was logged by several people over at
https://bugzilla.redhat.com/show_bug.cgi?id=568593.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
[ Please CC me I am not subscribed to dri-devel ML ]
[ QUOTE ]
Hi all,
This patch-set changes the algorithm in drm_mm.c to not need additional
allocations to track free space and adds an api to make embedding struct
drm_mm_node possible. Benefits:
- If struct drm_mm_node is provided, no allocations need to be done anymore
in drm_mm. It looks like some decent surgery, but ttm should be able to
drop its preallocation dance.
- void *priv is back, but done right ;)
- Avoids a pointer chase when lru-scanning in i915 and saves a few bytes.
As a proof of concept I've converted i915. Beware though, the drm/i915
patches depend on my direct-gtt patches (which are actually the reason for
this series here).
Tested on my i855gm, i945gme, ironlake and agp rv570.
Comments, flames, reviews highly welcome.
[ /QUOTE ]
Against which GIT tree or linux-next version are these patchset for?
- Sedat -
$ cd ~/src/linux-2.6/linux-2.6.37-rc1
$ echo $SINGLE_KERNEL_VARIANT
i386_none_686
$ LC_ALL=C fakeroot make -f debian/rules.gen
setup_${SINGLE_KERNEL_VARIANT} 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config
debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86'
LOCALVERSION='-686' LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686'
MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS
Makefile README REPORTING-BUGS arch block crypto drivers firmware fs
include init ipc kernel lib mm net samples scripts security sound
tools usr virt .gitignore .mailmap 'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must
support the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
1 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK
for-linux-next/drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
(+) FAIL
for-linux-next/drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
make[1]: *** [debian/stamps/source] Error 1
make[1]: Leaving directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
make: *** [setup_i386_none_686_real] Error 2
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, 14 Nov 2010 15:03:31 +0100, Sedat Dilek wrote: > [ Please CC me I am not subscribed to dri-devel ML ] > > [ QUOTE ] > As a proof of concept I've converted i915. Beware though, the drm/i915 > patches depend on my direct-gtt patches (which are actually the reason for > this series here). > > [ /QUOTE ] > > Against which GIT tree or linux-next version are these patchset for? git://anongit.freedesktop.org/~danvet/drm direct-gtt -Chris -- Chris Wilson, Intel Open Source Technology Centre ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31619] New: Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 Summary: Desktop freezes quickly every now and then with dynpm Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: ern...@gmail.com This is with linux 2.6.37 from xorg-edgers. If I do echo dynpm > /sys/class/drm/card0/device/power_method Run compiz Grab a window and move it around, every now it freezes quickly and the resumes. The mouse movement during that period is completely lost. I'll try more kernels... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 3:38 PM, Chris Wilson wrote: > On Sun, 14 Nov 2010 15:03:31 +0100, Sedat Dilek > wrote: >> [ Please CC me I am not subscribed to dri-devel ML ] >> >> [ QUOTE ] >> As a proof of concept I've converted i915. Beware though, the drm/i915 >> patches depend on my direct-gtt patches (which are actually the reason for >> this series here). >> >> [ /QUOTE ] >> >> Against which GIT tree or linux-next version are these patchset for? > > git://anongit.freedesktop.org/~danvet/drm direct-gtt > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre > Thank you for the pointer to the right GIT repository and branch. Looks like [1] has Daniel's patchset (9 patches) already included. To attract more people for testing or joining it would be appreciated these interesting work would be (re)based on Dave's drm-next GIT tree, as this one is going to linux-next. Or is drm-next/linux-next work for intel-gfxcards done elsewhere? Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or Linus-tree is causing conflicts. - Sedat - [1] http://cgit.freedesktop.org/~danvet/drm/log/?h=embed-gtt-space ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 04:52:43PM +0100, Sedat Dilek wrote: > Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or > Linus-tree is causing conflicts. I've just retested merging with drm-core-next / drm-next and the core drm_mm parts merge without conflict. The i915 parts fail all over due to conflicts with other ongoing stuff. As I've said, these patches are just proof-of-concept, I need to redo them (and coordinate merging with Chris Wilson). So either test my embed-gtt-space branch to also enjoy the i915 patches. Or only test the drm core changes. -Daniel > [1] http://cgit.freedesktop.org/~danvet/drm/log/?h=embed-gtt-space -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 5:13 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 04:52:43PM +0100, Sedat Dilek wrote: >> Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or >> Linus-tree is causing conflicts. > > I've just retested merging with drm-core-next / drm-next and the core > drm_mm parts merge without conflict. The i915 parts fail all over due to > conflicts with other ongoing stuff. As I've said, these patches are just > proof-of-concept, I need to redo them (and coordinate merging with Chris > Wilson). So either test my embed-gtt-space branch to also enjoy the i915 > patches. Or only test the drm core changes. > If you could geneate a patchset w/o i915 parts for testing would be cool. Thanks in advance. - Sedat - ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31619] Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 --- Comment #1 from Ernst Sjöstrand 2010-11-14 09:07:37 PST --- It also happens with the drm-next kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2010-11-10-maverick/ It does not happen with Ubuntu Mavericks default 2.6.35 kernel. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote: > If you could geneate a patchset w/o i915 parts for testing would be cool. > Thanks in advance. Just drop patches 5-9 (you can apply patch 8 without any problems, it's just not gonna do anything without patch 9 ;). After all, this patch series is supposed to be bisectable, so stopping anywhere in between should result in a working kernel. -Daniel -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31619] Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 --- Comment #2 from Alex Deucher 2010-11-14 09:19:58 PST --- This is due to the pm code holding a number of locks while waiting to update the clocks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 6:14 PM, Daniel Vetter wrote:
> On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote:
>> If you could geneate a patchset w/o i915 parts for testing would be cool.
>> Thanks in advance.
>
> Just drop patches 5-9 (you can apply patch 8 without any problems, it's
> just not gonna do anything without patch 9 ;). After all, this patch
> series is supposed to be bisectable, so stopping anywhere in between
> should result in a working kernel.
>
> -Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
>
Njet :-(
I am cloning linux-next GIT and pull into drm-next to see if there is
sth. missing.
- Sedat -
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$ grep ^+ debian/patches/series/base
+ linux-next/patch-v2.6.37-rc1-next-20101112
+ linux-next/0001-Remove-localversion-next.patch
+ for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
+ mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
+ mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
+ linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
+ tpm-fix/tpm-Autodetect-itpm-devices.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/3-9-drm-mm-extract-node-insert-helper-functions.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/4-9-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/8-9-drm-mm-add-helper-to-unwind-scan-state.patch
+ debian/version.patch
+ debian/kernelvariables-2.6.37.patch
+ debian/doc-build-parallel.patch
+ bugfix/ia64/hardcode-arch-script-output.patch
+ bugfix/mips/disable-advansys.patch
+ bugfix/arm/disable-scsi_acard.patch
+ debian/mips-disable-werror.patch
+ bugfix/powerpc/lpar-console.patch
+ features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch
+ debian/arch-sh4-fix-uimage-build.patch
+ bugfix/mips/mips-ide-flush-dcache.patch
+ bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch
+
bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$ LC_ALL=C fakeroot make -f
debian/rules.gen setup_i386_none_686 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86' LOCALVERSION='-686'
LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686' MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS Makefile README
REPORTING-BUGS arch block crypto drivers firmware fs include init ipc kernel
lib mm net samples scripts security sound tools usr virt .gitignore .mailmap
'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must support
the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
6 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
(+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
(+) OK mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
(+) OK linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
(+) OK tpm-fix/tpm-Autodetect-itpm-devices.patch
(+) OK
for-drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
(+) FAIL
for-drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
make[1]: *** [debian/stamps/source] Error 1
make[1]: Leaving directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
make: *** [setup_i386_none_686_real] Error 2
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 6:27 PM, Sedat Dilek wrote: > On Sun, Nov 14, 2010 at 6:14 PM, Daniel Vetter wrote: >> On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote: >>> If you could geneate a patchset w/o i915 parts for testing would be cool. >>> Thanks in advance. >> >> Just drop patches 5-9 (you can apply patch 8 without any problems, it's >> just not gonna do anything without patch 9 ;). After all, this patch >> series is supposed to be bisectable, so stopping anywhere in between >> should result in a working kernel. >> >> -Daniel >> -- >> Daniel Vetter >> Mail: dan...@ffwll.ch >> Mobile: +41 (0)79 365 57 48 >> > > Njet :-( > > I am cloning linux-next GIT and pull into drm-next to see if there is > sth. missing. > > - Sedat - > NOPE, linux-next is up-to-date what drm-next concerns. - Sedat - s...@tbox:/mnt/sdb5/linux-kernel$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Cloning into linux-next... remote: Counting objects: 3084175, done. remote: Compressing objects: 100% (404388/404388), done. remote: Total 3084175 (delta 2687481), reused 3050014 (delta 2653407) Receiving objects: 100% (3084175/3084175), 513.53 MiB | 566 KiB/s, done. Resolving deltas: 100% (2687481/2687481), done. s...@tbox:/mnt/sdb5/linux-kernel$ tar -cf files/linux-next_git_next-20101112.tar linux-next/ s...@tbox:/mnt/sdb5/linux-kernel$ cd linux-next/ s...@tbox:/mnt/sdb5/linux-kernel/linux-next$ git pull git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-next >From git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 * branchdrm-next -> FETCH_HEAD Already up-to-date. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote: > NOPE, linux-next is up-to-date what drm-next concerns. Sorry for wasting your time, I've totally forgotten about a patch in drm-intel-next (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git), namely: commit d935cc61d466f6cc7514032835f4fc379cb7e2ca Author: Daniel Vetter Date: Thu Sep 16 15:13:11 2010 +0200 drm_mm: add support for range-restricted fair-lru scans That one's necessary, too. Yours, Daniel -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
Found myself :-) $ ls -l 0001-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch -rw-r--r-- 1 sd sd 3620 14. Nov 19:15 0001-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch On Sun, Nov 14, 2010 at 7:14 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote: >> NOPE, linux-next is up-to-date what drm-next concerns. > > Sorry for wasting your time, I've totally forgotten about a patch in > drm-intel-next > (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git), > namely: > > commit d935cc61d466f6cc7514032835f4fc379cb7e2ca > Author: Daniel Vetter > Date: Thu Sep 16 15:13:11 2010 +0200 > > drm_mm: add support for range-restricted fair-lru scans > > That one's necessary, too. > > Yours, Daniel > -- > Daniel Vetter > Mail: dan...@ffwll.ch > Mobile: +41 (0)79 365 57 48 > ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 7:14 PM, Daniel Vetter wrote:
> On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote:
>> NOPE, linux-next is up-to-date what drm-next concerns.
>
> Sorry for wasting your time, I've totally forgotten about a patch in
> drm-intel-next
> (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git),
> namely:
>
> commit d935cc61d466f6cc7514032835f4fc379cb7e2ca
> Author: Daniel Vetter
> Date: Thu Sep 16 15:13:11 2010 +0200
>
> drm_mm: add support for range-restricted fair-lru scans
>
> That one's necessary, too.
>
> Yours, Daniel
> --
> Daniel Vetter
> Mail: dan...@ffwll.ch
> Mobile: +41 (0)79 365 57 48
>
Hmm, I tried with your patches from ML plus missing patch and
extracted patches from ~danvet/drm/embed-gtt-space.
Sth. messed up
Could be a "big.diff" is needed, *not* a chronological series.
I will do a big.diff from 0081..0089 and apply
0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first.
- Sedat -
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$ grep ^+ debian/patches/series/base
+ linux-next/patch-v2.6.37-rc1-next-20101112
+ linux-next/0001-Remove-localversion-next.patch
+ for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
+ mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
+ mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
+ linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
+ tpm-fix/tpm-Autodetect-itpm-devices.patch
+
extracted-from-embed-gtt-space/0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch
+
extracted-from-embed-gtt-space/0081-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
+ extracted-from-embed-gtt-space/0082-drm-mm-track-free-areas-implicitly.patch
+
extracted-from-embed-gtt-space/0083-drm-mm-extract-node-insert-helper-functions.patch
+
extracted-from-embed-gtt-space/0084-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch
+
extracted-from-embed-gtt-space/0085-drm-i915-embed-struct-drm_mm_node-into-struct-drm_i9.patch
+ extracted-from-embed-gtt-space/0086-drm-i915-kill-obj-gtt_offset.patch
+ extracted-from-embed-gtt-space/0087-drm-i915-kill-gtt_list.patch
+
extracted-from-embed-gtt-space/0088-drm-mm-add-helper-to-unwind-scan-state.patch
+
extracted-from-embed-gtt-space/0089-drm-i915-use-drm_mm_for_each_scanned_node_reverse-he.patch
+ debian/version.patch
+ debian/kernelvariables-2.6.37.patch
+ debian/doc-build-parallel.patch
+ bugfix/ia64/hardcode-arch-script-output.patch
+ bugfix/mips/disable-advansys.patch
+ bugfix/arm/disable-scsi_acard.patch
+ debian/mips-disable-werror.patch
+ bugfix/powerpc/lpar-console.patch
+ features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch
+ debian/arch-sh4-fix-uimage-build.patch
+ bugfix/mips/mips-ide-flush-dcache.patch
+ bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch
+
bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$
s...@tbox:~/src/linux-2.6/linux-2.6.37-rc1$ LC_ALL=C fakeroot make -f
debian/rules.gen setup_i386_none_686 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config
debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86'
LOCALVERSION='-686' LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686'
MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS
Makefile README REPORTING-BUGS arch block crypto drivers firmware fs
include init ipc kernel lib mm net samples scripts security sound
tools usr virt .gitignore .mailmap 'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must
support the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
5 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
(+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
(+) OK mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patc
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 07:31:24PM +0100, Sedat Dilek wrote: > Hmm, I tried with your patches from ML plus missing patch and > extracted patches from ~danvet/drm/embed-gtt-space. > Sth. messed up > > Could be a "big.diff" is needed, *not* a chronological series. > I will do a big.diff from 0081..0089 and apply > 0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first. I've pushed out a for-sedat-dilek branch to my fdo repo. That one compiles ... Patches simply cherry-picked with git. -Daniel -- Daniel Vetter Mail: dan...@ffwll.ch Mobile: +41 (0)79 365 57 48 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 7:54 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 07:31:24PM +0100, Sedat Dilek wrote: >> Hmm, I tried with your patches from ML plus missing patch and >> extracted patches from ~danvet/drm/embed-gtt-space. >> Sth. messed up >> >> Could be a "big.diff" is needed, *not* a chronological series. >> I will do a big.diff from 0081..0089 and apply >> 0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first. > I've pushed out a for-sedat-dilek branch to my fdo repo. That one compiles > ... Patches simply cherry-picked with git. > -Daniel > -- > Daniel Vetter > Mail: dan...@ffwll.ch > Mobile: +41 (0)79 365 57 48 > After erasing my source-dir and re-unpacking Linux-2.6.37-rc1 tarball, I could apply the ~danvet/drm/for-sedat-dilek GIT branch. Thanks also for the hints on IRC. Just compiling my "big" patch-series: $ grep OK setup_linux-next_next-20101112.1.log (+) OK linux-next/patch-v2.6.37-rc1-next-20101112 (+) OK linux-next/0001-Remove-localversion-next.patch (+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch (+) OK none-BKL-config/drm-i810-remove-SMP-support-and-BKL.patch (+) OK drm-vblank-timestamping/1-3-drm-vblank-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/2-3-kms-radeon-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/drm-i915-fix-assignment-obj_priv-to_intel_bo.patch (+) OK drm-vblank-timestamping/3-3-kms-i915-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/drm-i915-fix-error-implicit-declaration-of-function-IS_IRONLAKE.patch (+) OK agd5f-pflip/0002-drm-radeon-kms-add-pageflip-ioctl-support.patch (+) OK backlight-type/Backlight-Add-backlight-type-v2.patch (+) OK backlight-type/radeon-Expose-backlight-class-device-for-legacy-LVDS-encoder.patch (+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch (+) OK mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch (+) OK linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch (+) OK tpm-fix/tpm-Autodetect-itpm-devices.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/1-3-drm-radeon-embed-struct-drm_gem_object.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/2-3-drm-radeon-introduce-gem_to_radeon_bo-helper.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/3-3-drm-radeon-kill-radeon_bo--gobj-pointer.patch (+) OK danvet-drm-for-sedat-dilek/0001-drm-nouveau-don-t-munge-in-drm_mm-internals.patch (+) OK danvet-drm-for-sedat-dilek/0002-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch (+) OK danvet-drm-for-sedat-dilek/0003-drm-mm-track-free-areas-implicitly.patch (+) OK danvet-drm-for-sedat-dilek/0004-drm-mm-extract-node-insert-helper-functions.patch (+) OK danvet-drm-for-sedat-dilek/0005-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch (+) OK danvet-drm-for-sedat-dilek/0006-drm-mm-add-helper-to-unwind-scan-state.patch (+) OK debian/version.patch (+) OK debian/kernelvariables-2.6.37.patch (+) OK debian/doc-build-parallel.patch (+) OK bugfix/ia64/hardcode-arch-script-output.patch (+) OK bugfix/mips/disable-advansys.patch (+) OK bugfix/arm/disable-scsi_acard.patch (+) OK debian/mips-disable-werror.patch (+) OK bugfix/powerpc/lpar-console.patch (+) OK features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch (+) OK debian/arch-sh4-fix-uimage-build.patch (+) OK bugfix/mips/mips-ide-flush-dcache.patch (+) OK bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch (+) OK bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31482] When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 --- Comment #11 from Maximiliano Castañón 2010-11-14 15:23:12 PST --- Please refer to https://bugs.freedesktop.org/show_bug.cgi?id=31475 I believe it's another project related to that problem, probably xrandr with the resize screen... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/kms: fix and unify tiled buffer alignment checking for r6xx/7xx
Tiled buffers have the same alignment requirements regardless of
whether the surface is for db, cb, or textures. Previously, the
calculations where inconsistent for each buffer type.
- Unify the alignment calculations in a common function
- Standardize the alignment units (pixels for pitch/height/depth,
bytes for base)
- properly check the buffer base alignments
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/r600_cs.c | 309 --
drivers/gpu/drm/radeon/r600d.h |6 +
2 files changed, 199 insertions(+), 116 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r600_cs.c b/drivers/gpu/drm/radeon/r600_cs.c
index 37cc2aa..0f90fc3 100644
--- a/drivers/gpu/drm/radeon/r600_cs.c
+++ b/drivers/gpu/drm/radeon/r600_cs.c
@@ -50,6 +50,7 @@ struct r600_cs_track {
u32 nsamples;
u32 cb_color_base_last[8];
struct radeon_bo*cb_color_bo[8];
+ u64 cb_color_bo_mc[8];
u32 cb_color_bo_offset[8];
struct radeon_bo*cb_color_frag_bo[8];
struct radeon_bo*cb_color_tile_bo[8];
@@ -67,6 +68,7 @@ struct r600_cs_track {
u32 db_depth_size;
u32 db_offset;
struct radeon_bo*db_bo;
+ u64 db_bo_mc;
};
static inline int r600_bpe_from_format(u32 *bpe, u32 format)
@@ -140,6 +142,68 @@ static inline int r600_bpe_from_format(u32 *bpe, u32
format)
return 0;
}
+struct array_mode_checker {
+ int array_mode;
+ u32 group_size;
+ u32 nbanks;
+ u32 npipes;
+ u32 nsamples;
+ u32 bpe;
+};
+
+/* returns alignment in pixels for pitch/height/depth and bytes for base */
+static inline int r600_get_array_mode_alignment(struct array_mode_checker
*values,
+ u32 *pitch_align,
+ u32 *height_align,
+ u32 *depth_align,
+ u64 *base_align)
+{
+ u32 tile_width = 8;
+ u32 tile_height = 8;
+ u32 macro_tile_width = values->nbanks;
+ u32 macro_tile_height = values->npipes;
+ u32 tile_bytes = tile_width * tile_height * values->bpe *
values->nsamples;
+ u32 macro_tile_bytes = macro_tile_width * macro_tile_height *
tile_bytes;
+
+ switch (values->array_mode) {
+ case ARRAY_LINEAR_GENERAL:
+ /* technically tile_width/_height for pitch/height */
+ *pitch_align = 1; /* tile_width */
+ *height_align = 1; /* tile_height */
+ *depth_align = 1;
+ *base_align = 1;
+ break;
+ case ARRAY_LINEAR_ALIGNED:
+ *pitch_align = max((u32)64, (u32)(values->group_size /
values->bpe));
+ *height_align = tile_height;
+ *depth_align = 1;
+ *base_align = values->group_size;
+ break;
+ case ARRAY_1D_TILED_THIN1:
+ *pitch_align = max((u32)tile_width,
+ (u32)(values->group_size /
+(tile_height * values->bpe *
values->nsamples)));
+ *height_align = tile_height;
+ *depth_align = 1;
+ *base_align = values->group_size;
+ break;
+ case ARRAY_2D_TILED_THIN1:
+ *pitch_align = max((u32)macro_tile_width,
+ (u32)(((values->group_size / tile_height) /
+(values->bpe * values->nsamples)) *
+ values->nbanks)) * tile_width;
+ *height_align = macro_tile_height * tile_height;
+ *depth_align = 1;
+ *base_align = max(macro_tile_bytes,
+ (*pitch_align) * values->bpe *
(*height_align) * values->nsamples);
+ break;
+ default:
+ return -EINVAL;
+ }
+
+ return 0;
+}
+
static void r600_cs_track_init(struct r600_cs_track *track)
{
int i;
@@ -153,10 +217,12 @@ static void r600_cs_track_init(struct r600_cs_track
*track)
track->cb_color_info[i] = 0;
track->cb_color_bo[i] = NULL;
track->cb_color_bo_offset[i] = 0x;
+ track->cb_color_bo_mc[i] = 0x;
}
track->cb_target_mask = 0x;
track->cb_shader_mask = 0x;
track->db_bo = NULL;
+ track->db_bo_mc = 0x;
/* assume the biggest format and that htile is enabled */
track->db_depth_info = 7 | (1 << 25);
track->db_depth_view = 0xC000;
@@ -168,7 +234,10 @@ static void r600_cs_track_init(struct r600_cs_track *track)
static inline int r600_cs_track_validate_cb(struct radeon_cs_parser *p, int i
[Bug 31617] Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled
https://bugs.freedesktop.org/show_bug.cgi?id=31617 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Alex Deucher 2010-11-14 22:37:36 PST --- Thanks. Fix pushed to master: ef0720758e5ba34d0d163bdf5efc6e8dabd65aa8 and 7.9: 9b1ac4d127805f6a14415596e4a557fad3d570a5 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm: radeon: fix error value sign
enable_vblank implementations should use negative result to indicate error.
radeon_enable_vblank() returns EINVAL in this case. Change this to -EINVAL.
Signed-off-by: Vasiliy Kulikov
---
Compile tested.
drivers/gpu/drm/radeon/radeon_irq.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_irq.c
b/drivers/gpu/drm/radeon/radeon_irq.c
index 2f349a3..465746b 100644
--- a/drivers/gpu/drm/radeon/radeon_irq.c
+++ b/drivers/gpu/drm/radeon/radeon_irq.c
@@ -76,7 +76,7 @@ int radeon_enable_vblank(struct drm_device *dev, int crtc)
default:
DRM_ERROR("tried to enable vblank on non-existent crtc
%d\n",
crtc);
- return EINVAL;
+ return -EINVAL;
}
} else {
switch (crtc) {
@@ -89,7 +89,7 @@ int radeon_enable_vblank(struct drm_device *dev, int crtc)
default:
DRM_ERROR("tried to enable vblank on non-existent crtc
%d\n",
crtc);
- return EINVAL;
+ return -EINVAL;
}
}
--
1.7.0.4
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/3] embed drm_gem_object into radeon_bo
Hi, Daniel, My main concerns previously for embedding GEM objects as user-space references for TTM has been twofold and implementation specific. 1) The locking has been using global mutexes where local spin- or RCU locks have been more appropriate. It looks like this has finally been / is finally going to be addressed. 2) The gem object is too specialized for general purpose use: a) The shmem member has no natural use with TTM except possibly as a persistent swap storage, but in an ideal world, TTM would talk to the swap cache directly so in the longer term there is no need for the shmem object at all. b) Implementations may want to use other user-space visible objects than buffer objects: For example fence objects or CPU synchronization objects. The common traits of / operations on these are user-space visibility, inter-process visibility, refcounting and destruction when the relevant file is closed. Hence a class that provides only the user-space handles, naming (flink), refcounting and registering with a file handle would be the best choice of a "base" class. Traditional Gem objects could derive from those and provide any extra *generic* members needed for buffer objects. This doesn't really affect your work though. Just some comments on why vmwgfx don't use GEM objects by default and how they could be made optimal for TTM-aware drivers. Thanks, /Thomas On 11/13/2010 09:57 PM, Daniel Vetter wrote: Hi all, This patch series embeds drm_gem_object into struct radeon_bo and adjusts any references. I've decided against embedding the gem stuff into struct ttm_bo because - vmwgfx doesn't use gem and - ttm is used for implementing the memory management, whereas gem provides the userspace interface (I know, there's some overlap there, but that's not really a new problem). Please review and consider merging for -next. Yours, Daniel Daniel Vetter (3): drm/radeon: embed struct drm_gem_object drm/radeon: introduce gem_to_radeon_bo helper drm/radeon: kill radeon_bo->gobj pointer drivers/gpu/drm/radeon/atombios_crtc.c |8 ++-- drivers/gpu/drm/radeon/evergreen_blit_kms.c |2 +- drivers/gpu/drm/radeon/r600.c |2 +- drivers/gpu/drm/radeon/r600_blit_kms.c |2 +- drivers/gpu/drm/radeon/radeon.h |3 +- drivers/gpu/drm/radeon/radeon_benchmark.c |4 +- drivers/gpu/drm/radeon/radeon_cs.c |2 +- drivers/gpu/drm/radeon/radeon_device.c |4 +- drivers/gpu/drm/radeon/radeon_fb.c | 10 +++--- drivers/gpu/drm/radeon/radeon_gart.c|2 +- drivers/gpu/drm/radeon/radeon_gem.c | 43 --- drivers/gpu/drm/radeon/radeon_legacy_crtc.c |4 +- drivers/gpu/drm/radeon/radeon_object.c | 24 +++ drivers/gpu/drm/radeon/radeon_object.h |2 +- drivers/gpu/drm/radeon/radeon_ring.c|4 +- drivers/gpu/drm/radeon/radeon_test.c|4 +- drivers/gpu/drm/radeon/radeon_ttm.c |2 +- drivers/gpu/drm/radeon/rv770.c |2 +- 18 files changed, 59 insertions(+), 65 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] make struct drm_mm_node embeddable
On 11/12/2010 06:36 PM, Daniel Vetter wrote: Hi all, This patch-set changes the algorithm in drm_mm.c to not need additional allocations to track free space and adds an api to make embedding struct drm_mm_node possible. Benefits: - If struct drm_mm_node is provided, no allocations need to be done anymore in drm_mm. It looks like some decent surgery, but ttm should be able to drop its preallocation dance. - void *priv is back, but done right ;) - Avoids a pointer chase when lru-scanning in i915 and saves a few bytes. As a proof of concept I've converted i915. Beware though, the drm/i915 patches depend on my direct-gtt patches (which are actually the reason for this series here). Tested on my i855gm, i945gme, ironlake and agp rv570. Comments, flames, reviews highly welcome. Hi, Daniel! Nice work, although I have some comments about general applicability that we perhaps need to think about. 1) The space representation and space allocation algorithm is something that is private to the aperture management system. For a specialized implementation like i915 that is all fine, but Ben has recently abstracted that part out of the core TTM bo implementation. As an example, vmwgfx is now using kernel idas to manage aperture space, and drm_mm objects for traditional VRAM space. Hence, embedding drm_mm objects into ttm bos will not really be worthwile. At least not for aperture space management, and TTM will need to continue to "dance", both in the ida case and in the drm_mm case. For device address space, the situation is different, though, and it should be possible to embed the drm_mm objects, but that brings up the next thing: 2) The algorithm used by drm_mm has been around for a while and has seen a fair amount of changes, but nobody has yet attacked the algorithm used to search for free space, which was just quickly put together as an improvement on what was the old mesa range manager. In moderate fragmentation situations, the performance will degrade, particularly with "best match" searches. In the near future we'd probably want to add something like a "hole rb tree" rather than a "hole list", and a choice of algorithm for the user. With embeddable objects, unless you want to waste space for unused members, you'd need a separate drm_mm node subclass for each algorithm, whereas if you don't embed, you only need to allocate what you need. /Thomas Please consider merging the core drm parts (and the nouveau prep patch) for -next (the i915 patches need coordination with Chris Wilson, they're rather invasive). Thanks, Daniel Daniel Vetter (9): drm/nouveau: don't munge in drm_mm internals drm: mm: track free areas implicitly drm: mm: extract node insert helper functions drm: mm: add api for embedding struct drm_mm_node drm/i915: embed struct drm_mm_node into struct drm_i915_gem_object drm/i915: kill obj->gtt_offset drm/i915: kill gtt_list drm: mm: add helper to unwind scan state drm/i915: use drm_mm_for_each_scanned_node_reverse helper drivers/gpu/drm/drm_mm.c | 570 - drivers/gpu/drm/i915/i915_debugfs.c | 22 +- drivers/gpu/drm/i915/i915_drv.h | 13 +- drivers/gpu/drm/i915/i915_gem.c | 173 - drivers/gpu/drm/i915/i915_gem_debug.c| 10 +- drivers/gpu/drm/i915/i915_gem_evict.c| 37 +- drivers/gpu/drm/i915/i915_gem_gtt.c | 14 +- drivers/gpu/drm/i915/i915_gem_tiling.c |6 +- drivers/gpu/drm/i915/i915_irq.c | 34 +- drivers/gpu/drm/i915/intel_display.c | 26 +- drivers/gpu/drm/i915/intel_fb.c |6 +- drivers/gpu/drm/i915/intel_overlay.c | 14 +- drivers/gpu/drm/i915/intel_ringbuffer.c | 10 +- drivers/gpu/drm/nouveau/nouveau_object.c |2 +- drivers/gpu/drm/nouveau/nv50_instmem.c |2 +- include/drm/drm_mm.h | 49 ++- 16 files changed, 525 insertions(+), 463 deletions(-) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 31615] New: Some textures broken on r600g
https://bugs.freedesktop.org/show_bug.cgi?id=31615 Summary: Some textures broken on r600g Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: direx at betriebsdirektor.de I've been using r600g for quite a while and it was working well. Since commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9 XBMC does not display any fonts in the menus any more (XBMC svn, default skin) - I suspect it's a texture problem. To me it looks like this commit is responsible for this problem: commit 63c3e3a3dc73f8a72e0d08ac4453df57bccdfdb9 Author: Keith Whitwell Date: Tue Nov 9 20:08:45 2010 + r600: fix my pessimism about PIPE_TRANSFER_x flags -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31615] Some textures broken on r600g
https://bugs.freedesktop.org/show_bug.cgi?id=31615 Daniel changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #1 from Daniel 2010-11-14 02:58:23 PST --- *** This bug has been marked as a duplicate of bug 31613 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31613] UI Fonts in Blender are not visible with recent Mesa.
https://bugs.freedesktop.org/show_bug.cgi?id=31613 Daniel changed: What|Removed |Added CC||direx at betriebsdirektor.de --- Comment #1 from Daniel 2010-11-14 02:58:23 PST --- *** Bug 31615 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 31617] New: Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled
https://bugs.freedesktop.org/show_bug.cgi?id=31617
Summary: Radeon/Compiz: 'failed to attach dri2 front buffer',
error case not handled
Product: Mesa
Version: 7.9
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel at lists.freedesktop.org
ReportedBy: daniel.lichtenberger at gmail.com
Created an attachment (id=40267)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40267)
backtrace
System: Fedora 14, Radeon 4850, x86_64.
Using the system's mesa-dri-drivers package Compiz frequently crashes while
resizing windows. The backtrace (attached) and the error message, "failed to
attach dri2 front buffer XX", point to radeon_update_renderbuffers in
radeon_common_context.c around line 745:
bo = radeon_bo_open(...);
if (bo == NULL) {
fprintf(stderr, "failed to attach %s %d\n",
regname, buffers[i].name);
}
ret = radeon_bo_get_tiling(bo, &tiling_flags, &pitch);
An error message is printed when 'bo' could not be allocated, but bo is then
happily dereferenced in radeon_bo_get_tiling afterwards. Working around the
null pointer dereference (e.g. by adding a 'continue' in the "if bo==NULL"
block) fixes the crash for me and I haven't seen visual artifacts yet, although
the error message is printed from time to time while running Compiz.
The same stacktrace was logged by several people over at
https://bugzilla.redhat.com/show_bug.cgi?id=568593.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
[PATCH 0/9] make struct drm_mm_node embeddable
[ Please CC me I am not subscribed to dri-devel ML ]
[ QUOTE ]
Hi all,
This patch-set changes the algorithm in drm_mm.c to not need additional
allocations to track free space and adds an api to make embedding struct
drm_mm_node possible. Benefits:
- If struct drm_mm_node is provided, no allocations need to be done anymore
in drm_mm. It looks like some decent surgery, but ttm should be able to
drop its preallocation dance.
- void *priv is back, but done right ;)
- Avoids a pointer chase when lru-scanning in i915 and saves a few bytes.
As a proof of concept I've converted i915. Beware though, the drm/i915
patches depend on my direct-gtt patches (which are actually the reason for
this series here).
Tested on my i855gm, i945gme, ironlake and agp rv570.
Comments, flames, reviews highly welcome.
[ /QUOTE ]
Against which GIT tree or linux-next version are these patchset for?
- Sedat -
$ cd ~/src/linux-2.6/linux-2.6.37-rc1
$ echo $SINGLE_KERNEL_VARIANT
i386_none_686
$ LC_ALL=C fakeroot make -f debian/rules.gen
setup_${SINGLE_KERNEL_VARIANT} 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config
debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86'
LOCALVERSION='-686' LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686'
MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS
Makefile README REPORTING-BUGS arch block crypto drivers firmware fs
include init ipc kernel lib mm net samples scripts security sound
tools usr virt .gitignore .mailmap 'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must
support the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
1 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK
for-linux-next/drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
(+) FAIL
for-linux-next/drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
make[1]: *** [debian/stamps/source] Error 1
make[1]: Leaving directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
make: *** [setup_i386_none_686_real] Error 2
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, 14 Nov 2010 15:03:31 +0100, Sedat Dilek wrote: > [ Please CC me I am not subscribed to dri-devel ML ] > > [ QUOTE ] > As a proof of concept I've converted i915. Beware though, the drm/i915 > patches depend on my direct-gtt patches (which are actually the reason for > this series here). > > [ /QUOTE ] > > Against which GIT tree or linux-next version are these patchset for? git://anongit.freedesktop.org/~danvet/drm direct-gtt -Chris -- Chris Wilson, Intel Open Source Technology Centre
[Bug 31619] New: Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 Summary: Desktop freezes quickly every now and then with dynpm Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: ernstp at gmail.com This is with linux 2.6.37 from xorg-edgers. If I do echo dynpm > /sys/class/drm/card0/device/power_method Run compiz Grab a window and move it around, every now it freezes quickly and the resumes. The mouse movement during that period is completely lost. I'll try more kernels... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 3:38 PM, Chris Wilson wrote: > On Sun, 14 Nov 2010 15:03:31 +0100, Sedat Dilek googlemail.com> wrote: >> [ Please CC me I am not subscribed to dri-devel ML ] >> >> [ QUOTE ] >> As a proof of concept I've converted i915. Beware though, the drm/i915 >> patches depend on my direct-gtt patches (which are actually the reason for >> this series here). >> >> [ /QUOTE ] >> >> Against which GIT tree or linux-next version are these patchset for? > > git://anongit.freedesktop.org/~danvet/drm direct-gtt > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre > Thank you for the pointer to the right GIT repository and branch. Looks like [1] has Daniel's patchset (9 patches) already included. To attract more people for testing or joining it would be appreciated these interesting work would be (re)based on Dave's drm-next GIT tree, as this one is going to linux-next. Or is drm-next/linux-next work for intel-gfxcards done elsewhere? Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or Linus-tree is causing conflicts. - Sedat - [1] http://cgit.freedesktop.org/~danvet/drm/log/?h=embed-gtt-space
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 04:52:43PM +0100, Sedat Dilek wrote: > Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or > Linus-tree is causing conflicts. I've just retested merging with drm-core-next / drm-next and the core drm_mm parts merge without conflict. The i915 parts fail all over due to conflicts with other ongoing stuff. As I've said, these patches are just proof-of-concept, I need to redo them (and coordinate merging with Chris Wilson). So either test my embed-gtt-space branch to also enjoy the i915 patches. Or only test the drm core changes. -Daniel > [1] http://cgit.freedesktop.org/~danvet/drm/log/?h=embed-gtt-space -- Daniel Vetter Mail: daniel at ffwll.ch Mobile: +41 (0)79 365 57 48
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 5:13 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 04:52:43PM +0100, Sedat Dilek wrote: >> Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or >> Linus-tree is causing conflicts. > > I've just retested merging with drm-core-next / drm-next and the core > drm_mm parts merge without conflict. The i915 parts fail all over due to > conflicts with other ongoing stuff. As I've said, these patches are just > proof-of-concept, I need to redo them (and coordinate merging with Chris > Wilson). So either test my embed-gtt-space branch to also enjoy the i915 > patches. Or only test the drm core changes. > If you could geneate a patchset w/o i915 parts for testing would be cool. Thanks in advance. - Sedat -
[Bug 31619] Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 --- Comment #1 from Ernst Sj?strand 2010-11-14 09:07:37 PST --- It also happens with the drm-next kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2010-11-10-maverick/ It does not happen with Ubuntu Mavericks default 2.6.35 kernel. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote: > If you could geneate a patchset w/o i915 parts for testing would be cool. > Thanks in advance. Just drop patches 5-9 (you can apply patch 8 without any problems, it's just not gonna do anything without patch 9 ;). After all, this patch series is supposed to be bisectable, so stopping anywhere in between should result in a working kernel. -Daniel -- Daniel Vetter Mail: daniel at ffwll.ch Mobile: +41 (0)79 365 57 48
[Bug 31619] Desktop freezes quickly every now and then with dynpm
https://bugs.freedesktop.org/show_bug.cgi?id=31619 --- Comment #2 from Alex Deucher 2010-11-14 09:19:58 PST --- This is due to the pm code holding a number of locks while waiting to update the clocks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 6:14 PM, Daniel Vetter wrote:
> On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote:
>> If you could geneate a patchset w/o i915 parts for testing would be cool.
>> Thanks in advance.
>
> Just drop patches 5-9 (you can apply patch 8 without any problems, it's
> just not gonna do anything without patch 9 ;). After all, this patch
> series is supposed to be bisectable, so stopping anywhere in between
> should result in a working kernel.
>
> -Daniel
> --
> Daniel Vetter
> Mail: daniel at ffwll.ch
> Mobile: +41 (0)79 365 57 48
>
Njet :-(
I am cloning linux-next GIT and pull into drm-next to see if there is
sth. missing.
- Sedat -
-- next part --
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$ grep ^+ debian/patches/series/base
+ linux-next/patch-v2.6.37-rc1-next-20101112
+ linux-next/0001-Remove-localversion-next.patch
+ for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
+ mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
+ mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
+ linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
+ tpm-fix/tpm-Autodetect-itpm-devices.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/3-9-drm-mm-extract-node-insert-helper-functions.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/4-9-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch
+
for-drm-next/make-struct-drm_mm_node-embeddable/8-9-drm-mm-add-helper-to-unwind-scan-state.patch
+ debian/version.patch
+ debian/kernelvariables-2.6.37.patch
+ debian/doc-build-parallel.patch
+ bugfix/ia64/hardcode-arch-script-output.patch
+ bugfix/mips/disable-advansys.patch
+ bugfix/arm/disable-scsi_acard.patch
+ debian/mips-disable-werror.patch
+ bugfix/powerpc/lpar-console.patch
+ features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch
+ debian/arch-sh4-fix-uimage-build.patch
+ bugfix/mips/mips-ide-flush-dcache.patch
+ bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch
+
bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$ LC_ALL=C fakeroot make -f
debian/rules.gen setup_i386_none_686 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86' LOCALVERSION='-686'
LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686' MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS Makefile README
REPORTING-BUGS arch block crypto drivers firmware fs include init ipc kernel
lib mm net samples scripts security sound tools usr virt .gitignore .mailmap
'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must support
the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
6 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
(+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
(+) OK mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
(+) OK linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
(+) OK tpm-fix/tpm-Autodetect-itpm-devices.patch
(+) OK
for-drm-next/make-struct-drm_mm_node-embeddable/1-9-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
(+) FAIL
for-drm-next/make-struct-drm_mm_node-embeddable/2-9-drm-mm-track-free-areas-implicitly.patch
make[1]: *** [debian/stamps/source] Error 1
make[1]: Leaving directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
make: *** [setup_i386_none_686_real] Error 2
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 6:27 PM, Sedat Dilek wrote: > On Sun, Nov 14, 2010 at 6:14 PM, Daniel Vetter wrote: >> On Sun, Nov 14, 2010 at 05:56:04PM +0100, Sedat Dilek wrote: >>> If you could geneate a patchset w/o i915 parts for testing would be cool. >>> Thanks in advance. >> >> Just drop patches 5-9 (you can apply patch 8 without any problems, it's >> just not gonna do anything without patch 9 ;). After all, this patch >> series is supposed to be bisectable, so stopping anywhere in between >> should result in a working kernel. >> >> -Daniel >> -- >> Daniel Vetter >> Mail: daniel at ffwll.ch >> Mobile: +41 (0)79 365 57 48 >> > > Njet :-( > > I am cloning linux-next GIT and pull into drm-next to see if there is > sth. missing. > > - Sedat - > NOPE, linux-next is up-to-date what drm-next concerns. - Sedat - sd at tbox:/mnt/sdb5/linux-kernel$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Cloning into linux-next... remote: Counting objects: 3084175, done. remote: Compressing objects: 100% (404388/404388), done. remote: Total 3084175 (delta 2687481), reused 3050014 (delta 2653407) Receiving objects: 100% (3084175/3084175), 513.53 MiB | 566 KiB/s, done. Resolving deltas: 100% (2687481/2687481), done. sd at tbox:/mnt/sdb5/linux-kernel$ tar -cf files/linux-next_git_next-20101112.tar linux-next/ sd at tbox:/mnt/sdb5/linux-kernel$ cd linux-next/ sd at tbox:/mnt/sdb5/linux-kernel/linux-next$ git pull git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-next
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote: > NOPE, linux-next is up-to-date what drm-next concerns. Sorry for wasting your time, I've totally forgotten about a patch in drm-intel-next (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git), namely: commit d935cc61d466f6cc7514032835f4fc379cb7e2ca Author: Daniel Vetter Date: Thu Sep 16 15:13:11 2010 +0200 drm_mm: add support for range-restricted fair-lru scans That one's necessary, too. Yours, Daniel -- Daniel Vetter Mail: daniel at ffwll.ch Mobile: +41 (0)79 365 57 48
[PATCH 0/9] make struct drm_mm_node embeddable
Found myself :-) $ ls -l 0001-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch -rw-r--r-- 1 sd sd 3620 14. Nov 19:15 0001-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch On Sun, Nov 14, 2010 at 7:14 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote: >> NOPE, linux-next is up-to-date what drm-next concerns. > > Sorry for wasting your time, I've totally forgotten about a patch in > drm-intel-next > (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git), > namely: > > commit d935cc61d466f6cc7514032835f4fc379cb7e2ca > Author: Daniel Vetter > Date: ? Thu Sep 16 15:13:11 2010 +0200 > > ? ?drm_mm: add support for range-restricted fair-lru scans > > That one's necessary, too. > > Yours, Daniel > -- > Daniel Vetter > Mail: daniel at ffwll.ch > Mobile: +41 (0)79 365 57 48 >
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 7:14 PM, Daniel Vetter wrote:
> On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote:
>> NOPE, linux-next is up-to-date what drm-next concerns.
>
> Sorry for wasting your time, I've totally forgotten about a patch in
> drm-intel-next
> (git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git),
> namely:
>
> commit d935cc61d466f6cc7514032835f4fc379cb7e2ca
> Author: Daniel Vetter
> Date: ? Thu Sep 16 15:13:11 2010 +0200
>
> ? ?drm_mm: add support for range-restricted fair-lru scans
>
> That one's necessary, too.
>
> Yours, Daniel
> --
> Daniel Vetter
> Mail: daniel at ffwll.ch
> Mobile: +41 (0)79 365 57 48
>
Hmm, I tried with your patches from ML plus missing patch and
extracted patches from ~danvet/drm/embed-gtt-space.
Sth. messed up
Could be a "big.diff" is needed, *not* a chronological series.
I will do a big.diff from 0081..0089 and apply
0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first.
- Sedat -
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$ grep ^+ debian/patches/series/base
+ linux-next/patch-v2.6.37-rc1-next-20101112
+ linux-next/0001-Remove-localversion-next.patch
+ for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
+ mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
+ mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch
+ linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch
+ tpm-fix/tpm-Autodetect-itpm-devices.patch
+
extracted-from-embed-gtt-space/0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch
+
extracted-from-embed-gtt-space/0081-drm-nouveau-don-t-munge-in-drm_mm-internals.patch
+ extracted-from-embed-gtt-space/0082-drm-mm-track-free-areas-implicitly.patch
+
extracted-from-embed-gtt-space/0083-drm-mm-extract-node-insert-helper-functions.patch
+
extracted-from-embed-gtt-space/0084-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch
+
extracted-from-embed-gtt-space/0085-drm-i915-embed-struct-drm_mm_node-into-struct-drm_i9.patch
+ extracted-from-embed-gtt-space/0086-drm-i915-kill-obj-gtt_offset.patch
+ extracted-from-embed-gtt-space/0087-drm-i915-kill-gtt_list.patch
+
extracted-from-embed-gtt-space/0088-drm-mm-add-helper-to-unwind-scan-state.patch
+
extracted-from-embed-gtt-space/0089-drm-i915-use-drm_mm_for_each_scanned_node_reverse-he.patch
+ debian/version.patch
+ debian/kernelvariables-2.6.37.patch
+ debian/doc-build-parallel.patch
+ bugfix/ia64/hardcode-arch-script-output.patch
+ bugfix/mips/disable-advansys.patch
+ bugfix/arm/disable-scsi_acard.patch
+ debian/mips-disable-werror.patch
+ bugfix/powerpc/lpar-console.patch
+ features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch
+ debian/arch-sh4-fix-uimage-build.patch
+ bugfix/mips/mips-ide-flush-dcache.patch
+ bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch
+
bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$
sd at tbox:~/src/linux-2.6/linux-2.6.37-rc1$ LC_ALL=C fakeroot make -f
debian/rules.gen setup_i386_none_686 2>&1 | tee ../setup.log
make -f debian/rules.real setup-flavour ABINAME='' ARCH='i386'
COMPILER='gcc-4.4' FEATURESET='none' FLAVOUR='686'
INITRD_CMD='update-initramfs' KCONFIG='debian/config/config
debian/config/kernelarch-x86/config
debian/config/kernelarch-x86/config-arch-32
debian/config/i386/none/config.686' KERNEL_ARCH='x86'
LOCALVERSION='-686' LOCALVERSION_HEADERS='' LOCALVERSION_IMAGE='-686'
MAJOR='2.6' MODULES='True'
SOURCEVERSION='2.6.37~rc1-11~next~20101112.1~dileks.1' TYPE='plain'
UPSTREAMVERSION='2.6.37-rc1' VERSION='2.6.37'
make[1]: Entering directory `/home/sd/src/linux-2.6/linux-2.6.37-rc1'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild Kconfig MAINTAINERS
Makefile README REPORTING-BUGS arch block crypto drivers firmware fs
include init ipc kernel lib mm net samples scripts security sound
tools usr virt .gitignore .mailmap 'debian/build/source'
cd 'debian/build/source'; python
'/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply'
--overwrite-home='/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/patches'
/home/sd/src/linux-2.6/linux-2.6.37-rc1/debian/bin/patch.apply:81:
DeprecationWarning: functions overriding warnings.showwarning() must
support the 'line' argument
warn('No %s file, assuming Debian Linux %s' % (self._file, upstream))
Warning: No version.Debian file, assuming Debian Linux 2.6.37~rc1
5 out of 11 hunks FAILED -- saving rejects to file drivers/gpu/drm/drm_mm.c.rej
Error: Patch failed
--> Try to apply base.
(+) OK linux-next/patch-v2.6.37-rc1-next-20101112
(+) OK linux-next/0001-Remove-localversion-next.patch
(+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch
(+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch
(+) OK mm-fixes/kmemleak-remove-memset-by-using-kzal
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 07:31:24PM +0100, Sedat Dilek wrote: > Hmm, I tried with your patches from ML plus missing patch and > extracted patches from ~danvet/drm/embed-gtt-space. > Sth. messed up > > Could be a "big.diff" is needed, *not* a chronological series. > I will do a big.diff from 0081..0089 and apply > 0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first. I've pushed out a for-sedat-dilek branch to my fdo repo. That one compiles ... Patches simply cherry-picked with git. -Daniel -- Daniel Vetter Mail: daniel at ffwll.ch Mobile: +41 (0)79 365 57 48
[PATCH 0/9] make struct drm_mm_node embeddable
On Sun, Nov 14, 2010 at 7:54 PM, Daniel Vetter wrote: > On Sun, Nov 14, 2010 at 07:31:24PM +0100, Sedat Dilek wrote: >> Hmm, I tried with your patches from ML plus missing patch and >> extracted patches from ~danvet/drm/embed-gtt-space. >> Sth. messed up >> >> Could be a "big.diff" is needed, *not* a chronological series. >> I will do a big.diff from 0081..0089 and apply >> 0008-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch first. > I've pushed out a for-sedat-dilek branch to my fdo repo. That one compiles > ... Patches simply cherry-picked with git. > -Daniel > -- > Daniel Vetter > Mail: daniel at ffwll.ch > Mobile: +41 (0)79 365 57 48 > After erasing my source-dir and re-unpacking Linux-2.6.37-rc1 tarball, I could apply the ~danvet/drm/for-sedat-dilek GIT branch. Thanks also for the hints on IRC. Just compiling my "big" patch-series: $ grep OK setup_linux-next_next-20101112.1.log (+) OK linux-next/patch-v2.6.37-rc1-next-20101112 (+) OK linux-next/0001-Remove-localversion-next.patch (+) OK for-linux-next/next-iwlwifi-fix-modular-legacy-build-errors.patch (+) OK none-BKL-config/drm-i810-remove-SMP-support-and-BKL.patch (+) OK drm-vblank-timestamping/1-3-drm-vblank-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/2-3-kms-radeon-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/drm-i915-fix-assignment-obj_priv-to_intel_bo.patch (+) OK drm-vblank-timestamping/3-3-kms-i915-Add-support-for-precise-vblank-timestamping.patch (+) OK drm-vblank-timestamping/drm-i915-fix-error-implicit-declaration-of-function-IS_IRONLAKE.patch (+) OK agd5f-pflip/0002-drm-radeon-kms-add-pageflip-ioctl-support.patch (+) OK backlight-type/Backlight-Add-backlight-type-v2.patch (+) OK backlight-type/radeon-Expose-backlight-class-device-for-legacy-LVDS-encoder.patch (+) OK mm-fixes/cgroup-Avoid-a-memset-by-using-vzalloc.patch (+) OK mm-fixes/kmemleak-remove-memset-by-using-kzalloc.patch (+) OK linux-2.6-block-for-2.6.38-core/linux-2.6-block-for-2.6.38-core.patch (+) OK tpm-fix/tpm-Autodetect-itpm-devices.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/1-3-drm-radeon-embed-struct-drm_gem_object.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/2-3-drm-radeon-introduce-gem_to_radeon_bo-helper.patch (+) OK danvet-embed-drm_gem_object-into-radeon_bo/3-3-drm-radeon-kill-radeon_bo--gobj-pointer.patch (+) OK danvet-drm-for-sedat-dilek/0001-drm-nouveau-don-t-munge-in-drm_mm-internals.patch (+) OK danvet-drm-for-sedat-dilek/0002-drm_mm-add-support-for-range-restricted-fair-lru-sca.patch (+) OK danvet-drm-for-sedat-dilek/0003-drm-mm-track-free-areas-implicitly.patch (+) OK danvet-drm-for-sedat-dilek/0004-drm-mm-extract-node-insert-helper-functions.patch (+) OK danvet-drm-for-sedat-dilek/0005-drm-mm-add-api-for-embedding-struct-drm_mm_node.patch (+) OK danvet-drm-for-sedat-dilek/0006-drm-mm-add-helper-to-unwind-scan-state.patch (+) OK debian/version.patch (+) OK debian/kernelvariables-2.6.37.patch (+) OK debian/doc-build-parallel.patch (+) OK bugfix/ia64/hardcode-arch-script-output.patch (+) OK bugfix/mips/disable-advansys.patch (+) OK bugfix/arm/disable-scsi_acard.patch (+) OK debian/mips-disable-werror.patch (+) OK bugfix/powerpc/lpar-console.patch (+) OK features/all/i915-autoload-without-CONFIG_DRM_I915_KMS.patch (+) OK debian/arch-sh4-fix-uimage-build.patch (+) OK bugfix/mips/mips-ide-flush-dcache.patch (+) OK bugfix/all/qla4xxx-Fix-build-on-some-architectures-lacking-64-bit-I-O.patch (+) OK bugfix/x86/Skip-looking-for-ioapic-overrides-when-ioapics-are-not-present.patch
[Bug 31482] When trying to put the fullscreen window, data show and LCD laptop screen, the screen windwos screw up
https://bugs.freedesktop.org/show_bug.cgi?id=31482 --- Comment #11 from Maximiliano Casta??n 2010-11-14 15:23:12 PST --- Please refer to https://bugs.freedesktop.org/show_bug.cgi?id=31475 I believe it's another project related to that problem, probably xrandr with the resize screen... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm/radeon/kms: fix and unify tiled buffer alignment checking for r6xx/7xx
Tiled buffers have the same alignment requirements regardless of
whether the surface is for db, cb, or textures. Previously, the
calculations where inconsistent for each buffer type.
- Unify the alignment calculations in a common function
- Standardize the alignment units (pixels for pitch/height/depth,
bytes for base)
- properly check the buffer base alignments
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/r600_cs.c | 309 --
drivers/gpu/drm/radeon/r600d.h |6 +
2 files changed, 199 insertions(+), 116 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r600_cs.c b/drivers/gpu/drm/radeon/r600_cs.c
index 37cc2aa..0f90fc3 100644
--- a/drivers/gpu/drm/radeon/r600_cs.c
+++ b/drivers/gpu/drm/radeon/r600_cs.c
@@ -50,6 +50,7 @@ struct r600_cs_track {
u32 nsamples;
u32 cb_color_base_last[8];
struct radeon_bo*cb_color_bo[8];
+ u64 cb_color_bo_mc[8];
u32 cb_color_bo_offset[8];
struct radeon_bo*cb_color_frag_bo[8];
struct radeon_bo*cb_color_tile_bo[8];
@@ -67,6 +68,7 @@ struct r600_cs_track {
u32 db_depth_size;
u32 db_offset;
struct radeon_bo*db_bo;
+ u64 db_bo_mc;
};
static inline int r600_bpe_from_format(u32 *bpe, u32 format)
@@ -140,6 +142,68 @@ static inline int r600_bpe_from_format(u32 *bpe, u32
format)
return 0;
}
+struct array_mode_checker {
+ int array_mode;
+ u32 group_size;
+ u32 nbanks;
+ u32 npipes;
+ u32 nsamples;
+ u32 bpe;
+};
+
+/* returns alignment in pixels for pitch/height/depth and bytes for base */
+static inline int r600_get_array_mode_alignment(struct array_mode_checker
*values,
+ u32 *pitch_align,
+ u32 *height_align,
+ u32 *depth_align,
+ u64 *base_align)
+{
+ u32 tile_width = 8;
+ u32 tile_height = 8;
+ u32 macro_tile_width = values->nbanks;
+ u32 macro_tile_height = values->npipes;
+ u32 tile_bytes = tile_width * tile_height * values->bpe *
values->nsamples;
+ u32 macro_tile_bytes = macro_tile_width * macro_tile_height *
tile_bytes;
+
+ switch (values->array_mode) {
+ case ARRAY_LINEAR_GENERAL:
+ /* technically tile_width/_height for pitch/height */
+ *pitch_align = 1; /* tile_width */
+ *height_align = 1; /* tile_height */
+ *depth_align = 1;
+ *base_align = 1;
+ break;
+ case ARRAY_LINEAR_ALIGNED:
+ *pitch_align = max((u32)64, (u32)(values->group_size /
values->bpe));
+ *height_align = tile_height;
+ *depth_align = 1;
+ *base_align = values->group_size;
+ break;
+ case ARRAY_1D_TILED_THIN1:
+ *pitch_align = max((u32)tile_width,
+ (u32)(values->group_size /
+(tile_height * values->bpe *
values->nsamples)));
+ *height_align = tile_height;
+ *depth_align = 1;
+ *base_align = values->group_size;
+ break;
+ case ARRAY_2D_TILED_THIN1:
+ *pitch_align = max((u32)macro_tile_width,
+ (u32)(((values->group_size / tile_height) /
+(values->bpe * values->nsamples)) *
+ values->nbanks)) * tile_width;
+ *height_align = macro_tile_height * tile_height;
+ *depth_align = 1;
+ *base_align = max(macro_tile_bytes,
+ (*pitch_align) * values->bpe *
(*height_align) * values->nsamples);
+ break;
+ default:
+ return -EINVAL;
+ }
+
+ return 0;
+}
+
static void r600_cs_track_init(struct r600_cs_track *track)
{
int i;
@@ -153,10 +217,12 @@ static void r600_cs_track_init(struct r600_cs_track
*track)
track->cb_color_info[i] = 0;
track->cb_color_bo[i] = NULL;
track->cb_color_bo_offset[i] = 0x;
+ track->cb_color_bo_mc[i] = 0x;
}
track->cb_target_mask = 0x;
track->cb_shader_mask = 0x;
track->db_bo = NULL;
+ track->db_bo_mc = 0x;
/* assume the biggest format and that htile is enabled */
track->db_depth_info = 7 | (1 << 25);
track->db_depth_view = 0xC000;
@@ -168,7 +234,10 @@ static void r600_cs_track_init(struct r600_cs_track *track)
static inline int r600_cs_track_validate_cb(struct radeon_cs_parser *p, int i)
[Bug 31617] Radeon/Compiz: 'failed to attach dri2 front buffer', error case not handled
https://bugs.freedesktop.org/show_bug.cgi?id=31617 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Alex Deucher 2010-11-14 22:37:36 PST --- Thanks. Fix pushed to master: ef0720758e5ba34d0d163bdf5efc6e8dabd65aa8 and 7.9: 9b1ac4d127805f6a14415596e4a557fad3d570a5 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm: radeon: fix error value sign
enable_vblank implementations should use negative result to indicate error.
radeon_enable_vblank() returns EINVAL in this case. Change this to -EINVAL.
Signed-off-by: Vasiliy Kulikov
---
Compile tested.
drivers/gpu/drm/radeon/radeon_irq.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_irq.c
b/drivers/gpu/drm/radeon/radeon_irq.c
index 2f349a3..465746b 100644
--- a/drivers/gpu/drm/radeon/radeon_irq.c
+++ b/drivers/gpu/drm/radeon/radeon_irq.c
@@ -76,7 +76,7 @@ int radeon_enable_vblank(struct drm_device *dev, int crtc)
default:
DRM_ERROR("tried to enable vblank on non-existent crtc
%d\n",
crtc);
- return EINVAL;
+ return -EINVAL;
}
} else {
switch (crtc) {
@@ -89,7 +89,7 @@ int radeon_enable_vblank(struct drm_device *dev, int crtc)
default:
DRM_ERROR("tried to enable vblank on non-existent crtc
%d\n",
crtc);
- return EINVAL;
+ return -EINVAL;
}
}
--
1.7.0.4
