Multiple issues with omapdrm

[Dave Airlie]

On Thu, Jun 6, 2013 at 9:25 PM, Rob Clark <robdclark at gmail.com> wrote:
> On Thu, Jun 6, 2013 at 3:\
>>>> Why do you "need" drmOpen("omap")? Is it just a convention to use that
>>>> kind of name, instead of "omapdrm" style name?
>>>
>>> all of the /dev/dri/cardN get opened, and then DRM_IOCTL_VERSION ioctl
>>> to get the driver name/version, which is compared against the name
>>> passed in to drmOpen().  So drmOpen("omapdrm") shouldn't really work
>>
>> Ok, so normally nobody will call drmOpen("omapdrm") explicitly, but
>> somebody (X?) will just do what you described to get the modules loaded?
>> If so, I guess it's unlikely that there would be an app with
>> drmOpen("omapdrm").
>>

These days X shouldn't be loading anything, that is DRI1 left overs.

The kernel/udev should be loading all the drivers well before X starts.

Dave.