loader's SetupProc makes xfree86 assumptions
The current API for SetupProc has the driver calling up to xf86Add{Input,}Driver
by name. We don't really want arbitrary modules to require the xfree86 DDX as a framework.
AFAICT the "options" parameter is always null (except for things loaded from the Modules section a la vnc.so
), so we could possibly abuse that for a new vtable passed by the server into the driver. That's kinda icky.
Alternatively we could teach the loader about a new kind of fooModuleData symbol, preferably pointing to a new versioned structure with less insane API. That seems less bad.
Blocks: #2