Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750714AbVLGILP (ORCPT ); Wed, 7 Dec 2005 03:11:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750721AbVLGILP (ORCPT ); Wed, 7 Dec 2005 03:11:15 -0500 Received: from main.gmane.org ([80.91.229.2]:20461 "EHLO ciao.gmane.org") by vger.kernel.org with ESMTP id S1750714AbVLGILP (ORCPT ); Wed, 7 Dec 2005 03:11:15 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Dirk Steuwer Subject: Re: Linux in a binary world... a doomsday scenario Date: Wed, 7 Dec 2005 08:09:09 +0000 (UTC) Message-ID: References: <1133779953.9356.9.camel@laptopd505.fenrus.org> <1133894933.29084.3.camel@mindpipe> <200512062135.51960.grahame@regress.homelinux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 84.56.62.30 (Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20051010 Firefox/1.0.7 (Ubuntu package 1.0.7)) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1657 Lines: 35 Grahame White regress.homelinux.org> writes: > Then how about a "formal" linux certified logo? IOW a logo that can *only* > be used if the hardware has drivers that were written using an officially > supplied set of specifications and if said drivers are available under an > OSI certified licence. Any use of the logo on a piece of hardware that is > not certified would be liable to legal action. > > Admittedly this would require a fair amount of effort to set up and uphold > but if it helped make it easier to choose compatible hardware it could be > worth it. Yes, precisely what i was talking about. Something really simple joe average can follow. It has to be validated from a license point of view, but also from a technical side. Otherwise, hardware folks license a piece of hardware and then change something along the way, which doesn't work with the driver. So ideally you have the according linux kernel hacker acknowledging this as well was OSI or someone else. This would be a fantastic central database to look up for linux hardware compatibility. With clever Marketing, this in itself could be turn up quite some revenue. Part of the money could be returned to kernel bounty payment.... And this would put tremendous pressure on hardware folk to get in there - job done. I think this is feasable and if it chucks out some money, i can be done. regards, Dirk - 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/