Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752188AbWLOOMN (ORCPT ); Fri, 15 Dec 2006 09:12:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752186AbWLOOMN (ORCPT ); Fri, 15 Dec 2006 09:12:13 -0500 Received: from aa011msr.fastwebnet.it ([85.18.95.71]:56103 "EHLO aa011msr.fastwebnet.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752188AbWLOOMM (ORCPT ); Fri, 15 Dec 2006 09:12:12 -0500 X-Greylist: delayed 309 seconds by postgrey-1.27 at vger.kernel.org; Fri, 15 Dec 2006 09:12:12 EST Date: Fri, 15 Dec 2006 15:05:23 +0100 From: Paolo Ornati To: davids@webmaster.com Cc: "Linux-Kernel@Vger. Kernel. Org" Subject: Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches for 2.6.19] Message-ID: <20061215150523.662d981f@localhost> In-Reply-To: References: <20061214153949.GA3388@stusta.de> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.10.6; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2182 Lines: 52 On Thu, 14 Dec 2006 12:08:11 -0800 "David Schwartz" wrote: > > That is something that I think is well worth fixing. Doesn't Linus own the > trademark 'Linux'? How about some rules for use of that trademark and a > 'Works with Linux' logo that can only be used if the hardware specifications > are provided? > > Let them provide a closed-source driver if they want. Let them provide > user-space applications for which no source is provided if they want. But > don't let them use the logo unless they release sufficient information to > allow people to develop their own drivers and applications to interface with > the hardware. This is the same I think, but not Linux specific: http://wiki.duskglow.com/tiki-index.php?page=Open+Hardware+Foundation ------------------------------------------------------------------ P. Mc Namara 12 Jul 06: about the OHF foundation providing "certificates" for hardware, I'd propose (...) levels. * First, any company that pledges full and complete interface and behavioral documentation for a device, any docs necessary to make the device do everything it is designed to do, and makes it publicly available under nothing more cumbersome than the basic copyright that exists on all written works receives one certificate. Somebody else used "community friendly" or something similar. I don't know what to call it. Perhaps just "Open Documentation" (...) * A company that contributes back to the community during the development of a device get labeled "Community Supporter" or something similar. * A company that enters into a legal agreement to release the entire RTL and supporting information for a project at a given point in the future (far enough ahead to protect the companies commercial viability) can get the "Open Hardware" certificate. ------------------------------------------------------------------ -- Paolo Ornati Linux 2.6.18 on x86_64 - 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/