NOTE: this page is for archival only, see the note at the end of the page.

Go back –> ath6kl

ath6kl todo

Cleanup items

  • typedef cleanup
  • fix checkpatch reported errors/warnings.
  • fix sparse reported errors/warnings.
  • remove THREAD_X support
  • dl list cleanpu
  • netbuf cleanup (skbuff should be used)
  • rearchitecture of debug architecture
  • cleanup of modparams (more than 50+ mod params)
  • cleanup of kernel config options (see below)
  • simplify htc/hif
  • remove kernel thread
  • cleanup semaphore and wait_event apis
  • cleanup of locking
  • replace macros,apis with linux specific APIs.
  • handle error codes properly
  • remove test cmd support (and add it back later)
  • too many header files and lot of duplicates... clean it up.
  • WLAN node optimization
  • sysfs cleanup
  • remove bluetooth driver
  • remove camel case
  • remove hungarian notation
  • line length fixes
  • remove #if 0 code
  • remove cplusplus definitions
  • flatten directory structure
  • remove exported symbols
  • remove ieee80211.h
  • use align macros (grep ~3)
  • replace wlan_ieee2freq() and wlan_freq2ieee()
  • clean up arEvent usage
  • clean up wmitimeout usage
  • convert arSem to mutex
  • remove unused/unneeded ifdefs
  • remove static variables, eg. sip in ar6000_target_failure()
  • remove all wext code and configs

Then an item is done, please mark it with strike through.

config cleanup

CONFIG_HOST_TCMD_SUPPORT

This requires some special firmware and will vary depending on the revision of the chipset.

  • AR6003_REV1_VERSION –> AR6003_REV1_TCMD_FIRMWARE_FILE

  • AR6003_REV2_VERSION –> AR6003_REV2_TCMD_FIRMWARE_FILE

It seems this does not actually affect the WMI API other firmware so why not just remove the ifdef and keep the code in place. The only use I see for the config option is that it enables a module parameter testmode which if set then it will load the test firmware. This can likely be kept for now, even for proper placement in the Linux kernel.

No autodetection of features

You can only build ath6kl for a static targeted chipset model. So for example you only build ath6kl to support a dual band or single band setup, plugging in a dual band chipset into an box where ath6kl was compiled into for single band support will yield with no dual band support. The same applies to Bluetooth support. ath6kl has some config options which only let you statically select if ath6kl is shipping as a combo with BT support, and you have a few vendor options for the chipsets. None of these options are automatically detected. All this needs to change, work is required with the firmware team to ensure we can automatically detect these features and the type of card we are using.

Random always set macros

This can be remove and the code that makes sense left in place.

ccflags-y += -DTCMD
ccflags-y += -DWAPI_ENABLE
ccflags-y += -DCHECKSUM_OFFLOAD
...
#if WIRELESS_EXT < 18

AP Mode support using cfg80211

No one is working on this yet.

WiFi Direct

No one is working on this yet


This is a static dump of the old wiki, taken after locking it in January 2015. The new wiki is at https://wireless.wiki.kernel.org/.
versions of this page: last, v110, v109, v108, v107, v106, v105, v104, v103, v102, v101, v100, v99, v98, v97, v96, v95, v94, v93, v92, v91, v90, v89, v88, v87, v86, v85, v84, v83, v82, v81, v80, v79, v78, v77, v76, v75, v74, v73, v72, v71, v70, v69, v68, v67, v66, v65, v64, v63, v62, v61, v60, v59, v58, v57, v56, v55, v54, v53, v52, v51, v50, v49, v48, v47, v46, v45, v44, v43, v42, v41, v40, v39, v38, v37, v36, v35, v34, v33, v32, v31, v30, v29, v28, v27, v26, v25, v24, v23, v22, v21, v20, v19, v18, v17, v16, v15, v14, v13, v12, v11, v10, v9, v8, v7, v6, v5, v4, v3, v2, v1