From: Michael Buesch <mb@bu3sch.de>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: netdev@vger.kernel.org
Subject: Re: proposal for new wireless configuration API
Date: Sat, 19 Aug 2006 00:02:42 +0200 [thread overview]
Message-ID: <200608190002.42436.mb@bu3sch.de> (raw)
In-Reply-To: <20060818212941.GB28711@p15091797.pureserver.info>
On Friday 18 August 2006 23:29, Ulrich Kunitz wrote:
> On 06-08-18 09:12 Johannes Berg wrote:
>
> > On Fri, 2006-08-18 at 01:29 +0200, Ulrich Kunitz wrote:
> > > Or are here people, who
> > > really want to freely transmit on all frequencies their RF might
> > > be able to generate?
> >
> > Yes :P
> > Some amateur radio people asked me about extending the spectrum a bit to
> > the top (apparently they're allowed to use the band just above the ISM
> > band as well).
>
> I had some discussions with radio amateurs about the RFs in the
> ZD1211 devices. Even if I could transmit in their required bands,
> the RFs are so WLAN specific, that they don't fulfill their
> requirements. It's really funny, if somebody explains to you that
> these chips are of extremely low quality. I always try to explain
> to them that the complete devices are sold for only 17 Euros
> including VAT. You cannot expect for this price the quality
> required for long range transmissions at these high frequencies.
>
> I support the idea that radio amateurs should create their own
> patches if they need it. Supporting the frequencies in the
> interface, is a typical feature used by less than 1% of the user
> base, but would cost more than 80% of the effort. We should also not
> do anything, which would raise the impression, that we want to
> ignore regulatory rules.
I second that.
We should not allow to drive devices outside of the specs.
If someone wants to do this, he should be able to apply a one-liner
patch to tune to some different frequency. ;)
> > However, I don't think we need to cater them in the API. I think they
> > ought to be able to live with kernel patches since we don't really know
> > how far up the frequency on say the bcm43xx can go anyway before the
> > card breaks/malfunctions.
>
> Do they have a separate RF? They data sheets are usually
> available, even if the not always explain the register
> programming.
We currently know 6 different radio chips used by bcm43xx:
http://bcm-specs.sipsolutions.net/RadioID
AFAIK the chip is from broadcom, too. I don't like to check
now, as that would require to disassemble my AP and look at
the chip. ;) But I'm pretty sure.
There is no datasheet available for the chip. At least nobody
was able to get or found one so far... .
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-18 22:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 15:28 proposal for new wireless configuration API Johannes Berg
2006-08-15 16:14 ` Luis R. Rodriguez
2006-08-16 7:26 ` Johannes Berg
2006-08-15 16:29 ` Dan Williams
2006-08-15 16:38 ` Michael Buesch
2006-08-15 18:14 ` Dan Williams
2006-08-15 19:13 ` Michael Buesch
2006-08-15 19:27 ` Simon Barber
2006-08-15 19:35 ` Michael Buesch
2006-08-15 20:06 ` Dan Williams
2006-08-15 19:59 ` Dan Williams
2006-08-16 7:14 ` Johannes Berg
2006-08-17 19:39 ` Jean Tourrilhes
2006-08-17 21:24 ` Michael Buesch
2006-08-17 23:29 ` Ulrich Kunitz
2006-08-18 7:12 ` Johannes Berg
2006-08-18 15:00 ` John W. Linville
2006-08-18 21:29 ` Ulrich Kunitz
2006-08-18 22:02 ` Michael Buesch [this message]
2006-08-21 7:31 ` Johannes Berg
2006-08-16 6:51 ` Johannes Berg
2006-08-16 18:02 ` Simon Barber
2006-08-17 7:19 ` Johannes Berg
2006-08-17 16:42 ` Simon Barber
2006-08-17 23:23 ` Ulrich Kunitz
2006-08-18 7:01 ` Johannes Berg
2006-08-18 16:45 ` Simon Barber
2006-08-21 6:45 ` Johannes Berg
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=200608190002.42436.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=kune@deine-taler.de \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).