From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: Theodore Tso <tytso@mit.edu>, Kasper Sandberg <lkml@metanurb.dk>,
Matthew Garrett <mjg59@srcf.ucam.org>, Jan Dittmer <jdi@l4x.org>,
Jirka Lenost Benc <jbenc@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ipw2100-admin@linux.intel.com
Subject: Re: ipw3945 status
Date: Mon, 31 Jul 2006 01:23:06 +0100 [thread overview]
Message-ID: <200607310123.06177.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20060730231251.GB1800@elf.ucw.cz>
On Monday 31 July 2006 00:12, Pavel Machek wrote:
[snip]
> And... Intel will not even tell you WTF that daemon does. They claim
> it is for FCC, but it seems to be doing more than that. So maybe I'm
> not _that_ paranoid.
Agreed, from what Matthew's said it seems like the daemon is being used to
hide intellectual property, not something we should really be encouraging.
I think the title "regulatory daemon" has multiple meanings, it REGULATES your
frequencies to FCC specs, it REGULATES your wireless card's power and
temperature levels, and it REGULATES your right to use the hardware ;-)
Ultimately the question remains, will we open this can of worms by accepting
drivers that depend on proprietary software (i.e. they will not function at
all without it). I'm fairly sure the answer should be "No".
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-07-31 0:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 10:40 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 [this message]
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
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=200607310123.06177.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.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 \
--cc=tytso@mit.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
all inboxes | Powered by JetHome®