From: Norbert van Nobelen <norbert-kernel@edusupport.nl>
To: mcgrof@studorgs.rutgers.edu (Luis R. Rodriguez)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Thu, 6 Jan 2005 09:02:07 +0100 [thread overview]
Message-ID: <200501060902.07502.norbert-kernel@edusupport.nl> (raw)
In-Reply-To: <20050105202626.GN5159@ruslug.rutgers.edu>
You don't have to buy a company. There are white label manufacturers which are
happy to produce any card you like (but how big will the volume be?). The
point is just to find or design the chipset, from there on the card.
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
On Wednesday 05 January 2005 21:26, you wrote:
> On Wed, Jan 05, 2005 at 09:17:07PM +0100, Raphael Jacquot wrote:
> > Luis R. Rodriguez wrote:
> > >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?
> >
> > It's going. the company that the dude works at gave him the go ahead to
> > work full time on the project.
> >
> > http://lists.duskglow.com/mailman/listinfo/open-graphics
>
> Excellent we should start one for a wireless card. If we cannot come up
> with enough expertise perhaps we can look into buying out a company (?)
>
> Luis
--
<a href="http://www.edusupport.nl">EduSupport: Linux Desktop for schools and
small to medium business</a>
next prev parent reply other threads:[~2005-01-06 8:02 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 [this message]
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=200501060902.07502.norbert-kernel@edusupport.nl \
--to=norbert-kernel@edusupport.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@studorgs.rutgers.edu \
/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).