All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Regulatory domain
Date: Wed, 16 Mar 2011 21:00:16 +0100	[thread overview]
Message-ID: <20110316200016.8343.qmail@stuge.se> (raw)
In-Reply-To: <20110316194711.GA15689@tux>

Luis R. Rodriguez wrote:
> > Need to make that utility.
> 
> Blindly overwriting EEPROMs is a bad idea,

Such a utility must do the right thing of course! :) Only change the
right bits, in the right way. I haven't looked yet but I expect the
driver will show which bits matter, and how.


> You have the freedom to do what you please but essentially you
> loose my support completley for anything you ever report :)

Ah but I will not lose very much then! ;) SCNR, hehe.

I of course get your point that the EEPROM drives other things in
the driver and firmware than just reg domain, and that it's important
to be careful about which bits are touched.

This is another case where it would be cool if Atheros was open about
technical details, because instead of someone reverse engineering the
EEPROM contents there could be a known-reliable utility (a la ART)
which had expert knowledge about all the little corner cases. I guess
it's simply impossible to talk radio tech without rubbing FCC the
wrong way. So broken.. :\


//Peter

  reply	other threads:[~2011-03-16 20:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 15:49 [ath9k-devel] Regulatory domain Baldomero Coll
2011-03-16 15:59 ` Peter Stuge
2011-03-16 19:47   ` Luis R. Rodriguez
2011-03-16 20:00     ` Peter Stuge [this message]
2011-03-16 21:15       ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2011-03-17 10:49 Baldomero Coll
2011-03-17 10:59 ` Peter Stuge
2011-03-21 17:55 ` Luis R. Rodriguez
2011-03-21 18:08   ` Peter Stuge
2011-03-21 18:22     ` Luis R. Rodriguez
2009-02-27  1:06 Xaero
2009-02-27  3:26 ` Luis R. Rodriguez

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=20110316200016.8343.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.