[Mesa-dev] [Bug 38906] Mesa compilation failure if libudev development files are not installed.

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=38906

--- Comment #9 from Thomas Hellström <thellstrom at vmware.com> 2011-07-03 08:41:05 PDT ---
First, I have nothing at all against GBM, it probably serves its purpose well.

I'm curious, however, to why exactly it is needed for the gallium drm egl
platform code. Correct me if I'm wrong, but it looks to be like the gallium egl
drm code now just uses GBM to call into the gallium GBM state tracker which, in
turn calls the gallium code directly. Something that could well be done from
the gallium drm egl code directly? In addition, the egl state tracker drm
platform code needs to access structures internal to the gallium GBM state
tracker?

Two additional layers of abstraction, that, in addition pulls in a strong
requirement for udev, but as I understand it, it seems to be the loader code
that has this requirement.

And for the pipe driver loader code, it could be useful for other things than
GBM. There are other state trackers that optionally would want to use it (for
example XA). without needing to use the other parts of GBM.

So I think the optimal way to do this is

1) to break out the pipe driver loader, and make it optionally available to any
state tracker.
2) When that's done, (correct me if I'm wrong), there wouldn't be a need for
the egl state tracker drm platform code to take the GBM roundtrips, and perhaps
even to be optionally hard built against a specific gallium driver and drm
device name?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.