policy on GPL'd drivers?

[dave]

>
> I don't think anyone is talking about symbol versioning. The issue is
> stamping the API at a particular point in time that shows it behaves in
> a specified guaranteed way.
>
> The module system has all the hooks to deal with versioning. What's
> missing is not the mechanism but the knowledge, i.e. we don't know that
> module X won't work with kernel Y becuase we don't know what APIs 
> module
> X may invoke and whether kernel Y supports them.
>

<snip>

> The only true solution to this is to version the APIs in the kernel and
> use the module versioning hooks to not load modules if the version 
> isn't
> the right one.

Will this require *any* new infrastructure to implement properly?  Or is
it simply a matter of maintaining API metadata regarding versions.

I should probably try to understand the existing stuff more before 
asking
too many more questions.

>
> -- 
> Tis a wise thing to know what is wanted, wiser still to know when
> it has been achieved and wisest of all to know when it is unachievable
> for then striving is folly. [Magician]
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"
>