linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Norbert van Nobelen <norbert-kernel@edusupport.nl>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Sun, 9 Jan 2005 10:59:04 +0100	[thread overview]
Message-ID: <200501091059.04839.norbert-kernel@edusupport.nl> (raw)
In-Reply-To: <20050108204759.GQ14108@stusta.de>

On Saturday 08 January 2005 21:47, you wrote:
> On Wed, Jan 05, 2005 at 10:09:29PM +0100, Tomasz Torcz wrote:
> > On Wed, Jan 05, 2005 at 03:14:34PM -0500, Lennart Sorensen wrote:
> > > > 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.
> >
> >  Only in some countries. We can ignore those countries.
>
> Patents on hardware are legal and common in _many_ countries including
> all countries in the EU.
>
> cu
> Adrian

There are several independent designs in the market for these chipsets, but as 
far as I know the patents only govern the complete chipset, thus the contents 
of the chipset is not to be worried about.
The other patent issue is the 802.11 standard itself. Is that patent free? 
(IE: That would be a stupid patent)

-- 
<a href="http://www.edusupport.nl">EduSupport: Linux Desktop for schools and 
small to medium business in The Netherlands and Belgium</a>

  reply	other threads:[~2005-01-09  9:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050105192447.GJ5159@ruslug.rutgers.edu>
2005-01-05 20:05 ` Open hardware wireless cards Luis R. Rodriguez
2005-01-05 20:14   ` Lennart Sorensen
2005-01-05 20:48     ` linux-os
2005-01-05 21:35       ` Lennart Sorensen
2005-01-05 21:09     ` Tomasz Torcz
2005-01-08 20:47       ` Adrian Bunk
2005-01-09  9:59         ` Norbert van Nobelen [this message]
2005-01-09 22:28           ` Bernd Petrovitsch
2005-01-09 23:00           ` Alan Cox
2005-01-05 20:17   ` Raphael Jacquot
2005-01-05 20:26     ` Luis R. Rodriguez
2005-01-06  8:02       ` Norbert van Nobelen
2005-01-06 17:24         ` Luis R. Rodriguez
2005-01-06 17:37           ` Lee Revell
2005-01-06 17:38             ` Luis R. Rodriguez
2005-01-06 17:42               ` Lee Revell
2005-01-06 19:06                 ` Norbert van Nobelen
     [not found]                   ` <1105044024.15770.7.camel@krustophenia.net>
2005-01-06 20:51                     ` Norbert van Nobelen
2005-01-06 17:59             ` Alan Cox
2005-01-06 20:25               ` Lee Revell
2005-01-07 10:37               ` Aaron Lehmann
2005-01-06 19:11           ` Raphael Jacquot
2005-01-06 19:32             ` Norbert van Nobelen
2005-01-06 21:00               ` Lee Revell
2005-01-06 21:24                 ` Lennart Sorensen
2005-01-06 21:39                 ` Jim Nelson
2005-01-06 21:42                   ` Norbert van Nobelen
2005-01-08 11:58                   ` Paul Jakma
2005-01-06 21:43                 ` Christoph Hellwig
2005-01-05 20:22   ` [Prism54-users] " Steve Hill
2005-01-05 20:36     ` Luis R. Rodriguez
2005-01-05 22:19   ` christos gentsis
2005-04-19 19:07   ` Karel Kulhavy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501091059.04839.norbert-kernel@edusupport.nl \
    --to=norbert-kernel@edusupport.nl \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).