Ola Lundqvist <[EMAIL PROTECTED]> writes:
> Ok, you are probably right if the person use an automated tool to make
> this obfuscation. (Not sure though, see below).
>
> However as it is impossible to know if someone use a obfuscation program
> or if the person use a text editor to edit this, I can not see it as
> a violation anyway.
>
> At least it is a bit harsh to see it as a policy violation just because
> it may be obfuscated.
If you have 'char data[] = { 0xef, 0x45, ... };' and from running a
disassembler it is clear that this was produced with gcc for arm (yes,
that is not too wilde an idea) or some other compiler I think then it
is at least suspect.
Personaly I rather have such a char array under GPL than no driver or
a binary only driver. At least you can perfectly legaly dissasemble
the data and, comment the code and make it readable again.
Ultimately I think the decision is with ftp-master and then you have
to fight hard to reverse that. They usualy make good calls there.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
