blob: 75c279f268ae74ef58ea904230aa045ffdaf2e9c [file] [log] [blame]
Henk de Groot68c0bdf2009-09-27 11:12:52 +02001/*******************************************************************************
2 * Agere Systems Inc.
3 * Wireless device driver for Linux (wlags49).
4 *
5 * Copyright (c) 1998-2003 Agere Systems Inc.
6 * All rights reserved.
7 * http://www.agere.com
8 *
9 * Initially developed by TriplePoint, Inc.
10 * http://www.triplepoint.com
11 *
12 *------------------------------------------------------------------------------
13 *
14 * This file contains DHF configuration info.
15 *
16 *------------------------------------------------------------------------------
17 *
18 * SOFTWARE LICENSE
19 *
20 * This software is provided subject to the following terms and conditions,
21 * which you should read carefully before using the software. Using this
22 * software indicates your acceptance of these terms and conditions. If you do
23 * not agree with these terms and conditions, do not use the software.
24 *
Ruslan Pisarevfa519292010-03-20 09:36:15 +020025 * Copyright (c) 2003 Agere Systems Inc.
Henk de Groot68c0bdf2009-09-27 11:12:52 +020026 * All rights reserved.
27 *
28 * Redistribution and use in source or binary forms, with or without
29 * modifications, are permitted provided that the following conditions are met:
30 *
31 * . Redistributions of source code must retain the above copyright notice, this
32 * list of conditions and the following Disclaimer as comments in the code as
33 * well as in the documentation and/or other materials provided with the
34 * distribution.
35 *
36 * . Redistributions in binary form must reproduce the above copyright notice,
37 * this list of conditions and the following Disclaimer in the documentation
38 * and/or other materials provided with the distribution.
39 *
40 * . Neither the name of Agere Systems Inc. nor the names of the contributors
41 * may be used to endorse or promote products derived from this software
42 * without specific prior written permission.
43 *
44 * Disclaimer
45 *
46 * THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,
47 * INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT AND THE IMPLIED WARRANTIES OF
48 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. ANY
49 * USE, MODIFICATION OR DISTRIBUTION OF THIS SOFTWARE IS SOLELY AT THE USERS OWN
50 * RISK. IN NO EVENT SHALL AGERE SYSTEMS INC. OR CONTRIBUTORS BE LIABLE FOR ANY
51 * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
52 * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
53 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
54 * ON ANY THEORY OF LIABILITY, INCLUDING, BUT NOT LIMITED TO, CONTRACT, STRICT
55 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
56 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
57 * DAMAGE.
58 *
59 ******************************************************************************/
60
Henk de Groot68c0bdf2009-09-27 11:12:52 +020061#ifndef DHFCFG_H
62#define DHFCFG_H
63/*-----------------------------------------------------------------------------
64 * File DHFCFG.H
65 *
66 * Contents: #defines for the DHF module
67 *
68 * Comments:
69 * Some combinations of the #defines in this file are illegal (as noted below).
70 * If an illegal combinations of #defines is specified a compile error is
71 * generated. See document DHFUG.DOC for more information.
72 *
73 * Author: John Meertens
74 * Date: 11-01-2000
75 *
76 * Change history:
77 *---------------------------------------------------------------------------*/
78
79
Ruslan Pisarevfa519292010-03-20 09:36:15 +020080/* Define DHF_WCI if you want to use the WCI to access the ORiNOCO card.
81 Define DHF_UIL if you want to use the UIL to access the ORiNOCO card.
82 You must define either DHF_WCI or DHF_UIL. If neither of the two is defined
83 or both a compile error is generated. */
Henk de Groot68c0bdf2009-09-27 11:12:52 +020084#define DHF_WCI
Ruslan Pisarevfa519292010-03-20 09:36:15 +020085/* !!!#define DHF_UIL */
Henk de Groot68c0bdf2009-09-27 11:12:52 +020086
Ruslan Pisarevfa519292010-03-20 09:36:15 +020087/* Define DHF_BIG_ENDIAN if you are working on a big endian platform.
88 Define DHF_LITTLE_ENDIAN if you are working on a little endian platform.
89 You must define either DHF_BIG_ENDIAN or DHF_LITTLE_ENDIAN. If neither of
90 the two is defined or both a compile error is generated. */
Henk de Groot68c0bdf2009-09-27 11:12:52 +020091#ifdef USE_BIG_ENDIAN
92#define DHF_BIG_ENDIAN
93#else
94#define DHF_LITTLE_ENDIAN
95#endif /* USE_BIG_ENDIAN */
96
Ruslan Pisarevfa519292010-03-20 09:36:15 +020097/* Define DHF_WIN if you are working on Windows platform.
98 Define DHF_DOS if you are working on DOS.
99 You must define either DHF_WIN or DHF_DOS. If neither of
100 the two is defined or both a compile error is generated.
101 !!!#define DHF_WIN
102 !!!#define DHF_DOS */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200103
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200104/* Define if you want the DHF to users. Not defining DHF_GET_RES_MSG
105 leads to a decrease in code size as message strings are not included.
106 !!!#define DHF_GET_RES_MSG */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200107
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200108/* Linux driver specific
109 Prevent inclusion of stdlib.h and string.h */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200110#define _INC_STDLIB
111#define _INC_STRING
112
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200113/*-----------------------------------------------------------------------------
114 Define one or more of the following DSF #defines if you want to implement
115 the related DSF-function. Function dsf_callback must allways be implemented.
116 See file DHF.H for prototypes of the functions. */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200117
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200118/* Define DSF_ALLOC if you want to manage memory allocation and de-allocation
119 for the DHF. If DSF_ALLOC is defined you must implement dsf_alloc and dsf_free.
120 !!!#define DSF_ALLOC */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200121
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200122/* Define DSF_CONFIRM if you want the DHF to ask the user for confirmation in a
123 number of situations. If DSF_CONFIRM is defined you must implement dsf_confirm.
124 Not defining DSF_CONFIRM leads to a decrease in code size as confirmation
125 strings are not included.
126 !!!#define DSF_CONFIRM */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200127
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200128/* Define DSF_DEBUG_MESSAGE if you want debug messages added to your output.
129 If you define DSF_DEBUG_MESSAGE then you must implement function
130 dsf_debug_message.
131 #define DSF_DEBUG_MESSAGE */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200132
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200133/* Define DSF_ASSERT if you want asserts to be activated.
134 If you define DSF_ASSERT then you must implement function dsf_assert.
135 #define DBG 1
136 #define DSF_ASSERT */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200137
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200138/* Define DSF_DBWIN if you want asserts and debug messages to be send to a debug
139 window like SOFTICE or DebugView from SysInternals.
140 !!!#define DSF_DBWIN
141 !!! Not implemented yet! */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200142
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200143/* Define DSF_VOLATILE_ONLY if you only wants to use valatile functions
144 This is a typical setting for a AP and a driver. */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200145#define DSF_VOLATILE_ONLY
146
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200147/* Define DSF_HERMESII if you want to use the DHF for the Hermes-II */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200148#ifdef HERMES2
149#define DSF_HERMESII
150#else
151#undef DSF_HERMESII
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200152#endif /* HERMES2 */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200153
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200154/* Define DSF_BINARY_FILE if you want to use the DHF in combination with
155 reading the Firmware from a separate binary file.
156 !!!#define DSF_BINARY_FILE */
Henk de Groot68c0bdf2009-09-27 11:12:52 +0200157
Ruslan Pisarevfa519292010-03-20 09:36:15 +0200158#endif /* DHFCFG_H */