From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262629AbVAEUPO (ORCPT ); Wed, 5 Jan 2005 15:15:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262630AbVAEUPO (ORCPT ); Wed, 5 Jan 2005 15:15:14 -0500 Received: from perpugilliam.csclub.uwaterloo.ca ([129.97.134.31]:24720 "EHLO perpugilliam.csclub.uwaterloo.ca") by vger.kernel.org with ESMTP id S262624AbVAEUOh (ORCPT ); Wed, 5 Jan 2005 15:14:37 -0500 Date: Wed, 5 Jan 2005 15:14:34 -0500 To: prism54-devel@prism54.org, prism54-users@prism54.org, Netdev , linux-kernel@vger.kernel.org, Jeff Garzik , Jean Tourrilhes Subject: Re: Open hardware wireless cards Message-ID: <20050105201434.GB30311@csclub.uwaterloo.ca> References: <20050105192447.GJ5159@ruslug.rutgers.edu> <20050105200526.GL5159@ruslug.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050105200526.GL5159@ruslug.rutgers.edu> User-Agent: Mutt/1.3.28i From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 05, 2005 at 03:05:26PM -0500, Luis R. Rodriguez wrote: > I'd also like to add... > > For those of you frustrated about our current wireless driver situation > in open platforms -- > > I think we probably will have this trouble with most modern hardware for a while > (graphics cards, wireless driver, etc). A lot of has to do with patent > infringement issues, "intellectual property" protection, and other > business-oriented excuses. > > What I think we probably will have to do is just work torwards seeing if > we can come up with our own open wireless hardware. I know there was > a recent thread on lkml about an open video card -- anyone know where > that ended up? > > If we can't come up with our own project to work on open hardware we can > also just see if its feasible to purchase hardware companies on the > verge of going backrupt and buy them out and release the specs/etc (a la > blender). Can someone do the math here? I'm lazy. Being open doesn't mean you aren't violating some stupid patent. Software patents really are an incredibly stupid idea. Algorithms are pushing it. After all what does the algorithm do on it's own? Can you show it working and doing something? Len Sorensen