ray_cs.txt 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150
  1. September 21, 1999
  2. Copyright (c) 1998 Corey Thomas (corey@world.std.com)
  3. This file is the documentation for the Raylink Wireless LAN card driver for
  4. Linux. The Raylink wireless LAN card is a PCMCIA card which provides IEEE
  5. 802.11 compatible wireless network connectivity at 1 and 2 megabits/second.
  6. See http://www.raytheon.com/micro/raylink/ for more information on the Raylink
  7. card. This driver is in early development and does have bugs. See the known
  8. bugs and limitations at the end of this document for more information.
  9. This driver also works with WebGear's Aviator 2.4 and Aviator Pro
  10. wireless LAN cards.
  11. As of kernel 2.3.18, the ray_cs driver is part of the Linux kernel
  12. source. My web page for the development of ray_cs is at
  13. http://world.std.com/~corey/raylink.html and I can be emailed at
  14. corey@world.std.com
  15. The kernel driver is based on ray_cs-1.62.tgz
  16. The driver at my web page is intended to be used as an add on to
  17. David Hinds pcmcia package. All the command line parameters are
  18. available when compiled as a module. When built into the kernel, only
  19. the essid= string parameter is available via the kernel command line.
  20. This will change after the method of sorting out parameters for all
  21. the PCMCIA drivers is agreed upon. If you must have a built in driver
  22. with nondefault parameters, they can be edited in
  23. /usr/src/linux/drivers/net/pcmcia/ray_cs.c. Searching for module_param
  24. will find them all.
  25. Information on card services is available at:
  26. http://pcmcia-cs.sourceforge.net/
  27. Card services user programs are still required for PCMCIA devices.
  28. pcmcia-cs-3.1.1 or greater is required for the kernel version of
  29. the driver.
  30. Currently, ray_cs is not part of David Hinds card services package,
  31. so the following magic is required.
  32. At the end of the /etc/pcmcia/config.opts file, add the line:
  33. source ./ray_cs.opts
  34. This will make card services read the ray_cs.opts file
  35. when starting. Create the file /etc/pcmcia/ray_cs.opts containing the
  36. following:
  37. #### start of /etc/pcmcia/ray_cs.opts ###################
  38. # Configuration options for Raylink Wireless LAN PCMCIA card
  39. device "ray_cs"
  40. class "network" module "misc/ray_cs"
  41. card "RayLink PC Card WLAN Adapter"
  42. manfid 0x01a6, 0x0000
  43. bind "ray_cs"
  44. module "misc/ray_cs" opts ""
  45. #### end of /etc/pcmcia/ray_cs.opts #####################
  46. To join an existing network with
  47. different parameters, contact the network administrator for the
  48. configuration information, and edit /etc/pcmcia/ray_cs.opts.
  49. Add the parameters below between the empty quotes.
  50. Parameters for ray_cs driver which may be specified in ray_cs.opts:
  51. bc integer 0 = normal mode (802.11 timing)
  52. 1 = slow down inter frame timing to allow
  53. operation with older breezecom access
  54. points.
  55. beacon_period integer beacon period in Kilo-microseconds
  56. legal values = must be integer multiple
  57. of hop dwell
  58. default = 256
  59. country integer 1 = USA (default)
  60. 2 = Europe
  61. 3 = Japan
  62. 4 = Korea
  63. 5 = Spain
  64. 6 = France
  65. 7 = Israel
  66. 8 = Australia
  67. essid string ESS ID - network name to join
  68. string with maximum length of 32 chars
  69. default value = "ADHOC_ESSID"
  70. hop_dwell integer hop dwell time in Kilo-microseconds
  71. legal values = 16,32,64,128(default),256
  72. irq_mask integer linux standard 16 bit value 1bit/IRQ
  73. lsb is IRQ 0, bit 1 is IRQ 1 etc.
  74. Used to restrict choice of IRQ's to use.
  75. Recommended method for controlling
  76. interrupts is in /etc/pcmcia/config.opts
  77. net_type integer 0 (default) = adhoc network,
  78. 1 = infrastructure
  79. phy_addr string string containing new MAC address in
  80. hex, must start with x eg
  81. x00008f123456
  82. psm integer 0 = continuously active
  83. 1 = power save mode (not useful yet)
  84. pc_debug integer (0-5) larger values for more verbose
  85. logging. Replaces ray_debug.
  86. ray_debug integer Replaced with pc_debug
  87. ray_mem_speed integer defaults to 500
  88. sniffer integer 0 = not sniffer (default)
  89. 1 = sniffer which can be used to record all
  90. network traffic using tcpdump or similar,
  91. but no normal network use is allowed.
  92. translate integer 0 = no translation (encapsulate frames)
  93. 1 = translation (RFC1042/802.1)
  94. More on sniffer mode:
  95. tcpdump does not understand 802.11 headers, so it can't
  96. interpret the contents, but it can record to a file. This is only
  97. useful for debugging 802.11 lowlevel protocols that are not visible to
  98. linux. If you want to watch ftp xfers, or do similar things, you
  99. don't need to use sniffer mode. Also, some packet types are never
  100. sent up by the card, so you will never see them (ack, rts, cts, probe
  101. etc.) There is a simple program (showcap) included in the ray_cs
  102. package which parses the 802.11 headers.
  103. Known Problems and missing features
  104. Does not work with non x86
  105. Does not work with SMP
  106. Support for defragmenting frames is not yet debugged, and in
  107. fact is known to not work. I have never encountered a net set
  108. up to fragment, but still, it should be fixed.
  109. The ioctl support is incomplete. The hardware address cannot be set
  110. using ifconfig yet. If a different hardware address is needed, it may
  111. be set using the phy_addr parameter in ray_cs.opts. This requires
  112. a card insertion to take effect.