From: elektra <onelektra@gmx.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] sysfs compat
Date: Tue, 4 May 2010 15:05:34 +0200 [thread overview]
Message-ID: <201005041505.34855.onelektra@gmx.net> (raw)
In-Reply-To: <4BE014CC.50904@aon.at>
Hi Franz -
there are certified devices out there, running OpenWrt / open-source drivers.
May I ask, what particular regulator issues you have in mind, that a open-
source driver can not comply with? Read: Are you sure you don't get the
regulators blessing for your product with a open-source driver?
Besides: Do you know this song by Eric Idle, regarding the FCC?
http://www.youtube.com/watch?v=F4ajZ-5kTXk
A few memes:
Any product can be tampered with.
In many certified devices you can simply switch the reg domain. Then choose
Japan, for example. Now you can transmit on channel 14 in the 2.4GHz range.
Not so legal anywhere outside of Nippon.
The old Broadcom chipset / proprietary driver can be configured to transmit at
250mW with the proprietary closed source driver. Hence you can transmit at
~25dbm EIRP (with the stock antennas), far beyond the ETSI regulations of
20dBm EIRP.
Any device with a external antenna connector can be used together with a high-
gain antenna. Again you get far beyond the legal limits.
Cheers,
Elektra
next prev parent reply other threads:[~2010-05-04 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 0:28 [B.A.T.M.A.N.] sysfs compat Marek Lindner
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: adding MAC_FMT compatibility Marek Lindner
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: adding sysfs compat Marek Lindner
2010-05-03 8:03 ` [B.A.T.M.A.N.] " Andrew Lunn
2010-05-03 9:05 ` Franz Böhm
2010-05-03 10:30 ` Sven Eckelmann
2010-05-03 20:40 ` Simon Wunderlich
2010-05-04 2:21 ` Marek Lindner
2010-05-04 11:13 ` Franz Böhm
2010-05-04 11:40 ` elektra
2010-05-04 12:36 ` Franz Böhm
2010-05-04 13:05 ` elektra [this message]
2010-05-04 17:34 ` Franz Böhm
2010-05-04 23:59 ` RHS Linux User
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=201005041505.34855.onelektra@gmx.net \
--to=onelektra@gmx.net \
--cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox