On Thu, Aug 05, 2004 at 04:19:55PM -0700, Ian Romanick wrote:
> >module and the card dependant one.. I can see people building their own
> >card drivers from the DRM CVS and trying to load them vs a kernel with a
> >built-in DRM core.. my current thinking on this is we use the Kconfig to
> >try and ban it (I hope it is flexible enough)... so if a kernel has a
> >built-in drm library CVS won't build against it, and we won't build DRM
> >modules unless the library is a module ..
I think thats the way to go. Try and get things in the mainline kernel
quick enough, or maybe even do the work there (Its the reason we
have things like CONFIG_EXPERIMENTAL). If you reduce the incentive for
folks to grab bits from another source, this problem goes away.
> I guess one (unpleasant) way to make it work would be to add the version
> to all the symbols in the device-independent layer. Instead of drm_foo
> you'd have drm_foo_100 or drm_foo_101 or whatever. You could then have
> multiple modules loaded or a module loaded with a built-in version. I'm
> not sure how happy that would make the kernel maintainers (not to
> mention how happy it would make us). :( It's basically like what we
> have now, except the current code has the device's name add to all the
> symbols and is built into the device-dependent module. Ugh, ugh.
"Ugh" is putting things very politely 8-)
Whilst I realise we don't live in a perfect world, and getting interfaces
right first time is hard, I'd really like to warn about the horrors
of versioned ioctl's and the like.
> How do other multi-layer kernel modules handle this? For example, how
> does agpgart or iptables do it?
For agpgart it hasn't really been an issue as all the development there
in the last year or two has been done in tree. Yes, there has been some
work on things like i915 out-of-tree, but that stuff has been merged up
pretty quickly.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
