Re: is there a fork between drm from DRI and drm from kernel.org?
It's better to just build the required kernel modules. Rebuilding the Linux kernel as a whole is unnecessary, even undesirable. - Make sure that you have configured kernel sources installed. - Checkout DRI. - Goto "drm/linux-core". - Type "make "DRM_MODULES="drm.ko ati.ko"" or equivalent according to your chipset. The "LINUXDIR=" option allows to specify a custom kernel source path if necessary. - Make sure to load the resulting kernel modules at an early moment of the system boot-up. I'm used to loading the modules via "insmod" in "/etc/rc.d/rc.sysinit". This even works when the kernel module is already present but you want to use a newer version. That's all and works as expected. -Joachim --- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: is there a fork between drm from DRI and drm from kernel.org?
Strictly speaking, the kernel sources are not required themselves. Just make sure you have the "kernel-devel" package of your distro installed which provides the necessary header and config files. --- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
FreeBSD & DRM
So at some point in the not too distant past, I managed to get current Mesa/DRI CVS working on my FreeBSD workstation (with an X700Pro). Just earlier today, though, I did a "make buildworld" and "make installworld" and suddenly Direct Rendering is not working any more. It turns out that -CURRENT on FreeBSD only has DRM version 1.19.0 but the version of Mesa/DRI I have installed requires version 1.20.0. Since I managed to get 1.20 installed before, I figured I could get it working again. Except that I can't. I pulled DRM from CVS, changed to the bsd-core directory, and did a make. It died with: /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c: In function `drm_device_find_capability': /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: error: `AGP_CAPPTR' undeclared (first use in this function) /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: error: (Each undeclared identifier is reported only once /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: error: for each function it appears in.) /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:66: warning: implicit declaration of function `AGP_CAPID_GET_NEXT_PTR' /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:66: warning: nested extern declaration of `AGP_CAPID_GET_NEXT_PTR' /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:71: warning: implicit declaration of function `AGP_CAPID_GET_CAP_ID' /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:71: warning: nested extern declaration of `AGP_CAPID_GET_CAP_ID' /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:45: warning: unused variable `ret' I started jumping back one month at a time, starting on December 2nd, going back to June 2nd. From June 2nd, this is what I get when I try make: /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c: In function `drm_device_is_agp': /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:50: error: structure has no member named `driver' /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:51: error: structure has no member named `driver' /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: `AGP_CAPPTR' undeclared (first use in this function) /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: (Each undeclared identifier is reported only once /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: for each function it appears in.) /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:72: warning: implicit declaration of function `AGP_CAPID_GET_NEXT_PTR' /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:72: warning: nested extern declaration of `AGP_CAPID_GET_NEXT_PTR' /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:77: warning: implicit declaration of function `AGP_CAPID_GET_CAP_ID' /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:77: warning: nested extern declaration of `AGP_CAPID_GET_CAP_ID' *** Error code 1 Different functions, but essentially the same errors. Yet I know that somehow I did manage to get 1.20.0 installed on this machine because I had it working before :-( Any ideas what I'm doing wrong? Thanks! 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: FreeBSD & DRM
On Mon, 2005-12-26 at 15:49 -0500, Adam K Kirchhoff wrote: > So at some point in the not too distant past, I managed to get current > Mesa/DRI CVS working on my FreeBSD workstation (with an X700Pro). Just > earlier today, though, I did a "make buildworld" and "make installworld" > and suddenly Direct Rendering is not working any more. It turns out > that -CURRENT on FreeBSD only has DRM version 1.19.0 but the version of > Mesa/DRI I have installed requires version 1.20.0. Since I managed to > get 1.20 installed before, I figured I could get it working again. > Except that I can't. I pulled DRM from CVS, changed to the bsd-core > directory, and did a make. It died with: > > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c: > In function `drm_device_find_capability': > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: > error: `AGP_CAPPTR' undeclared (first use in this function) > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: > error: (Each undeclared identifier is reported only once > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:62: > error: for each function it appears in.) > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:66: > warning: implicit declaration of function `AGP_CAPID_GET_NEXT_PTR' > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:66: > warning: nested extern declaration of `AGP_CAPID_GET_NEXT_PTR' > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:71: > warning: implicit declaration of function `AGP_CAPID_GET_CAP_ID' > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:71: > warning: nested extern declaration of `AGP_CAPID_GET_CAP_ID' > /home/adamk/saved/source/drm.current/bsd-core/drm/../drm_agpsupport.c:45: > warning: unused variable `ret' > > I started jumping back one month at a time, starting on December 2nd, > going back to June 2nd. From June 2nd, this is what I get when I try make: > > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c: In > function `drm_device_is_agp': > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:50: error: > structure has no member named `driver' > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:51: error: > structure has no member named `driver' > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: > `AGP_CAPPTR' undeclared (first use in this function) > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: > (Each undeclared identifier is reported only once > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:68: error: > for each function it appears in.) > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:72: > warning: implicit declaration of function `AGP_CAPID_GET_NEXT_PTR' > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:72: > warning: nested extern declaration of `AGP_CAPID_GET_NEXT_PTR' > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:77: > warning: implicit declaration of function `AGP_CAPID_GET_CAP_ID' > /home/adamk/saved/source/drm/bsd-core/drm/../drm_agpsupport.c:77: > warning: nested extern declaration of `AGP_CAPID_GET_CAP_ID' > *** Error code 1 > > Different functions, but essentially the same errors. > > Yet I know that somehow I did manage to get 1.20.0 installed on this > machine because I had it working before :-( > > Any ideas what I'm doing wrong? Thanks! Nothing. I need to commit jhb's DRM patch from the vga master device changes. -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
[Bug 5104] Xorg 6.8.2 freeze computer when dri is enabled for a Radeon 7000
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=5104 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2005-12-27 09:59 --- I see approximately the same with ATI Radeon 9500 AD (AGP) card on Linux, x86_64 hardware, and 6.99.99.904 (7.0.0 RC 4) server. A machine is not precisely frozen as a remote login is still possible but a local console presents a blank screen, a dead keyboard and X server is _really_ busy taking around 99% of CPU. If one would believe only in logs then everything is just great - ... (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [DRI] installation complete (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 217 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 (II) RADEON(0): Direct rendering enabled ... only not much works. Turning off dri provides a working X server using 'radeon' driver but a rather slow one. Also when dri is turned on I see in logs a bunch of messages like that: No matching visual for __GLcontextMode with visual class = 1 (32774), nplanes = 32 With dri turned off they are replaces with: No matching visual for __GLcontextMode with visual class = 1 (32774), nplanes = 4294967295 The last number is 0x, which probably was meant to be -1, only on a 64-bit machine is not. Only a bad format on a printout or something more? -- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: is there a fork between drm from DRI and drm from kernel.org?
> Sorry for the question, but browsing the mailing list did not give any > answer, other then that you need to build drm WITH current Linux kernel, > but why is it not in THE current Linux kernel? There is a delay between patches going into the CVS tree and the kernel, usually because of the kernel merge cycles, most of the latest CVS should be in my git tree .. and that is what I'll merge to Linus when he next opens up for merges, I can't submit major patches to the kernel outside of the merge cycles... > with that kind of chipset and I can do the merge, but I don't know what > to merge into what. The mach64 DRM is insecure, it needs securing before it can be included in the kernel... > I saw that those trees are forked, my interest was in mga and mach64 > chip families. MGA in the kernel is dated > > DRIVER_DATE "20050607" > > whereas DRI version is > > DRIVER_DATE "20051102" > > But, kernel version is not a superset of DRI version. Function name > changes, and even interface changes (i.e. parameters for functions). The kernel also has no support for DRM drivers acting as full PCI drivers, the CVS tree still has this, at some point I'll start fixing up the kernel to support fb and drm devices on the same PCI device... > I wanted to get myself linux kernel updated to latest DRI code, but I > don't know what to do to be generally productive, i.e. so those patchese > may be merged into kernel tree. > > I figured that Dave Airlie is managing the kernel.org version of > drivers/char/drm, but who is in charge of drm/shared-core > /drm/linux-core? > Usually myself and Eric Anholt are the main hackers, but everyone in the DRI/X.org team have DRM commit access.. myself and Eric push them to Linux/FreeBSD projects.. 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Status of Xpress chips support
Alex Deucher wrote: On 12/24/05, Dave Jones <[EMAIL PROTECTED]> wrote: On Fri, Dec 23, 2005 at 11:20:34PM +, Dave Airlie wrote: > > > Anyhow, I was wanting to volunteer my services and my Radeon Xpress 200M for development work on this project. I have some kernel hacking/driver development experience, but that was on a device with open specifications, so I wanted to ask the following questions: > > 1) What do we currently know about these chipsets? > > They have no on-board RAM and are PCI Express I'm not entirely sure that's correct. Santa brought me a laptop which gives me the option of using the onboard video ram, system ram, or even both. I've not had chance to play with it much yet though. Some of the new XPRESS chips have mixed on-board/system configurations. There are supposedly desktop versions with mixed ram types as well. on the xpress chips, it's called sideport. It can apparently do local/system ram accesses interleaved, though I've no idea how it works (maybe per-tile access, half the tiles local half not?). The other possible modes (i.e. uma only, sideport mem only, or sideport + uma but not interleaved) look simpler. On the desktop chips (at least for the "old" 3-letter Xxyz chips) it's called hypermemory. As far as I can tell though those chips can't do interleaved accesses, and I don't think there's anything different to the non-hypermemory cards whatsoever (except they have less ram on a half-as wide bus). At least all r300 based chips should be able to render to system memory directly already. 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
