From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jan Dittmer <jdi@l4x.org>
Cc: Theodore Tso <tytso@mit.edu>, Kasper Sandberg <lkml@metanurb.dk>,
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:32:03 +0100 [thread overview]
Message-ID: <20060730163203.GA31495@srcf.ucam.org> (raw)
In-Reply-To: <44CCDD7E.3010207@l4x.org>
On Sun, Jul 30, 2006 at 06:25:34PM +0200, Jan Dittmer wrote:
> So if this is done, there should be a clearly abstracted interface
> for such a daemon. I don't see what the daemon is doing more than
> echo 1 4 7 8 > /sys/.../allowed_channels and a control circuit for
> tx/rx power.
The daemon sets the list of acceptable channels, the transmission powers
for each of them and modifies this based on things like the temperature.
Oh, yes, and it writes 802.11 scan frames that get passed straight to
the firmware and broadcast. Insane crack. For reasons I don't as yet
understand, various received frames also get passed back up to the
daemon. I probably really don't want to know why.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-07-30 16:32 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 [this message]
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
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=20060730163203.GA31495@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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=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