Re: compatibility problem with drm-core.
Hi! Jon Smirl wrote: I think this is happening for Thomas because he is running an older X server that isn't negotiating to the most current DRM interface. I believe the attached patch will fix the problem but we all need to test it to make sure it doesn't have unintended side effects. I don' t have an old X server around anymore to test for his exact problem. The patch you sent fixes the problem. /Thomas --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: compatibility problem with drm-core.
On Thu, 18 Nov 2004 22:13:23 +0100, Thomas Hellström [EMAIL PROTECTED] wrote: The patch you sent fixes the problem. I'm in the middle of moving to a new house so I will be off-line for at least a few more days. I don't have internet access at the new house yet, something is messed up in the CAT5 wiring. Maybe Dave can take care of this or you will need to wait for me to get moved in. -- Jon Smirl [EMAIL PROTECTED] --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: compatibility problem with drm-core.
I think this is happening for Thomas because he is running an older X server that isn't negotiating to the most current DRM interface. I believe the attached patch will fix the problem but we all need to test it to make sure it doesn't have unintended side effects. I don' t have an old X server around anymore to test for his exact problem. -- Jon Smirl [EMAIL PROTECTED] patch Description: Binary data
compatibility problem with drm-core.
Hi! I've come across a problem with drm-core. When a drm device is opened by the X server, it opens the first drm device that does not have a busid assigned to it, since that means it is busy. It then assigns a busid to that device. Now, if the server is exited and restarted, the server cannot find a an available device with no bus-id assigned to it and falls back to the old /proc interface: drmOpenByBusid: busid is PCI:1:0:0 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports PCI:1:0:0 (II) VIA(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Device or resource busy (EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI. /Thomas --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
