linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mcgrof@studorgs.rutgers.edu (Luis R. Rodriguez)
To: Norbert van Nobelen <norbert-kernel@edusupport.nl>
Cc: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
	linux-kernel@vger.kernel.org, prism54-devel@prism54.org
Subject: Re: Open hardware wireless cards
Date: Thu, 6 Jan 2005 12:24:38 -0500	[thread overview]
Message-ID: <20050106172438.GT5159@ruslug.rutgers.edu> (raw)
In-Reply-To: <200501060902.07502.norbert-kernel@edusupport.nl>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Thu, Jan 06, 2005 at 09:02:07AM +0100, Norbert van Nobelen wrote:
> You don't have to buy a company. There are white label manufacturers which are 
> happy to produce any card you like 

Excellent

> (but how big will the volume be?). 

Maybe 100 / month?

> The point is just to find or design the chipset, from there on the card.

Ok lets try giving this a shot by seeing if we can get a company to let
another manufacture a specific card design for us.  We can do this by
getting people to sign up for the card once we have details. Once we
reach a threshold we charge all users and order in-bulk to the
manufacturer. How's this sound? We can use linuxwireless.org for this.

I'll see if I can get people from Conexant to agree to let us use the
old fullmac chipset design for starters, since we already have that
driver in the stock kernel.

> What is also possible, is just to design an open chipset like the openrisc 
> guys did: They designed and published the design of a risc processor under I 
> believe GPL (have to look it up).
> If you let companies use that design to produce their open card, you will have 
> solved the problem. Companies like Trust (Dutch white label company: Buy a 
> stack of stuff, and put Trust label on it), will probably pick this up

Cool we should get an estimate to see how many cards they'd need in
order to start a bulk order.

	Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-06 17:25 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
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 [this message]
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=20050106172438.GT5159@ruslug.rutgers.edu \
    --to=mcgrof@studorgs.rutgers.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norbert-kernel@edusupport.nl \
    --cc=prism54-devel@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).