On Friday 20th Dec, Dieter Nutzel wrote; > > >What about just implementing it as a patch hosted outside the U.S.? > > >Leave the choice up to the users just like with decss. > > > > Bettr still. A loadable part of Mesa/ drivers. Have a simple default > > module that does nothing/ returns an error if S3TC (de)compression is > > requested. Then someone, out of reach of the patent, can write a version > > of the module that works. A single C file should work, built against the > > DRI/XF86/Mesa headers, and it replaces the default version. If at some > > later date S3/VIA decide we can use it, the infastructure is there. If > > needed for speed, the code could then be builtin instead of a module. > > Add in the hooks for a loadable module, is simply preparing for quick > > implementation when S3/VIA give the go ahead. > > Couldn't this be a "general" API to get missing stuff (e.g. ATI's "Smooth > Vision", "HyperZ" etc.) into the DRI? Something like to get (binary) addon > modules into the tree. > > What do you think?
Why not do what the Freetype project does regarding problems with the native truetype bytecode interpretor due to patents belonging to Apple. Include the code but disable it by default with a warning about distibuting binary enabled versions. At least until such a time as we get a positive response from Via (hopefully this century :-) Free speech, academic interpration or whatever. It would allow individuals to recompile X and play UT2003. PS Sorry for breaking the mail thread, but I'm a digestive biscuit. -- Alan. "One must never be purposelessnessnesslessness."
signature.asc
Description: This is a digitally signed message part
