Changes between Version 8 and Version 9 of Internal/AtherosDriverLimits

Timestamp:

Sep 14, 2006, 3:53:16 PM (18 years ago)

Author:

Gautam D. Bhanage

Comment:

—

Internal/AtherosDriverLimits

@@ -15 +15 @@
 == Limitations With the Virtual Device Declarations ==
  
- Each physical device on a Atheros card is able to support upto 4 virtual access points and a single station. The number of devices supported on the single physical device also depend on the order in which the devices are created. If a single station is defined on a physical device then no more virtual devices may be created on the same physical device. If  a virtual access point (master) is created on a physical device then upto a single station (with the nosbeacon – this flag will disable the use of the hardware beacon timers for the station mode operation of the device.) and upto a total of 3 more virtual access point may be defined on the same underlying physical device.
+ * Each physical device on a Atheros card is able to support upto 4 virtual access points and a single station. 
+ * The number of devices supported on the single physical device also depend on the order in which the devices are created. 
+ * If a single station is defined on a physical device then no more virtual devices may be created on the same physical device.
+ * If a virtual access point (master) is created on a physical device then upto a single station (with the nosbeacon – this flag will disable the use of the hardware beacon timers for the station mode operation of the device.) and upto a total of 3 more virtual access point may be defined on the same underlying physical device.
 
 
@@ -29 +32 @@
  * Smart script that detects the usage of the same physical interface for multiple (>1) virtual interfaces.
  * Checks the make of the driver on the node (Intel / Atheros).
- * Virtualization of Intel based cards yet to be determined, hence, creates the first requested virtual interface and replies with a polite error for the second request saying "device already in use, please use another device".
+ * Virtualization of Intel based cards yet to be determined, hence for intel based devices, creates the first requested virtual interface and replies with a polite error for the second request saying "device already in use, please use another device".
  * If card make is Atheros, do a constraint check on the number and type of virtual interfaces supported by the card.
  * On each interface creation request, check the number of interfaces already created for that physical interface and see if it is possible to create more by verification with a global interface-usage table.