From: Karel Kulhavy <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Open hardware wireless cards
Date: Tue, 19 Apr 2005 19:07:40 +0000 [thread overview]
Message-ID: <20050419190740.GA8517@beton.cybernet.src> (raw)
In-Reply-To: <20050105200526.GL5159@ruslug.rutgers.edu>
On Wed, Jan 05, 2005 at 03:05:26PM -0500, Luis R. Rodriguez wrote:
> On Wed, Jan 05, 2005 at 02:24:47PM -0500, Luis R. Rodriguez wrote:
> <-- snip -->
>
> > As far as support for the new chipsets goes -- sorry -- we won't be able
> > to support it as I don't think even Conexant has a final well tested
> > linux source base ready for 2.6. And even if we are given a source base
> > there is nothing we can do to get around the need for the closed-source
> > softmac libs that it relies on. As much as I'd like to support it, I
> > don't want to get a headache to support something I cannot modify so I
> > won't be willing to support a half-opened driver as the atheros driver.
>
> 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?
I got open hardware optical wireless, though it's not a card, just
add-on to existing Ethernet:
http://ronja.twibright.com
Nevertheless it show how to use the free-software toolchain.
Also see GNU Radio.
http://www.gnu.org/software/gnuradio/doc/exploring-gnuradio.html
CL<
prev parent reply other threads:[~2005-04-19 19:05 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
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 [this message]
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=20050419190740.GA8517@beton.cybernet.src \
--to=clock@twibright.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.