3 .\" Dr. Duncan McLennan Barclay, dmlb@ragnet.demon.co.uk.
5 .\" All rights reserved.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. Neither the name of the author nor the names of any co-contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY DUNCAN BARCLAY AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL DUNCAN BARCLAY OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
31 .\" $FreeBSD: src/share/man/man4/man4.i386/ray.4,v 1.8.2.1 2001/10/23 07:25:48 ru Exp $
38 .Nd Raytheon Raylink/Webgear Aviator PCCard driver
44 driver provides support for
45 .Tn "Raytheon Raylink"
46 adapters (commonly available as
47 .Tn "Webgear Aviator" ,
48 .Tn "Webgear Aviator Pro"
54 cards is a frequency hopping PHY with an
57 style MAC that interacts with the host using shared memory and mailboxes.
61 driver currently supports ad-hoc operation mode and the
64 Infrastructure mode, interworking with
65 .Tn "Windows 2000" Ns / Ns Tn Linux Ns / Ns Nx ,
66 .Tn "Raylink PC Cards"
69 is rudimentary and in active development.
72 driver currently encapsulates all IP and ARP traffic as
78 Other translations will be forthcoming as needed.
80 selectable between 0.5Mbps, 1Mbp , 1.5Mbps or 2Mbps all with auto fallback.
84 driver configures the card for ad-hoc operation.
86 stations can communicate amongst each other without the aid of an access
88 To join a managed service set, the driver must be set for infrastructure mode
93 There are two known firmware versions; version 4 and version 5.
94 Version 4 firmware was shipped on the orignal
95 .Tn "Webgear Aviators"
104 .Tn "Raylink PC Cards"
106 Version 4 is not likely to be 100%
109 compliant - version 5 should be.
111 For more information on configuring this device, see
116 The following messages occur when there are problems
117 setting up the memory mapped buffers due to nits in
120 .It "ray?: pccardd did not map CM - giving up"
123 section and contact the author for help enclosing a copy
126 This message only occurs on 3.x systems.
127 .It "ray?: fixing up CM ..."
128 .It "ray?: fixing up AM ..."
129 The driver is fixing up PCCard memory management after mis-configuration
136 On 4.x and -current systems the following messages can occur when the
137 memory mapped buffers are set up.
138 .It "ray?: allocated common memory:"
139 .It ". start 0xd0000 count 0xc0000 flags 0x40"
141 .It "ray?: allocated attribute memory:"
142 .It ". start 0xdc000 count 0x1000 flags 0x50"
144 .It "ray?: allocated irq:"
145 .It ". start 0x9 count 0x1"
147 .It "ray?: Cannot allocate attribute memory"
148 .It "ray?: Cannot allocate common memory"
149 .It "ray?: Cannot allocate irq"
150 .It "ray?: Failed to setup irq"
151 .It "ray?: CARD_SET_MEMORY_OFFSET returned 0x??"
152 .It "ray?: CARD_SET_RES_FLAGS returned 0x??"
155 section and contact the author for help enclosing a copy
162 If the kernel is booted with the verbose flag turned on then the
163 extra information is printed when the driver is probed.
164 These messages are also seen when the
165 .Dv RAY_DBG_BOOTPARAM
168 option is turned on, as is the case for all existing
169 versions of the driver.
170 .It "ray?: memory start 0x???? count 0x???? flags 0x???? offset 0x????"
171 Description of memory map settings on entry to the driver.
172 .It "ray?: irq start 0x???? count 0x????"
173 Description of irq settings on entry to the driver (only on 4.1 and
177 On start-up the driver will report hardware failures thus:
179 .It "ray?: card failed self test: status 0x??<???>"
180 The card failed to come ready after it was plugged in to the PCCard
182 The most common cause of this message is incorrect PCCard memory
183 management (indicated by a status of 0xff or 0x55).
184 Bent cards might say that the receiver calibration failed.
185 If you are brave enough removing the
186 base of the case can resurrect cards (no warranties etc.).
187 .It "ray?: unsupported firmware version 0x??"
189 Contact the author for help enclosing a copy
194 The following messages are enabled using the
199 .It "ray?: cannot transmit - not running"
200 A packet was ready for transmission but the NIC is not connected to a
202 May occur when removing the PCCard.
203 .It "ray?: cannot transmit - no network"
204 The wireless NIC has roamed from an access point and not connected with a new
206 .It "ray?: cannot transmit - ECF busy"
207 The controller firmware was busy when a packet was about to be sent out.
208 It will be retried automatically.
209 .It "ray?: mbuf too long ??"
210 Should never happen, and if it does represents something wrong in the
211 generic ethernet driver in the kernel.
212 .It "ray?: could not pullup ether"
213 Problem with re-aligning mbufs.
214 Very unlikely to happen.
215 .It "ray?: unknown framing type ??"
216 An impossible error - mail the author.
217 .It "ray?: could not translate packet"
218 An error occured when trying to re-frame a packet for transmission.
219 .It "ray?: ECF busy, dropping packet"
220 The NIC was busy just before a packet was to be transmitted.
221 .It "ray?: tx completed but status is fail"
222 Typically associated with transmissions to out of range NICs.
223 .It "ray?: packet too big or too small"
224 A received packet was impossibly small or too large to fit into an mbuf.
225 .It "ray?: MGETHDR failed"
226 The driver could not get a mbuf to store a received packet into.
229 in your kernel configuration.
230 .It "ray?: MCLGET failed"
231 The driver could not get a mbuf to store a received packet into.
234 in your kernel configuration.
235 .It "ray?: bad length current 0x?? pktlen 0x??"
236 The lengths of a fragmented packet were inconsistent.
237 .It "ray?: bad rcs index 0x??"
238 The index of the buffer used for part of a fragmented packet is
239 outside of the usable range.
240 .It "ray?: header not version 0 fc0 0x??"
244 packet had an unkown header type.
245 Represents link corruption or non standard nodes in the network.
246 .It "ray?: unknown packet fc0 0x??"
250 packet type is unknown.
251 Represents link corruption or non standard nodes in the network.
252 .It "ray?: reserved DATA packet subtype 0x??"
256 data packet has a reserved (i.e. not allowed) subtype.
257 Represents link corruption or non standard nodes in the network.
258 .It "ray?: MGT TODS/FROMDS wrong fc1 0x??"
262 management packet had a malformed header.
263 Represents link corruption or non standard nodes in the network.
264 .It "ray?: unexpected MGT packet subtype 0x??"
268 management packet was of a subtype that the NIC
269 should have processed.
270 Benign, but might represent buggy firmware.
271 .It "ray?: reserved MGT packet subtype 0x??"
275 management packet has a reserved (i.e. not allowed)
277 Represents link corruption or non standard nodes in the network.
278 .It "ray?: open system authentication request"
279 Self explanatory and for testing
282 .It "ray?: authentication failed with status ??"
283 Self explanatory and currently represents a bug as the driver never
284 requests authentication.
285 .It "ray?: shared key authentication request"
286 Self explanatory and for testing
289 .It "ray?: reserved authentication subtype 0x??"
290 An authentication request has been received for a reserved (i.e. not allowed)
292 Represents link corruption or non standard nodes in the network.
293 .It "ray?: CTL TODS/FROMDS wrong fc1 0x??"
297 management packet had a malformed header.
298 Represents link corruption or non standard nodes in the network.
299 .It "ray?: unexpected CTL packet subtype 0x??"
303 control packet was of a subtype that the NIC
304 should have processed.
305 Benign, but might represent buggy firmware.
306 .It "ray?: reserved CTL packet subtype 0x??"
310 control packet has a reserved (i.e. not allowed)
312 Represents link corruption or non standard nodes in the network.
313 .It "ray?: bad ccs index 0x??"
314 The NIC has generated an interrupt with an incorrect control block.
315 .It "ray?: unexpected UPDATE_APM"
316 .It "ray?: unexpected TEST_MEM"
317 .It "ray?: unexpected SHUTDOWN"
318 .It "ray?: unexpected DUMP_MEM"
319 .It "ray?: unexpected START_TIMER"
320 The NIC has generated an interrupt signalling that
321 the indicated command has completed.
322 At present these commands are never
323 issued by the driver, so they represent firmware/hardware/driver bugs.
324 .It "ray?: unknown command 0x??"
325 The NIC has generated an interrupt for an unknown command completion.
326 Represents firmware/hardware/driver bugs.
327 .It "ray?: unexpected JAPAN_CALL_SIGNAL"
328 The NIC has generated an interrupt with a control block requesting
329 processing of a packet that is only ever used in Japanese RCR
331 Represents firmware/hardware/driver bugs unless you
332 are trying to certify the NICs in Japan (in which case you would have to
333 of modified the driver and this manual is out of date).
335 The controller firmware was busy when a command was about to be issued.
336 If the driver spins for too long then it will panic.
340 .It "ray?: freeing free ccs 0x??"
341 Benign warning that may occur when the NIC is ejected.
352 device driver first appeared in
356 Early versions of this
358 driver were a port of the
361 .An "Christian E. Hopps" .
364 .An Duncan Barclay Aq dmlb@FreeBSD.org ,
369 Infra-structure mode is not supported yet.
370 The driver is likely to panic if it is set into this mode.
371 Testers are encouraged to contact the
376 has a small problem managing and setting up the correct memory maps.
377 However, this driver should reset the
378 memory maps correctly - it works around
380 (where it reads the CIS for common memory, sets it all up
381 and then throws it all away assuming the card is an
384 Note that this could be dangerous (because it doesn't interact with
386 if you use other memory mapped cards at the same time or have
387 SCSI cards with on-board BIOS.
389 More encapsulations and translations could be supported, but they have
390 little value unless someone can demonstrate that the
392 cards will communicate with other manufacturers cards.
397 compliant, but version 5 is.
401 machines ensure that the
404 creates the BSS/IBSS.
406 The driver currently panics on some errors that it should recover from.
407 These will be removed RSN.