Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752581AbWLWHTk (ORCPT ); Sat, 23 Dec 2006 02:19:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752628AbWLWHTk (ORCPT ); Sat, 23 Dec 2006 02:19:40 -0500 Received: from mail1.webmaster.com ([216.152.64.169]:1943 "EHLO mail1.webmaster.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752581AbWLWHTj (ORCPT ); Sat, 23 Dec 2006 02:19:39 -0500 From: "David Schwartz" To: "Linux-Kernel@Vger. Kernel. Org" Subject: RE: Binary Drivers Date: Fri, 22 Dec 2006 23:19:09 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <7b69d1470612221414h7bca6dd3x89f52be55a47746d@mail.gmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Importance: Normal X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Sat, 23 Dec 2006 00:21:40 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: linux-kernel@vger.kernel.org Reply-To: davids@webmaster.com X-MDAV-Processed: mail1.webmaster.com, Sat, 23 Dec 2006 00:21:40 -0800 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2677 Lines: 54 > Two of the specific arguments I've heard are (a) that the board (and > its hardware interfaces that the documentation would describe) involve > IP licensed from a third party, which the board manufacturer does not > have a legal right to disclose, If they can't disclose it, they can't sell it. If they can't sell it, it's fraud to tell someone that they can buy it. If a contract with a third party limits your ability to sell something to someone, you have to *tell* *them* that they do not get all of the rights of ownership because you don't own some of them and hence can't transfer them. If I can't tell you what you're buying, I can't sell it to you. It's really that simple. I might be able to make some kind of agreement with you that's something like a sale, but it is not a normal sale and you are not buying the expected type of ownership. To claim it's a sale is fraud. > or (b) that there is, in fact, no > suitable documentation, because the boards are developed somewhat > fluidly and the driver is developed directly from low-level knowledge > that simply isn't written down in a form suitable for passing on. You can't sell something that doesn't exist. If you sell a car even though you can't explain how anyone could drive it, that's fraud. A person who buys something is entitled to be told how to operate it and make it work (and not just the one way you think they should use it, they have the right to use it any way they want if the transaction is a normal sale including all rights). If you can't tell them that, then they are not actually buying all of the thing. > If you're building products with no expectation of supporting outside > driver developers, both of those are quite possible. And they're both quite fraudulent. You cannot both sell something and keep its construction a secret. A person who owns something has a right to be told what they're buying. If you are only selling some of the rights that normally come with buying something, you cannot claim you are selling it free and clear. As I said before, this same thing used to happen with cell phones. I bought a Primeco phone, fully believing that I fully owned it. However, Primeco refused to tell me the code to unlock the phone, demanding $200 to do so. That's simply fraud -- if I fully own the phone, free and clear, they have no right to sell access to it to me. You can't sell the car and then charge for the keys. DS - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/