<?xml version="1.0" encoding="UTF-8"?>

<relnotes name="IrDA PRT">

  <purpose>

    PRT plugin to ESock Sockets Server, implements IrDA infrared stack.

  </purpose>

  <defect number="PDEF139836" title=".esk and .cmi files do not have header" revision="020">

    Added copyright headers

  </defect>

  <deliverystep number="1657" name="Remove IrDA" osproject="SymTB9.2" revision="001">

	  <preq number="2613" title="Remove IrDA"/>

  </deliverystep>

  <milestone project="GT0418" number="3.3"/>

  <defect number="DEF132889" title="[ONB Coverity] CHECKED_RETURN error in infra-red" revision="019">

    Removed the code causing a build warning

  </defect>

  <defect number="DEF129360" title="DEF130910: [Future OS Product] Build warnings in irda " revision="018">

    Removed the code causing a build warning

  </defect>

  <defect number="DEF130780" title="[Coverity]-MISSING_BREAK,REVERSE_INULL -infra-red/irda" revision="017">

    Failures corrected and prevented.

  </defect>

  <defect number="DEF129360" title="[Coverity]-RESOURCE_LEAK -infra-red/irda " revision="016">

    two places are change to avoid memory leak.

  </defect>

  <defect number="DEF129123" title="Memory Leak Introduced Into Usbman" revision="015">

    Memory leak also in IRDA. Removed two instances of memory leak.

  </defect>

  <defect number="DEF128204" title="errors in IM tagging in shortlink" revision="014">

    Correct the IM tagging.

  </defect>

  <defect number="DEF127257" title="[Coverity]-UNUSED_VALUE-infra-red/irda " revision="013">

	Changed return of 'CIrmux::NewIASServerSAPL' to void.

  </defect>

  <defect number="DEF127256" title="[Coverity]-SYMBIAN.CLEANUP_STACK-infra-red/irda" revision="012">

	Upgraded 'IrTranpUtil::HexOut' to improve the management of memory allocation failure and to take hex buffer length into account.

  </defect>

  <defect number="DEF124963" title="[Coverity]2 USE_AFTER_FREE failures in CIrdaNetDatabase" revision="011">

	Changed parameter to DisconnectIASServerSAP to be a reference. Set the returned parameter to NULL after deletion.

  </defect>

  <defect number="DEF125858" title="[coverity] - FORWARD_NULL - infra-red/irda" revision="010">

	Checked iSocket before dereferencing

  </defect>

  <defect number="DEF124962" title="[Coverity]FORWARD_NULL failure in CIrmux" revision="009">

	Fixed the issue returning NULL instead --lsap.

  </defect>

  <defect number="PDEF123075" title="Re-export irda.rh" revision="008">

    Re-export irda.rh as required again to be exported to \\epoc32\include, was added in the bld.inf file. also changed irda.rss to use a export level include. 

  </defect>

  <defect number="PDEF120827" title="KErrDisconnect Notification not raised" revision="007">

    IR stack send disconnect notification when it get disconnected

  </defect>

  <defect number="DEF106011" title="Ensure Shortlink files have correct IM tags" revision="006">

    Updated files to correct copyright dates

  </defect>

  <defect number="DEF106011" title="Ensure Shortlink files have correct IM tags" revision="005">

    Found that irda.rh was no longer required to be exported to \\epoc32\include, was there removed from the bld.inf file. Also changed irda.rss to use a user level include, as opposed to system level include for the irda.rh file and teh IM tag of publishedPartner was added

  </defect>

  <defect number="DEF101319" title="Filename case check failures in source build and test" revision="004">

    Corrected filenames to enable building of Symbian OS in Linux

  </defect>

  <defect number="DEF101971" title="Update with 8.1b changes for IrDA qualification" revision="003">

    Changes made as suggested by LPD to qualify IrDA stack.

  </defect>

  <defect number="INC100851" title="KNotifyDataAvailableSupported missing from IRCOMM's Caps()" revision="002">

    CIrCommPort now indicates that it supports the NotifyDataAvailable() method when queried for its communication capabilities.

  </defect>

  <defect number="PDEF100837" title="Conflicting discoveries in irda" revision="001">

    Stack now will complete its own discovery even if a remote device is performing a discovery too.

  </defect>

</relnotes>