[2.6 patch] drivers/char/drm/: make some functions static
This patch makes some needlessly global functions static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
This patch was already sent on:
- 19 Jan 2006
drivers/char/drm/i810_dma.c|2 +-
drivers/char/drm/i810_drv.h|2 --
drivers/char/drm/i830_dma.c|2 +-
drivers/char/drm/i830_drv.h|3 ---
drivers/char/drm/savage_bci.c |4 +++-
drivers/char/drm/savage_drv.h |1 -
drivers/char/drm/via_dma.c | 10 +-
drivers/char/drm/via_dmablit.c |2 +-
drivers/char/drm/via_drv.h |7 ---
drivers/char/drm/via_irq.c |2 +-
10 files changed, 12 insertions(+), 23 deletions(-)
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/i810_drv.h.old 2006-01-19
00:15:28.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/i810_drv.h 2006-01-19
00:15:36.0 +0100
@@ -113,8 +113,6 @@
} drm_i810_private_t;
/* i810_dma.c */
-extern void i810_reclaim_buffers(drm_device_t * dev, struct file *filp);
-
extern int i810_driver_dma_quiescent(drm_device_t * dev);
extern void i810_driver_reclaim_buffers_locked(drm_device_t * dev,
struct file *filp);
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/i810_dma.c.old 2006-01-19
00:15:44.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/i810_dma.c 2006-01-19
00:15:49.0 +0100
@@ -958,7 +958,7 @@
}
/* Must be called with the lock held */
-void i810_reclaim_buffers(drm_device_t * dev, struct file *filp)
+static void i810_reclaim_buffers(drm_device_t * dev, struct file *filp)
{
drm_device_dma_t *dma = dev-dma;
int i;
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/i830_drv.h.old 2006-01-19
00:17:38.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/i830_drv.h 2006-01-19
00:17:47.0 +0100
@@ -123,9 +123,6 @@
extern drm_ioctl_desc_t i830_ioctls[];
extern int i830_max_ioctl;
-/* i830_dma.c */
-extern void i830_reclaim_buffers(drm_device_t * dev, struct file *filp);
-
/* i830_irq.c */
extern int i830_irq_emit(struct inode *inode, struct file *filp,
unsigned int cmd, unsigned long arg);
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/i830_dma.c.old 2006-01-19
00:18:33.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/i830_dma.c 2006-01-19
00:18:41.0 +0100
@@ -1239,7 +1239,7 @@
}
/* Must be called with the lock held */
-void i830_reclaim_buffers(drm_device_t * dev, struct file *filp)
+static void i830_reclaim_buffers(drm_device_t * dev, struct file *filp)
{
drm_device_dma_t *dma = dev-dma;
int i;
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/savage_drv.h.old 2006-01-19
00:19:48.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/savage_drv.h 2006-01-19
00:19:55.0 +0100
@@ -212,7 +212,6 @@
extern int savage_driver_firstopen(drm_device_t *dev);
extern void savage_driver_lastclose(drm_device_t *dev);
extern int savage_driver_unload(drm_device_t *dev);
-extern int savage_do_cleanup_bci(drm_device_t * dev);
extern void savage_reclaim_buffers(drm_device_t * dev, DRMFILE filp);
/* state functions */
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/savage_bci.c.old 2006-01-19
00:20:02.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/savage_bci.c 2006-01-19
00:20:24.0 +0100
@@ -32,6 +32,8 @@
#define SAVAGE_EVENT_USEC_TIMEOUT 500 /* 5s */
#define SAVAGE_FREELIST_DEBUG 0
+static int savage_do_cleanup_bci(drm_device_t * dev);
+
static int
savage_bci_wait_fifo_shadow(drm_savage_private_t * dev_priv, unsigned int n)
{
@@ -895,7 +897,7 @@
return 0;
}
-int savage_do_cleanup_bci(drm_device_t * dev)
+static int savage_do_cleanup_bci(drm_device_t * dev)
{
drm_savage_private_t *dev_priv = dev-dev_private;
--- linux-2.6.16-rc1-mm1-full/drivers/char/drm/via_drv.h.old2006-01-19
00:21:25.0 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/char/drm/via_drv.h2006-01-19
01:07:36.0 +0100
@@ -110,11 +110,6 @@
extern int via_agp_init(DRM_IOCTL_ARGS);
extern int via_map_init(DRM_IOCTL_ARGS);
extern int via_decoder_futex(DRM_IOCTL_ARGS);
-extern int via_dma_init(DRM_IOCTL_ARGS);
-extern int via_cmdbuffer(DRM_IOCTL_ARGS);
-extern int via_flush_ioctl(DRM_IOCTL_ARGS);
-extern int via_pci_cmdbuffer(DRM_IOCTL_ARGS);
-extern int via_cmdbuf_size(DRM_IOCTL_ARGS);
extern int via_wait_irq(DRM_IOCTL_ARGS);
extern int via_dma_blit_sync( DRM_IOCTL_ARGS );
extern int via_dma_blit( DRM_IOCTL_ARGS );
@@ -139,8 +134,6 @@
extern void via_init_futex(drm_via_private_t * dev_priv);
extern void via_cleanup_futex(drm_via_private_t * dev_priv);
extern void via_release_futex(drm_via_private_t * dev_priv, int context);
-extern int via_driver_irq_wait(drm_device_t * dev, unsigned int irq,
- int force_sequence, unsigned int *sequence);
extern void
Current DRM on FreeBSD
Just thought I'd point out that DRM has stopped compiling on FreeBSD again: === radeon (all) Warning: Object directory not changed from original /home/adamk/saved/source/drm/bsd-core/radeon cc -O2 -fno-strict-aliasing -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I.. -I. -I@ -I@/contrib/altq -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c: In function `radeon_cp_cmdbuf': /home/adamk/saved/source/drm/bsd-core/radeon/../radeon_state.c:2750: error: incompatible types in assignment *** Error code 1 Stop in /home/adamk/saved/source/drm/bsd-core/radeon. *** Error code 1 DRI, from Mesa CVS, still builds, but falls back to indirect rendering since it needs DRM 1.22.x to run. Isn't it possible to only make newer functionality in the DRI drivers depend on newer DRM? This way, users stuck with a particular version of the DRM still have functional DRI drivers, even if they are missing out on newer features of the driver? Adam --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
DRM Translation Table Map interface
Hi, I've checked in the first shot at a Translation Table Map TTM interface in drm-ttm-branch. The interface is intended to be a low-level support structure for an AGP memory manager. A ttm is conceptually a shared memory map, part of which can be bound to a translation table, typically the GTT. They are created with a fixed size, but pages aren't actually allocated until they are used by the user's virtual mapping or bound into the TT. Either the whole map or multiple parts of it can be bound. There can be different kinds of translation tables so a backend object is needed. This object holds private data and a set of functions to manipulate the translation tables. Currently there is an implementation of an AGP backend in drm_agpsupport.c, and each driver has a function pointer to the function creating a backend object. In that way device independent caching policies, translation table types and multiple apertures are handled. The backend _may_ tell the TTM interface that pages should be mapped uncached while bound. In that case, before pages are bound into the TT, they are unmapped from all VMAs referencing them, and then the kernel virtual mapping is adjusted to be non-cached. When the user references a page through a VMA, it is re-mapped also to user-space with the new caching policy. When unbound the old caching policy is restored in the same way. There are devices that can map cached pages into GTT and for those, the above operation is not done. In this way we always ensure consistent mappings. When the file used to create a TTM is closed, the TTM it is removed unless the user had done it already. To speed up map (both TTM and ordinary map) lookups in the vm part of drm, a hashing approach is used instead of the old linked-list lookup. This means that quite arbitrary page-aligned 32-bit user-tokens are generated for maps, so drivers assuming that the handle returned by drmAddMap is actually the physical address will fail. I'm not sure that there are such drivers left except the via DDX? Should we handle this at the DRM level? The hash tables are closed (for speed) and they fail when full. However, this protects against an arbitrary number of maps or bound regions. The tables hold (void *) pointers but a good policy is to have a hash table holding pointers to one object type only. In that way one knows that a populated hash table entry always points to a valid object of a certain type, and fields within that object may always be accessed. The concept requires minimal changes to the AGP drivers. An example for the intel-agp driver is posted on bugzilla bug #5709, and there is a user-space test program in test/ttmtest. Comments on this would be appreciated. Particularly on the anonymous map handle approach. /Thomas. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
status
I'm thinking of trying the radeon driver again, but i'm wondering wether or not it will ever catch up with the fglrx driver on speed? what's the status of this, or goal? and what's the status on 9800 pro dual monitor support with 3d? thanks for all your hard work anyway. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5710] DRI libs relocation problems on hardened systems
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5710 --- Additional Comments From [EMAIL PROTECTED] 2006-01-25 22:10 --- That error should be: Cannot make segment writable for relocation. Permission denied I have this refined somewhat. Reading the readme in the et_dyn.tar.gz file referenced in the kernel help (under CONFIG_PAX_NOELFRELOCS) indicates that it is the -pie option in gcc which is causing trouble. This position independent feature is nobbled by any text relocations, which, apparently fix a position. Inserting '-no-pie' where I thought it would help (in the many GL directories) got me a version of libGL.so.1.2 with no TEXTRELs. I have not to date got a version of any of the following without text relocations. glxinfo glsgears xdriinfo radeon_drv.so Compiler options are tricky on hardened systems, as the compiler throws a set of hardening options by default, some of which can be overridden by command line stuff On Xorg-6.9.0, this turns out to be an X problem and may advantageously be labelled as such by someone handling it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5721] New: doom3 segfaults sometimes in the _tnl_DrawElements code
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5721 Summary: doom3 segfaults sometimes in the _tnl_DrawElements code Product: Mesa Version: CVS Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Drivers/DRI/r200 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] Even with tcl_mode=0 (on the radeon 9000pro) doom3 sometimes segfaults. It's kinda hard to trigger, but it seems to happen always around the same places (one place is at the end of the game, just some moments before approaching the cyberdemon - just walking by there has a chance of around 20% to crash). There are also some obvious rendering errors there (looks like misspecified polyons or something like that, though it could just be z-fighting issues) which may be related. Program received signal SIGSEGV, Segmentation fault #0 0x3c44e509 in loopback_Color4ubv_f ( v=0x11e57638 Address 0x11e57638 out of bounds) at main/api_loopback.c:280 #1 0x3c37a158 in _ae_loopback_array_elt (elt=1290) at main/api_arrayelt.c:788 #2 0x3c47768f in fallback_drawelements (ctx=Variable ctx is not available. ) at tnl/t_array_api.c:75 #3 0x3c477c25 in _tnl_DrawElements (mode=4, count=306, type=5125, indices=0x666) at tnl/t_array_api.c:375 #4 0x08156450 in ?? () (Now, with indices 666 it must just go wrong :-). Though mode and type always seem to be the same.) I'd suspect it's not a r200 driver specific problem, but I'd need days until I would hit a crash with the software renderer... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5710] DRI libs relocation problems on hardened systems
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5710 --- Additional Comments From [EMAIL PROTECTED] 2006-01-26 03:38 --- The full list of problem programs libs are all linked against libGL.so.1, which (I must correct myself) contains a Textrel. http://www.linuxfromscratch.org/hlfs/view/unstable/glibc/chapter02/pie.html /wallows out of his depth, then gradually sinks. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5710] DRI libs relocation problems on hardened systems
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5710 --- Additional Comments From [EMAIL PROTECTED] 2006-01-26 03:50 --- See bug 4197. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5721] doom3 segfaults sometimes in the _tnl_DrawElements code
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5721 --- Additional Comments From [EMAIL PROTECTED] 2006-01-26 03:54 --- Is it possible to record a demo at the place where the SEGFAULT is hit? If there's only a 20% hitting it (that isn't dependent on exact view parameters), looping the demo 5 times should be able to consistently reproduce it. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5710] DRI libs relocation problems on hardened systems
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5710 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2006-01-26 04:12 --- This is a duplicate of 4197, it appears. Thanks for that. From reading the vitriol on bug 4197, the patch attached carries a performance penalty and a mixed blessing, but works. I'll shoehorn it in and try it. *** This bug has been marked as a duplicate of 4197 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: status
On Wed, 25 Jan 2006 11:51:17 +0100 Kristoffer [EMAIL PROTECTED] wrote: I'm thinking of trying the radeon driver again, but i'm wondering wether or not it will ever catch up with the fglrx driver on speed? what's the status of this, or goal? and what's the status on 9800 pro dual monitor support with 3d? thanks for all your hard work anyway. my guess is that you're going to get either silence from the list, or a answer to your own question by doing benchmarks-type response. the only thing I can say is that fglrx is better than dri on some aspects of GL, unfortunatly this is what is used in UT2K3 / UT2K4 for example. there are plans to fix this, as time allows. khaqq --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 5721] doom3 segfaults sometimes in the _tnl_DrawElements code
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5721 --- Additional Comments From [EMAIL PROTECTED] 2006-01-26 06:43 --- (In reply to comment #1) Is it possible to record a demo at the place where the SEGFAULT is hit? If there's only a 20% hitting it (that isn't dependent on exact view parameters), looping the demo 5 times should be able to consistently reproduce it. This is a good idea. I've recorded a short, yet 6MB, demo, http://homepage.hispeed.ch/rscheidegger/segfault.demo. However, I'm not sure anymore this is easily reproducible, it seems very highly moon-phase dependant. For instance, if it succeeds once, it will always succeed in subsequent runs, it looks like you need to restart doom3 or at least run a different demo (like demo1). You can try your luck :-). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Current DRM on FreeBSD
DRI, from Mesa CVS, still builds, but falls back to indirect rendering since it needs DRM 1.22.x to run. Isn't it possible to only make newer functionality in the DRI drivers depend on newer DRM? This way, users stuck with a particular version of the DRM still have functional DRI drivers, even if they are missing out on newer features of the driver? For any other driver than r300 this is done, I don't want to do this for r300 as it is an experimental driver, and having a lot of backwarrds compat in the Mesa driver during development is only going to make it look uglier for no real gain.. I guess it was my kcmdbuf changes that broke radeon on FreeBSD, they shouldn't be that hard to fixup.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
i915-Graphics Driver for Xorg-7.0
Hello, I hope I've got the right mail-adress, I have a question at the i915 (GMA900) developer of the i810 driver?! As far as I know nearly everyone with an i915GM-Chipset (GMA900) has a problem with a BusID-Error, everything seems to work good but something must be not working in the right way. Just see below (don't care about the xkbcomp-message): System is Gentoo-Linux based. Thanks Peter Weber PS: If you want addional information, just mail me. X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.14.2 i686 Current Operating System: Linux party 2.6.14.2 #8 Fri Dec 30 16:01:26 CET 2005 i686 Build Date: 24 December 2005 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Dec 30 19:00:00 2005 (==) Using config file: /etc/X11/xorg.conf (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found Warning!? expected keysym, got dead_diaresis: line 143 of pc/de The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: i915-Graphics Driver for Xorg-7.0
It's not a problem. Don't worry about it. Alan. On Wed, 2006-01-25 at 21:56 +0100, Peter Weber wrote: Hello, I hope I've got the right mail-adress, I have a question at the i915 (GMA900) developer of the i810 driver?! As far as I know nearly everyone with an i915GM-Chipset (GMA900) has a problem with a BusID-Error, everything seems to work good but something must be not working in the right way. Just see below (don't care about the xkbcomp-message): System is Gentoo-Linux based. Thanks Peter Weber PS: If you want addional information, just mail me. X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.14.2 i686 Current Operating System: Linux party 2.6.14.2 #8 Fri Dec 30 16:01:26 CET 2005 i686 Build Date: 24 December 2005 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Dec 30 19:00:00 2005 (==) Using config file: /etc/X11/xorg.conf (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found Warning!? expected keysym, got dead_diaresis: line 143 of pc/de The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: status
On Wed, 25 Jan 2006 20:29:05 +0100 khaqq [EMAIL PROTECTED] wrote: On Wed, 25 Jan 2006 11:51:17 +0100 Kristoffer [EMAIL PROTECTED] wrote: I'm thinking of trying the radeon driver again, but i'm wondering wether or not it will ever catch up with the fglrx driver on speed? what's the status of this, or goal? and what's the status on 9800 pro dual monitor support with 3d? thanks for all your hard work anyway. my guess is that you're going to get either silence from the list, or a answer to your own question by doing benchmarks-type response. the only thing I can say is that fglrx is better than dri on some aspects of GL, unfortunatly this is what is used in UT2K3 / UT2K4 for example. there are plans to fix this, as time allows. The ut2k4 problem(s) have been in a semi-fixed state for a while now. Bits and bolts dealing with it arent just enabled by default because quite a few changes are needed to get it fully transparent. Couple shots: http://www.rasterburn.org/~aet/ut2k4_tweaked.png http://www.rasterburn.org/~aet/ut2k4_vanilla.png -- Aapo Tahkola --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: status
On Wednesday 25 January 2006 19:01, Aapo Tahkola wrote: On Wed, 25 Jan 2006 20:29:05 +0100 khaqq [EMAIL PROTECTED] wrote: On Wed, 25 Jan 2006 11:51:17 +0100 Kristoffer [EMAIL PROTECTED] wrote: I'm thinking of trying the radeon driver again, but i'm wondering wether or not it will ever catch up with the fglrx driver on speed? what's the status of this, or goal? and what's the status on 9800 pro dual monitor support with 3d? thanks for all your hard work anyway. my guess is that you're going to get either silence from the list, or a answer to your own question by doing benchmarks-type response. the only thing I can say is that fglrx is better than dri on some aspects of GL, unfortunatly this is what is used in UT2K3 / UT2K4 for example. there are plans to fix this, as time allows. The ut2k4 problem(s) have been in a semi-fixed state for a while now. Bits and bolts dealing with it arent just enabled by default because quite a few changes are needed to get it fully transparent. Couple shots: http://www.rasterburn.org/~aet/ut2k4_tweaked.png http://www.rasterburn.org/~aet/ut2k4_vanilla.png Do these fixes remove the need to disable s3tc to avoid the flickering tiling problem? And just a general warning to the original writer of the original question about the r300 driver on 9800 hardware: there are problems with pretty regular lockups. Other r300 hardware (X700, X800, for example) don't seem to have this issue, though. Adam --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: status
On Wed, 25 Jan 2006 17:28:17 -0500 Adam K Kirchhoff [EMAIL PROTECTED] wrote: On Wednesday 25 January 2006 19:01, Aapo Tahkola wrote: On Wed, 25 Jan 2006 20:29:05 +0100 khaqq [EMAIL PROTECTED] wrote: On Wed, 25 Jan 2006 11:51:17 +0100 Kristoffer [EMAIL PROTECTED] wrote: I'm thinking of trying the radeon driver again, but i'm wondering wether or not it will ever catch up with the fglrx driver on speed? what's the status of this, or goal? and what's the status on 9800 pro dual monitor support with 3d? thanks for all your hard work anyway. my guess is that you're going to get either silence from the list, or a answer to your own question by doing benchmarks-type response. the only thing I can say is that fglrx is better than dri on some aspects of GL, unfortunatly this is what is used in UT2K3 / UT2K4 for example. there are plans to fix this, as time allows. The ut2k4 problem(s) have been in a semi-fixed state for a while now. Bits and bolts dealing with it arent just enabled by default because quite a few changes are needed to get it fully transparent. Couple shots: http://www.rasterburn.org/~aet/ut2k4_tweaked.png http://www.rasterburn.org/~aet/ut2k4_vanilla.png Do these fixes remove the need to disable s3tc to avoid the flickering tiling problem? These changes are already in cvs with exception of fb vbos(pretty useless anyways) and the drm scratch patch. s3tc problem is still there im afraid. Im using patches off #5353 to get around the texture swapping problem... -- Aapo Tahkola --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] new radeon memory map fixes
Ok, so finally here is a new version of the patch. This time, it's against modular and it comes with a DRM patch. The X driver and the DRM patch should both work with the unpatched counterpart though you'll only get the full benefit of the fixes with both patches applied. As I had to shuffle a lot of code around in the X driver, there may still be bugs lurking around. Especially look for regressions around Xinerama and MergedFB as I haven't yet had a chance to test with those (especially Xinerama is doing a lot of very dodgy stuffs in the radeon driver). Please, try to test all sort of combinations of color tiling on/off, dri enabled/disabled, bit depth, hw/sw cursor etc... Patches are available at: Xorg driver patch: http://gate.crashing.org/~benh/radeon-memmap-7.0-2.diff DRM patch: http://gate.crashing.org/~benh/radeon-memmap-drm-1.diff Please, report any problem, thanks, Ben. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Marbleblast + r300
Marbleblast, a game from GarageGames, seems to have an issue with the r300 driver... The game crashes when it goes to start a new level. It crashes with: drmRadeonCmdBuffer: -22 (exiting) drmRadeonCmdBuffer: -22 (exiting) dmesg shows: [drm:r300_emit_carefully_checked_packet0] *ERROR* Offset failed range check (reg=4540 sz=3) [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet0 failed If anyone is interested, there is a demo available: http://www.garagegames.com/demos/browse/game/ Orbz, another game from them, seems to work fine. ** Adam --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] new radeon memory map fixes
Benjamin Herrenschmidt wrote: Ok, so finally here is a new version of the patch. This time, it's against modular and it comes with a DRM patch. The X driver and the DRM patch should both work with the unpatched counterpart though you'll only get the full benefit of the fixes with both patches applied. As I had to shuffle a lot of code around in the X driver, there may still be bugs lurking around. Especially look for regressions around Xinerama and MergedFB as I haven't yet had a chance to test with those (especially Xinerama is doing a lot of very dodgy stuffs in the radeon driver). Please, try to test all sort of combinations of color tiling on/off, dri enabled/disabled, bit depth, hw/sw cursor etc... Not tested yet, but I see you now no longer set the HDP_APER_CNTL which didn't work for me at all. However, does that mean some cards which map their memory as for instance 2x64MB have to live with 64MB because of that? Do you have any information why this setting doesn't work for some cards? Roland --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] new radeon memory map fixes
On Thu, 2006-01-26 at 01:42 +0100, Roland Scheidegger wrote: Not tested yet, but I see you now no longer set the HDP_APER_CNTL which didn't work for me at all. However, does that mean some cards which map their memory as for instance 2x64MB have to live with 64MB because of that? Do you have any information why this setting doesn't work for some cards? Unless I screwed up, I keep the original code from Hui that sets it on some cards (r300 typically). My previous patch set it on all cards but that caused some cards (including an rv250 I have here) to completely stop responding on PCI accesses to the aperture :( Note also that I don't clear it neither ... Thus if the firmware sets it, it will work. I do read the bit to decide wether to expose half or not of memory in those cases. I'm still waiting for somebody from ATI to reply to my request asking for more infos about what's going on with that bit ... Ben --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] new radeon memory map fixes (if you segfault)
On Thu, 2006-01-26 at 10:43 +1100, Benjamin Herrenschmidt wrote: Ok, so finally here is a new version of the patch. This time, it's against modular and it comes with a DRM patch. The X driver and the DRM patch should both work with the unpatched counterpart though you'll only get the full benefit of the fixes with both patches applied. As I had to shuffle a lot of code around in the X driver, there may still be bugs lurking around. Especially look for regressions around Xinerama and MergedFB as I haven't yet had a chance to test with those (especially Xinerama is doing a lot of very dodgy stuffs in the radeon driver). Please, try to test all sort of combinations of color tiling on/off, dri enabled/disabled, bit depth, hw/sw cursor etc... BTW. If you get segfaults with the patch, please look into rebuilding your server with http://cvs.freedesktop.org/xorg/xserver/xorg/include/xorg-config.h.in?r1=1.12r2=1.13 To enable backtrace support, it was broken in stock 7.0 Ben. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
