From: Denis Vlasenko <vda@ilport.com.ua>
To: andi@lisas.de
Cc: acx100-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] improve configopt, slightly correct acx111 radio recalib
Date: Wed, 11 Jan 2006 08:42:24 +0200 [thread overview]
Message-ID: <200601110842.24245.vda@ilport.com.ua> (raw)
In-Reply-To: <20060110151104.GA28270@rhlx01.fht-esslingen.de>
On Tuesday 10 January 2006 17:11, Andreas Mohr wrote:
> Hi all,
>
> this patch adds support for configopt parsing for ACX100 EEPROM version v5
> (please report whether ACX100 v5 now works, preferrably with logs showing
> configopt activity).
>
> Also, we now only start another radio recalibration interval every 5 seconds
> on ACX111 instead of every second (in case of radio recalibration FAILURES,
> that is). 5 recalibration attempts every second in case of repeated failure
> is waaaaay too much, both for undistorted card operation and syslog.
-unsigned int acx_debug = L_ASSOC|L_INIT;
+unsigned int acx_debug __read_mostly = L_ASSOC|L_INIT;
I think __read_mostly is not worth the compat trouble it currently will require
(#ifdef LINUX_VERSION_CODE...).
+ }
+ else
+ {
Changing this to "} else {".
Patch applied, thanks!
BTW, currently we have
priv->scan_probe_delay = 200;
/* reported to break scanning: priv->scan_probe_delay = priv->cfgopt_probe_delay; */
Do I need to uncomment that?
--
vda
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next parent reply other threads:[~2006-01-11 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060110151104.GA28270@rhlx01.fht-esslingen.de>
2006-01-11 6:42 ` Denis Vlasenko [this message]
2006-01-11 8:50 ` Re: [PATCH] improve configopt, slightly correct acx111 radio recalib Andreas Mohr
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=200601110842.24245.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=acx100-devel@lists.sourceforge.net \
--cc=andi@lisas.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).