/**************** claimer ******************
** Copyright (C) 2003, 2010 ACX100 Open Source Project
** The contents of this file are subject to the Mozilla Public
** License Version 1.1 (the "License"); you may not use this file
** except in compliance with the License. You may obtain a copy of
** the License at http://www.mozilla.org/MPL/
** Software distributed under the License is distributed on an "AS
** IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
** implied. See the License for the specific language governing
** rights and limitations under the License.
** Alternatively, the contents of this file may be used under the
** terms of the GNU Public License version 2 (the "GPL"), in which
** case the provisions of the GPL are applicable instead of the
** above. If you wish to allow the use of your version of this file
** only under the terms of the GPL and not to allow others to use
** your version of this file under the MPL, indicate your decision
** by deleting the provisions above and replace them with the notice
** and other provisions required by the GPL. If you do not delete
** the provisions above, a recipient may use your version of this
** file under either the MPL or the GPL.
Inquiries regarding the ACX100 Open Source Project can be made directly to:
Support and Bug reports:
Please describe your wireless setup, manufacturer and type
(acx100/acx100usb/acx111?) of your hardware. Which firmware image(s)
are you using? If problem is reproducible, #define ACX_DEBUG 2
in acx_config.h and modprobe driver with debug=0xffff.
Post resulting kernel log (bzipped). It is large but very useful
for bug hunting. Try older versions of the driver.
=> See also the wiki
You should not supply firmware_dir= parameter anymore. Driver will try
to load the following images via hotplug (not from /usr/share/acx
directory as older driver did, hotplug firmware directory location
varies for different distros, try /lib/firmware or
'tiacxNNNcMM' (NNN=100/111, MM=radio module ID (in uppercase hex)):
combined firmware for specified chipset and radio.
Failing that, it will try to load images named 'tiacxNNN'
(main firmware for specified chipset) and 'tiacxNNNrMM' (corresponding
radio module). For example, my firmware is in file named 'tiacx111c16'.
Alternatively, I may remove it and use pair of files 'tiacx111' and
image is named 'tiacxNNNusbcMM'
=> See INSTALL file