<apw> slangasek, we know that the drm driver can be opened by splash before its 
ready.  we had to add an 'EAGAIN' failure there
<apw> slangasek, we may or may not cope with that in userspace
<apw> commit 6d74feca6235b463ade4ecddd1dfdb73d30a2ff7
<apw> Author: Andy Whitcroft <a...@canonical.com>
<apw> Date:   Thu Jul 29 16:48:21 2010 +0100
<apw>     UBUNTU: SAUCE: drm -- stop early access to drm devices
<apw> slangasek, ^^
<apw> bryceh, its a race, we need to know the minors to tell the load method, 
but till its run we can't actually safely open them
<apw> which is why we have to tell you to hang fire a sec
<apw> though any open can return EAGAIN and you really should damn well listen 
:)
<slangasek> upstart should not open the drm device at all - it's up to whatever 
wants to use it to handle this
<slangasek> (assuming the kernel really can't defer announcing it until it's 
initialized)
<apw> right, we presumably run plymouth or X and its crapping self cause the 
open failed
<bryceh> ok, so then _X_ should block and retry on the device until it gets 
something working?
<slangasek> yes
<apw> that'd be helpful if it could
<bryceh> hum
<apw> as EAGAIN really means, ooops could you try that again please
<apw> bryceh, well it should only do it for open == -1 and errno == EAGAIN

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/982889

Title:
  X trying to start faster than drm driver is ready

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to