<br><br><div class="gmail_quote">On Wed, Apr 2, 2008 at 5:33 AM, Andy Green <<a href="mailto:andy@openmoko.com">andy@openmoko.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Somebody in the thread at some point said:<br></div><div><div></div><div class="Wj3C7c">
| On Wednesday 02 April 2008 11:07:47 Andy Green wrote:<br>
|> There's a 6) I thought about, AFAIK it could theoretically anyway be<br>
|> possible we can write detailed header files for an open driver which<br>
|> contain register and bitfield enums and comments for the 3D unit. If we<br>
|> did write our own we would certainly have to do this anyway and<br>
|> presumably it is okay by whatever agreement exists (but surprises are<br>
|> the norm here).<br>
|<br>
| How about the 7) developer to become a new OM "employee" and thus gets<br>
access<br>
| (unpaid intern or something like that, if nothing else) to the OM license?<br>
<br></div></div>
I think we have to be seen to take care about the spirit of the<br>
agreement as well as the letter or the consequences could be negative<br>
all around.<br>
<br>
But the agreement must allow for transcription of the information into a<br>
FOSS driver because otherwise there'd be no point. So this would be a<br>
"way through it" rather than a "way around it".</blockquote><div><br>No one has suggested it yet, but could this be a Summer of Code project? Harald's note seemed to indicate that the product of such an effort would be an open-source driver, and documentation to assist in writing of other drivers.<br>
<br>I'm not sure if this would be close enough to the spirit, though. Could this be a way through it too?<br><br>Gerald<br> </div></div>