[PATCH] Install fbdevhw.so in the correct os-specific path

Vignatti Tiago (Nokia-D/Helsinki) tiago.vignatti at nokia.com
Mon May 31 05:39:30 PDT 2010


On Sun, May 30, 2010 at 11:57:04PM +0200, ext Alan Coopersmith wrote:
> 
> I also don't know any reason not to move it out of the OS-specific libdir and
> up to the generic modules directory, now that all modules there use the OS'es
> actual libc & system calls instead of the libcwrappers.

exactly. 

And, at least using this approach, we'd get rid of all OS directories crap
used by the loader. On the other hand, fbdevhw will keep being in a portable
fashion due its stub version - while in theory shouldn't.

You got my Acked here anyway.

 
> ajax had suggested this solution on IRC as it would be a no-op for Linux
> builders and just fix other OS'es, but we didn't discuss just moving up a
> level instead - which then raises the question of if there's any point having
> the module loader waste time doing all those extra stat() calls during module
> loading to find modules in OS-specific subdirs in a post-libcwrap Xorg.

going more in depth: why we need a loader? Seriously, distros could have all
drivers library linked with the server anyway, which generate trash in the
memory only when using them. So not big deal.

             Tiago


More information about the xorg-devel mailing list