From: Timothy Miller <miller@techsource.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: vda <vda@port.imtp.ilyichevsk.odessa.ua>,
Dax Kelson <dax@gurulabs.com>,
James Ketrenos <jketreno@linux.co.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Announce] Intel PRO/Wireless 2100 802.11b driver
Date: Wed, 10 Mar 2004 12:31:19 -0500 [thread overview]
Message-ID: <404F50E7.4090907@techsource.com> (raw)
In-Reply-To: <404ED404.4050604@pobox.com>
Jeff Garzik wrote:
> vda wrote:
>
>> *FLAME ALERT*
>> /me is slowly getting mad about his prism54 11g hardware
>> and its firmware, with neither firmware authors nor documentation
>> for this pile of silicon crap nowhere in sight
>>
>> What's so cool about having binary firmware? Bugs are bugs,
>> and you won't be able to even see bugs, less fix, in it.
>> I don't like being at the mercy of firmware authors.
>
>
>
> Well that's typical in wireless, unfortunately. Certain parts of
> wireless are political tennis balls with the US govt. and FCC. Sometimes
> "put it in firmware" is the only way get ever get open source drivers at
> all :/
>
> I'll pick firmware over no-driver any day.
>
Hmmm... As you may know, I'm a chip designer...
Are there not open specs on the wireless protocols? Could we not design
our own open-source wireless network hardware? What would the US
government have to say about an open-source implementation? Are there
patents which would impede us?
next prev parent reply other threads:[~2004-03-10 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 20:24 [Announce] Intel PRO/Wireless 2100 802.11b driver James Ketrenos
2004-03-09 20:57 ` Arjan van de Ven
2004-03-09 22:01 ` James Ketrenos
2004-03-09 23:48 ` Marcel Holtmann
2004-03-09 21:05 ` Timothy Miller
2004-03-09 21:12 ` Dax Kelson
2004-03-10 2:46 ` James Ketrenos
2004-03-10 8:15 ` vda
2004-03-10 8:38 ` Jeff Garzik
2004-03-10 17:31 ` Timothy Miller [this message]
2004-03-10 17:26 ` Jeff Garzik
2004-03-12 0:32 ` Lincoln Dale
2004-03-11 1:07 ` Joel Jaeggli
2004-03-10 12:35 ` bert hubert
2004-03-10 18:06 ` Disconnect
2004-03-11 22:45 ` Bill Davidsen
2004-03-10 7:52 ` Jan De Luyck
2004-03-11 6:23 ` Jan De Luyck
2004-03-11 7:48 ` James Ketrenos
2004-03-11 8:05 ` Jan De Luyck
2004-03-11 18:37 ` Stephen Hemminger
2004-03-11 22:14 ` James Ketrenos
2004-03-11 22:27 ` Bill Davidsen
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=404F50E7.4090907@techsource.com \
--to=miller@techsource.com \
--cc=dax@gurulabs.com \
--cc=jgarzik@pobox.com \
--cc=jketreno@linux.co.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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