linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux-os <linux-os@chaos.analogic.com>
To: lsorense@csclub.uwaterloo.ca
Cc: prism54-devel@prism54.org, prism54-users@prism54.org,
	Netdev <netdev@oss.sgi.com>,
	linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	Jean Tourrilhes <jt@bougret.hpl.hp.com>
Subject: Re: Open hardware wireless cards
Date: Wed, 5 Jan 2005 15:48:46 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501051533470.12237@chaos.analogic.com> (raw)
In-Reply-To: <20050105201434.GB30311@csclub.uwaterloo.ca>

On Wed, 5 Jan 2005 lsorense@csclub.uwaterloo.ca wrote:

> 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

Well its mostly about making boards just a bit too cheap.

If the vendors would just put in a serial EPROM that loads the
proprietary stuff to their PLD upon startup, then there is
no "proprietary" code to worry about. You have the generic
published interface like a PLX chip, plus the specific published
register functions of their PLD chip. How the device actually
makes smoke and mirrors is hidden even from the programmer.

But, by eliminating the US$0.50 cost of a EPROM, they want to supply
a sack of bits that needs to be uploaded to the PLD by software. This
sack of bits can be reverse-engineered so companies are not going
to supply these (you can extract those bits from a Win-Modem dll so
this gets a bit too ridiculous for some devices).

In most cases it's not some algorithm that needs to be protected.
Instead its the 400-or-so engineering man-hours used to develop the
contents of the PLD (notice I did not use the words "Gate-Arrays"
until now. There are many kinds of Programmable Logic Devices).

Until vendors stop being penny-wise-pound-foolish, we will continue
to have these kinds of problems. Vendor education will ultimately
be the fix, I predict.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by Dictator Bush.
                  98.36% of all statistics are fiction.

  reply	other threads:[~2005-01-05 20:56 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 [this message]
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
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=Pine.LNX.4.61.0501051533470.12237@chaos.analogic.com \
    --to=linux-os@chaos.analogic.com \
    --cc=jgarzik@pobox.com \
    --cc=jt@bougret.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@oss.sgi.com \
    --cc=prism54-devel@prism54.org \
    --cc=prism54-users@prism54.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).