GPL RTG driver information available

[kamelito]

@Heiroglyph

Are you following CBM RTG specifications as seen in the Amiga Developers Conference of Orlando from 1993? And others info like FutureProductOptions_dist.pdf

Kamelito

[Heiroglyph]

I've cancelled this project now, too many legal questions.

I've move to another project which uses the Aros RTG which is similar to CGX. So no, I'm not unless they did.

[wawrzon]

i think we may have to wait a little. there was a hefty discussion on a1k, which result may be that the community will be offered to open source p96 for a certain price, even if i consider this unlikely anymore. if p96 will be handed over to another party or company it might really occur necessary. especially for the rtg solution vendors to reach for some oprn solution themselves, which most conveniently could be based on aros as it seems.

[Heiroglyph]

i think we may have to wait a little. there was a hefty discussion on a1k, which result may be that the community will be offered to open source p96 for a certain price, even if i consider this unlikely anymore. if p96 will be handed over to another party or company it might really occur necessary. especially for the rtg solution vendors to reach for some oprn solution themselves, which most conveniently could be based on aros as it seems.

As long as we get something figured out, I'm fine with it.

Hopefully it's open source so that when the money runs out we aren't stuck again.

[polyp2000]

I've cancelled this project now, too many legal questions.

I've move to another project which uses the Aros RTG which is similar to CGX. So no, I'm not unless they did.

Well done to all involved in this decision.

[grond]

there was a hefty discussion on a1k, which result may be that the community will be offered to open source p96 for a certain price

As you, I wouldn't put my hopes on it and certainly not stop a project because of it. Right now there is some momentum which should be used before it's lost.

[polyp2000]

As you, I wouldn't put my hopes on it and certainly not stop a project because of it. Right now there is some momentum which should be used before it's lost.

Has anyone considered a white room implementation ?

N

[wawrzon]

Has anyone considered a white room implementation ?

N

clean room? aros is such. what concerns p96 mntmn is putting now his own p96 compatible headers on a public repo.

[wawrzon]

As you, I wouldn't put my hopes on it and certainly not stop a project because of it. Right now there is some momentum which should be used before it's lost.

what concerns momentum. one simply needs to start work on it. i have notified lukas about these threads, but i think he probably prefers to work, rather than to post around in amiga forums.

[billt]

Using GPL forces all programs using the library to also be GPL that is the reason why a GPL library can't be included in AROS but a LGPL one can.

This can be tricky to understand. Are you using a GPL library here, and thus taking on the GPL, or is the GPL library using something else from the OS or other binary-only proprietary distribution? You can't write a GPL thing that makes MS Windows become a GPL OS just because some GPL thing used an OS function call...

Look at ReactOS, it's a GPL reimplementation of old MS Windows API and intends to be binary compatible with drivers and apps etc. written/compiled  for MS Windows. I don't believe that a user trying to run some proprietary app on ReactOS makes that app become GPL. You can also have proprietary software on Linux.

So, where are the GPL lines here, and which direction are the calls going in, how do all pieces fit togehter, and when and under what conditions did which binary get compiled? Are there legacy proprietary things making use of other legacy proprietary things, and you are trying to fit in an open-source layer in between them, or replacing them? Legacy proprietary things can remain proprietary, as they were not written for or linked with a GPL thing, they were designed to a proprietary companion. Pulling that proprietary companion piece away and replacing it without knowledge of the original proprietary author or toolset does not force GPL onto the other proprietary thing that isn't aware its now making use of a GPL companion thing. While some see GPL as a cancer, it doesn't grow quite that way...

You can also look at using LGPL middleman tricks, such as how some proprietary drivers work with Linux kernel. That gets further into grey area, but the above is less grey than that.

[Fats]

Look at ReactOS, it's a GPL reimplementation of old MS Windows API and intends to be binary compatible with drivers and apps etc. written/compiled  for MS Windows. I don't believe that a user trying to run some proprietary app on ReactOS makes that app become GPL. You can also have proprietary software on Linux.

If you would include OpenPCI GPL in AROS and non-GPL programs using the openpci.library it becomes very hard to argue these programs should not be GPL.