From: James Courtier-Dutton <James@superbug.co.uk>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, Jan Dittmer <jdi@l4x.org>,
Pavel Machek <pavel@suse.cz>, Jirka Lenost Benc <jbenc@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ipw2100-admin@linux.intel.com
Subject: Re: ipw3945 status
Date: Sun, 30 Jul 2006 17:58:09 +0100 [thread overview]
Message-ID: <44CCE521.7090705@superbug.co.uk> (raw)
In-Reply-To: <1154264478.13635.22.camel@localhost>
Kasper Sandberg wrote:
>> Because it would involve a moderate rewriting of the driver, and we'd
>> have to carry a delta against Intel's code forever.
> without knowing this for sure, dont you think that if a largely changed
> version of the driver appeared in the tree, intel may start developing
> on that? cause then they wouldnt be the ones that "broke" compliance
> with FCC(hah) by not doing binaryonly.
>
Where can I find this FCC law that seems to be crippling open source
wlan development?
I am not from the USA, so I don't have to comply with the FCC. Could we
make a non-crippled totally open source driver for use by people outside
the USA?
For example, here in the UK one can own radios that can transmit on any
frequency one likes, but if you actually press the TX button without a
the appropriate License, you break the law.
James
next prev parent reply other threads:[~2006-07-30 16:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 10:40 ipw3945 status Pavel Machek
2006-07-30 11:28 ` Matthew Garrett
2006-07-30 11:30 ` Pavel Machek
2006-07-30 11:34 ` Jan Dittmer
2006-07-30 11:47 ` Matthew Garrett
2006-07-30 13:01 ` Kasper Sandberg
2006-07-30 14:53 ` Theodore Tso
2006-07-30 15:00 ` Kasper Sandberg
2006-07-30 15:09 ` Theodore Tso
2006-07-30 16:09 ` Kasper Sandberg
2006-07-30 16:25 ` Jan Dittmer
2006-07-30 16:32 ` Matthew Garrett
2006-07-30 17:52 ` Alan Cox
2006-07-30 23:12 ` Pavel Machek
2006-07-31 0:23 ` Alistair John Strachan
2006-07-31 1:16 ` Kasper Sandberg
2006-07-31 6:06 ` Alon Bar-Lev
2006-07-31 8:32 ` Kasper Sandberg
2006-07-30 16:58 ` James Courtier-Dutton [this message]
2006-07-30 17:25 ` Kasper Sandberg
2006-07-30 17:37 ` Rene Rebe
2006-07-30 18:03 ` Kasper Sandberg
2006-07-30 20:09 ` Rene Rebe
2006-07-30 21:02 ` Kasper Sandberg
2006-07-30 23:44 ` Alan Cox
2006-07-31 0:19 ` Kasper Sandberg
2006-07-31 7:11 ` Rene Rebe
2006-07-30 15:57 ` Tomasz Torcz
2006-07-30 16:01 ` Matthew Garrett
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=44CCE521.7090705@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=ipw2100-admin@linux.intel.com \
--cc=jbenc@suse.cz \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@suse.cz \
/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