[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <orodjefgrc.fsf@oliva.athome.lsd.ic.unicamp.br>
Date: Sun, 17 Jun 2007 17:49:43 -0300
From: Alexandre Oliva <aoliva@...hat.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Ingo Molnar <mingo@...e.hu>, Daniel Hazelton <dhazelton@...er.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <greg@...ah.com>,
debian developer <debiandev@...il.com>, david@...g.hm,
Tarkan Erimer <tarkan@...one.net.tr>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
On Jun 17, 2007, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Sun, 17 Jun 2007 15:33:33 -0300
> Alexandre Oliva <aoliva@...hat.com> wrote:
>> On Jun 17, 2007, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>>
>> >> I don't know any law that requires tivoization.
>>
>> > In the USSA it is arguable that wireless might need it (if done in
>> > software) for certain properties. (The argument being it must be
>> > tamperproof to random end consumers).
>>
>> But this is not tivoization.
> It most definitely is
>> Tivoization is a manufacturer using technical measures to prevent the
>> user from tampering (*) with the device, *while* keeping the ability
>> to tamper with it changes itself.
> That accurately describes the FCC wireless rules.
AFAIK the FCC mandates not permitting the user to tinker. It doesn't
mandate the vendor to retain this ability to itself.
Therefore, per the above, FCC doesn't mandate tivoization.
Is there anything else I'm missing that would show it does?
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists