From: <bogus@does.not.exist.com>
To: ath9k-devel@lists.ath9k.org
Subject: No subject
Date: Fri, 05 Aug 2011 03:08:35 -0000 [thread overview]
Message-ID: <mailman.4.1320256157.5984.ath9k-devel@lists.ath9k.org> (raw)
so the user should only be allowed to change the value to anything else than
what is stored in the eeprom if we know it's a valid setting.
As far as I understand the EEPROM only stores a single value for the
antenna-switch setting, i.e. if there multiple valid values these must come from
somewhere else.
I don't know the exact electronic details of the implementation, so I'd go with
a list of known-to-be-good values (passed to the driver via platform-data)
instead of a causal check (e.g. don't allow to set the TX and RX to the same
antenna or whatever you imagine to possibly be an invalid setting).
Cheers
Daniel
next reply other threads:[~2011-08-05 3:08 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 3:08 bogus [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-19 18:31 No subject bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-06-13 6:24 bogus
2016-06-13 6:24 bogus
2016-02-09 7:29 bogus
2015-11-16 16:13 bogus
2015-10-12 17:26 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2013-09-15 9:49 bogus
2013-09-15 9:49 bogus
2013-09-15 9:49 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-01-16 21:46 bogus
2013-01-16 21:46 bogus
2012-11-08 9:33 bogus
2012-05-25 15:26 bogus
2012-05-25 15:26 bogus
2012-04-05 7:54 bogus
2012-04-05 7:54 bogus
2012-02-27 5:00 bogus
2012-02-27 5:00 bogus
2012-02-27 5:00 bogus
2012-01-15 8:24 bogus
2011-11-12 14:39 bogus
2011-11-12 14:39 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-06-04 23:16 bogus
2011-06-04 23:16 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-07-23 10:05 bogus
2010-03-25 17:02 bogus
2010-03-25 17:02 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-15 8:49 bogus
2009-01-04 17:33 bogus
2009-01-04 17:33 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-07-28 4:41 bogus
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=mailman.4.1320256157.5984.ath9k-devel@lists.ath9k.org \
--to=bogus@does.not.exist.com \
--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 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).