From: Richard Farina <sidhayn@gmail.com>
To: wireless <linux-wireless@vger.kernel.org>
Subject: [Fwd: please don't regress ath5k.h]
Date: Sun, 23 Nov 2008 21:42:47 -0500 [thread overview]
Message-ID: <492A14A7.4040808@gmail.com> (raw)
sorry for sending twice, accidentally sent to owner instead of list...
wireless-testing.git/drivers/net/wireless/ath5k/ath5k.h
/* TODO: Clean up channel debuging -doesn't work anyway- and start
* working on reg. control code using all available eeprom information
* -rev. engineering needed- */
#define CHAN_DEBUG 0
I recently saw this additional comment added to wireless-testing.git and
it has me a bit concerned. I use this feature for a specific patch set
that I maintain and it would break it pretty bad to remove this. I
don't believe I need all of the features that chan_debug provides, but
when I set chan_debug to 0 it severely limits the number of channels
that I can set the driver to. I currently maintain a patch that
supports 471 channels for atheros a/b/g cards and without chan_debug 1
it simply cuts the top channels off (because it isn't able to have that
many channels). It is my opinion that the driver should support what
the hardware supports and the regulatory requirements should be handled
by crda as expected, I will submit some patches to this effect asap but
in the mean time please do not remove chan_debug without enabling
support for at least 471 channels to be stored (and it would be cool to
cc me on that patch so I can follow it and make sure it works for me).
Thanks,
Rick Farina
PS> Please note, this is not meant to start a discussion about adding in
addition channels that may or may not be legal, I promise I'll start
that discussion next, but this mail is to request that a feature I'm not
using not be removed from the driver breaking my work. Thanks.
next reply other threads:[~2008-11-24 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 2:42 Richard Farina [this message]
2008-11-24 5:44 ` [Fwd: please don't regress ath5k.h] Michael Renzmann
2008-11-24 6:16 ` Johannes Berg
2008-11-24 15:29 ` Richard Farina
2008-11-24 18:29 ` Jouni Malinen
2008-11-24 18:39 ` Richard Farina
2008-11-24 21:35 ` Luis R. Rodriguez
2008-11-24 22:21 ` Richard Farina
2008-11-24 23:01 ` Luis R. Rodriguez
2008-11-24 20:25 ` Nick Kossifidis
2008-11-24 20:51 ` Richard Farina
2008-11-24 20:52 ` Nick Kossifidis
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=492A14A7.4040808@gmail.com \
--to=sidhayn@gmail.com \
--cc=linux-wireless@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 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.