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 CA
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
ha
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 ar
> 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
> drmOpenBy
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 f
