

Version1.0.0.26 Dated 02-05-2011
================================
- The Bugs 5867 5869 and 5855 are resolved with this release.

Bug 5867-
Changed the Tx and Rx path by using RemoveEntryList API to list manipulation whenever Completion routine or IssuBulkTrannsfer fails.By which we are made sure that the exact TCB and RCBs are get removed from the Linked lists.With this we are able to manage the TCBs and RCBs to be available all the time and make sure that the transmit and rececive path to go smoothly.

Bug 5859-
In between several Suspend-resume of the device we get IP assignement failure with the older version.The power management of driver is not properly handled earlier.

Bug 5855-
With the proper list manipulation and proper cancellation of pending request with USB we are able to avoid the data aborts.



Version1.0.0.25 Dated 18-04-2011
================================

- Fixed the bug 5867 which occured because of the shortage of Tcbs.The Tcbs when the bug occures are all stuck in the NdisPendingList which needs to be scheduled to send to USB host.Since all Tcbs pending in the NdisPendingList there are no Tcbs free to be scheduled hence the Shortage of Tcbs and eventually the failure of file transfer.We got this fixed by setting the event which removes the Tcb from NdisPendingList and processes it.

- Fixed the bug 5855.Upon completion of a read request (RCB transfer) with USB,in the completion routine we are popping the Rcb from the list(UsbPendingList) which have the Rcbs pending with the USB host and pushing the RCB to the USBCompletion List.Between this process we are getting some unknown invalid pointers in the UsbPendingList.So, whenever Halt been called,we try to cancel the TCBs and RCBs,then we are getting data abort which is nothing but accessing the invalid address.We took care while manipulating the lists to avoid data abort.


Version1.0.0.24 Dated 11-03-2011
================================

- Fixed the issue reported by the customer APK_PMB,which states that when ActiveSybc usb cable plug/unplup for multiple times the Data Aborts occuring.The actual reason for data aborts when debugged found to be the Sleep interval given in the fucntion call which reads from and writes to the the HIF registers.This function we are calling periodically to check the status of link and NDIS too will poll the link status with the every 2 sec interval which again uses this funtion.

- to fix this we removed the Sleep() API from the routine.


Version1.0.0.23 Dated 03-01-2011
================================

- Fixed the bug #5833.The zero length packet TCB was not updated properly in the linked list which contains TCBs pending with USB.


Version1.0.0.22 Dated 15-12-2010
================================

1.In the Version 1.0.0.21 to minimise the time taken for the driver to get unloadd properly we changed the architecture of the driver and removed the delay when driver unloads,which is now causing the data aborts when suspend-resume done.So in the version 21 we incorporated some delay again to make the driver get unload properly.


Version1.0.0.21 Dated 18-11-2010
================================

1.Version 1.0.0.21 minimises the time taken for the driver to get uninstalled properly.
  the bug #5803 solved with this release.




Version1.0.0.20
===============

1. This version does contain version 18 change i.e. support for MCS7832 added.

2. And version 19 change is excluded, i.e. the FILTER_TYPE_ALL_MULTICAST bit set in the packet filter is avoided.

3.The Ping(Bug #5784) as well as IP lease time(Bug #5785) expirations bugs resolved.The reason for these bugs is, the Multicast registers were not updated properly,due to which the ARP broadcast packets were not responded and the ip renew was not done at the proper interval.These are updated when we read back after wrtiing into the registers.




Version1.0.0.17
===============
 
Changes done:

-  Changed the TX and Rx completion routine paths code to support event based completion routines. With the earlier Tx and Rx completion routines doing post processing within the callback context, seeing that after some time Host Controller driver 
gets hung and further Tx and Rx completion routines are not being called even though requests are pending with Host Controller driver.

- Increased the delay while waiting for the Tx and Rx threads to terminate, in the unload path.




Version1.0.0.15
===============

Changes:
+++++++++++

As the NDIS periodic timer was fast enough to queue timer objects.
When we unplug the device,we were cancelling queued periodic timer object calling timer function.
so we were unable to cancel the set link status periodic timer.


Version 1.0.0.15 fixes this issue,when user unplugs device he sets "UsbCloseDevice" flag,
and we reset link status periodic timer in it's timer function itself.

Fixes the Bug Id 5656. 

Version1.0.0.14
===============
2:47 PM 1/9/2009

Changes:
+++++++++++
1.Fixes the Bug Id 5656:Customer Issue (APK-PMB):Link Up lead time for MCS7830 is greater than standard Ethernet controller.  
2.Current Version1.0.0.14 decreases the link-up time of MCS7830. 
3.This is done by having a NDIS timer in MCS7830 driver,that update the link status information every 500ms .