1. 15 Nov, 2011 1 commit
  2. 10 Oct, 2011 2 commits
    • Luis R. Rodriguez's avatar
      crda: add support to send DFS master region · 8cbde045
      Luis R. Rodriguez authored
      wireless-regdb now has support for a DFS master region
      for each country. We must read this from the file and
      send it as an NL80211_ATTR_DFS_REGION attribute.
      
      We add a "creqs" value for the country structure but only
      use the first two bits as that is all we need right now.
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      8cbde045
    • Luis R. Rodriguez's avatar
      crda: fix null string assumption for alpha2 · e40afba1
      Luis R. Rodriguez authored
      The wireless-regdb only accounts for two bytes for
      the country code but CRDA defined the alpha2 to be
      as a string of length 2, and so does the nl80211 attribute
      policy:
      
              [NL80211_ATTR_REG_ALPHA2] = { .type = NLA_STRING, .len = 2 },
      
      The meaning of a string is it'll be null terminated, so if you
      do not add the null termination a country without the null termination
      will not match up with the nl80211 attribute policy.
      
      This has no impact for us unless we want to use the next available
      pad byte on the wireless-regdb. This fixes CRDA by using a local copy
      of the regdb's alpha2 that is properly null terminated and sending it.
      
      The implications of this change is that new wirelesss-regdb's that
      make use of the next pad byte for a country will get that country
      ignored for regulatory hints sent to the kernel. At this point we
      don't yet know what the next byte will be used for though so this
      has no impact. The second pad byte is being used for DFS and that
      is not impacted by this nor is this change required for it.
      
      Distributions should upgrade though in case we ever do decide to use
      this last precious country byte. I've tested that this indeed fixes
      the bogus issue I saw when instead of using the second pad byte we
      use the first pad byte. Thanks to Johannes for spotting the issue.
      Signed-off-by: default avatarJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      e40afba1
  3. 03 Oct, 2011 1 commit
  4. 09 Aug, 2011 1 commit
  5. 25 Jan, 2010 2 commits
    • Luis R. Rodriguez's avatar
      Space fix · 52300e7e
      Luis R. Rodriguez authored
      Signed-off-by: default avatarLuis R. Rodriguez <lrodriguez@atheros.com>
      52300e7e
    • Paul Fertser's avatar
      Implement runtime loading of RSA public keys · 7429427a
      Paul Fertser authored
      This patch allows crda to load and use additional keys from a
      pre-configured location for the database signature verification. This
      provides a convenient way for distro maintainers and card manufacturers to
      supply a custom regulatory database along with their public keys, without
      the need to recompile crda.
      
      Implemented for USE_OPENSSL=1 case only because libgcrypt lacks PEM parser.
      
      Default location for public keys in PEM format is
      /etc/wireless-regdb/pubkeys and can be changed by specifying
      RUNTIME_PUBKEY_DIR at the make command line.
      Signed-off-by: default avatarPaul Fertser <fercerpav@gmail.com>
      7429427a
  6. 13 Oct, 2009 1 commit
  7. 06 Aug, 2009 1 commit
    • Pavel Roskin's avatar
      CRDA and cross-compilation · c49eb5d1
      Pavel Roskin authored
      On Thu, 2009-08-06 at 09:56 -0700, Luis R. Rodriguez wrote:
      
      > ACK, is it possible to make it simpler?
      
      OK, here's my take.
      
      We only need a native compiler to verify regulatory.bin.  I believe it's
      orthogonal to building CRDA.
      
      For someone doing a cross-compilation, it makes no sense to verify the
      installed regulatory.bin.  Thus, the verification should be optional.
      
      But the compilation of regdbdump shouldn't be.  Firstly, it's installed
      by "make install".  Secondly, somebody may want to verify regulatory.bin
      on the target system.
      
      Here's the patch:
      
      crda: make it possible to disable verification
      Signed-off-by: default avatarPavel Roskin <proski@gnu.org>
      c49eb5d1
  8. 17 Apr, 2009 4 commits
  9. 06 Mar, 2009 1 commit
  10. 24 Feb, 2009 4 commits
  11. 11 Feb, 2009 1 commit
  12. 06 Feb, 2009 1 commit
    • Daniel Mierswa's avatar
      use SBINDIR in install target of CRDA · 8e7bec8b
      Daniel Mierswa authored
      You supply the user with a chance to specify SBINDIR during make
      install, yet forgot to use it in one place at the install target. I
      attached a patch against trunk for crda.git which fixes that.
      8e7bec8b
  13. 02 Feb, 2009 2 commits
  14. 25 Jan, 2009 1 commit
  15. 24 Jan, 2009 2 commits
  16. 23 Jan, 2009 6 commits
  17. 18 Jan, 2009 1 commit
  18. 15 Jan, 2009 1 commit
  19. 22 Dec, 2008 2 commits
  20. 10 Dec, 2008 1 commit
  21. 04 Dec, 2008 1 commit
  22. 01 Dec, 2008 3 commits