ATI R600g Gains Mip-Map, Face Culling Support

[tball]

I have written an email to the author, kindly asking him to re-release the source-code under a MIT license. It is his libmpeg2 project I want to be MIT licensed:
http://libmpeg2.sourceforge.net

If I can't get it under a MIT, I won't be releasing my current vdpau implementation. I would have to redo too much work writing a bitstream parser from the scratch. My summer vacation is ending soon unfortunately and probably won't have much time spending on the backend.

[adamk]

That's what some BSD people do. They scrounge GPL'd Linux kernel code for 'inspiration' and 'ideas' and then try to obfuscate it by renaming variables and rearranging code. Sometimes they are a little bit careless and this results in blatant copyright infringement.

http://thread.gmane.org/gmane.linux....s.general/1558

Funny, it's also what some Linux people do. They scourge BSD code for inspiration and ideas and then blatantly violate the license by removing the text of the license... Despite the fact that they could have just legally used the code if they had kept the license in place:

http://www.undeadly.org/cgi?action=a...20070829001634

Adam

[marek]

Well what about getting ideas from it then?

First I would kindly ask the original authors if you can get their code under a Mesa-compatible license (MIT/BSD/X11/you name it). That's the simplest thing you can do and the least time consuming in the end. I believe they will be interested in GPU-accelerated video decoding.

[nanonyme]

http://thread.gmane.org/gmane.linux....s.general/1558

That Theo guy sounds bloody scary.

[monraaf]

Well what about getting ideas from it then?

That's what some BSD people do. They scrounge GPL'd Linux kernel code for 'inspiration' and 'ideas' and then try to obfuscate it by renaming variables and rearranging code. Sometimes they are a little bit careless and this results in blatant copyright infringement.

http://thread.gmane.org/gmane.linux....s.general/1558

Really there's a fine line between copying ideas and copying code. A line that can be easily crossed even if you do have good intent. Since it's not uncommon to end up implementing the ideas exactly the same way as the code where you got the ideas from in the first place.

Surely you don't want to go that road, and I don't think Mesa would accept it.

[tball]

Concerning the licensing issues, you can't copy a GPL code and commit it in Mesa.

Well what about getting ideas from it then?

[nanonyme]

http://cgit.freedesktop.org/mesa/demos/
Brian Paul committed the patches. Now there's source from me in mesa. Ego++

Hopefully it'll prevent a bit of confusion for driver developers in the future.

Yeah, now there's no weird white stuff anyway. I still find it a bit confusing that the lower part of the wheel you fixed isn't similar to the upper part of the wheel but guess I can live with it.

[rohcQaH]

http://cgit.freedesktop.org/mesa/demos/
Brian Paul committed the patches. Now there's source from me in mesa. Ego++

Hopefully it'll prevent a bit of confusion for driver developers in the future.

[V!NCENT]

An incorrect test which is supposed to fail but doesn't crash a GPU or Mesa means that Mesa/GPU passes and handles the incorrectness correctly. :P

Concerning the licensing issues, you can't copy a GPL code and commit it in Mesa.

Maybe if he simply states in a friendly e-mail what he likes to do (contribute to Mesa) and just ask if they could perhaps release a tiny segment of that code under the mit lisence to him they will just do it? No is what you have, a yes is what you might get.

[chrisr]

Dare I suggest having two geartrains?

So.. it's a test-case. Fixing everything may make it beautiful, but not necessarily more useful as a test-case. Does this program have a certain purpose to test specific features that must continue to be used?

Fix one geartrain to render beautifully, and keep the other broken one around to test that the driver doesn't crash or lock up when abused?