============================
R E L E A S E N O T E S
============================
Broadcom xD Picture Card Driver
Copyright (c) 2009-2010 Broadcom Corporation
All rights reserved.
Version 1.0.0.10 - Jun 10, 2010
----------------------------------------
Bug Fix:
========
1. Problem:
Interrupt sharing may cause problem when resuming from
S3/S4.
Fix:
Changed the driver to verify power state after resuming.
Version 1.0.0.9 - Jun 10, 2010
----------------------------------------
Bug Fix:
========
1. Problem:
CQ#47941 CR-XD:Unplugging an XD card will cause a
blue screen during a file transfer
Fix:
Added code to support ungraceful removal during file IO.
Version 1.0.0.8 - Jun 08, 2010
----------------------------------------
Bug Fix:
========
1. Problem:
CQ#48063 CR_SD3.0_xD: BSOD occurs while formatting SD card
if xD driver is installed.
Cause:
The xD card reset event could interfere with the SD card's
operation.
Fix:
Changed the xD card detection logic such that it doesn't
affect the SD bus.
Version 1.0.0.7 - Jun 03, 2010
----------------------------------------
Bug Fix:
========
1. Problem:
Resuming from S3/S4 from VDISK mode may BSOD.
Fix:
Do not touch interrupt in VDKSK mode.
2. Problem:
A bug was introduced in previous version that the xD card
CIS string is not properly copied.
3. Problem:
Resume from S3/S4 on Win7 system would BSOD.
Casue:
The forced bus rescan causes side effect on some systems that
doesn't need the workaround. SCSIPORT would stuck the PNP
state transition which causes BCC_9f subcode 4.
Fix:
Removed the power management workaround implemented in v1.0.0.3.
4. Problem:
CQ48146 Aspen-CR-XD: Unable to Access XD device after resume from S3/S4.
Cause:
This is newly introduced while fixing other bugs. The driver would
mistakenly enable ECC and/or disable DMA access. It will make the access
to the media very slow and/or not able to access the media due to outstanding
ECC problem.
Fix:
Correct the driver so that it doesn't alter the setting incorrectly.
Known issues:
=============
1. Symptom:
The media may not be detected if inserted after resuming from S3/S4 on
some systems.
Cause:
A workaround for SCSIport power management is removed to address problem #3
in the bug fix list.
Workaround:
The media should be detected again if user go to device manager and perform
a "scan for new hardware".
Future action:
This problem will be fix in next release.
Version 1.0.0.5 - May 26, 2010
----------------------------------------
Bug Fix:
========
1. Problem:
CQ47933 CR-XD: The XD device will disappear after resuming
from s3/s4 during a file transfer.
Fix:
Finished power management code.
2. Problem:
CQ47934 CR-XD: The XD device will disappear from Windows
explorer after running the disable/enable test.
CQ47935 CR-XD: Unable to auto detect XD device after installing
the driver when the XD card is already plugged in
Cause:
The controller may or may not generate card insertion interrupt
when a xD card is inserted.
Fix:
Change the detection logic such that the driver to poll the card state
at initialization and resuming from S3, S4 mode.
Enhancements:
=============
1. Request:
Enhance the driver so that it handles the case where xD media is unpluged
in the middle of building FTL table.
2. Request:
Recover from some hardware access timeout gracefully.
Version 1.0.0.4 - May 19, 2010
----------------------------------------
Bug Fix:
=============
1. Request:
System may prompt to format the media even
the media has been formatted previously when
DMA is turned on.
Cause:
The shared memory is not aligned to DMA boundary
so that the chip may generate DMA interrupt prematurely
causing invalid data being read.
Change:
Force the shared memory align to DMA boundary.
Impact:
Notes:
2. Request:
Read Tail operation timeout if ECC mode is on.
Change:
Always clear enable ECC bit when reading tail.
Impact:
Notes:
Enhancements:
=============
1. Request:
Turn DMA on by default.
Change:
As requested.
Version 1.0.0.3 - May 18, 2010
----------------------------------------
Bug Fix:
=============
1. Request:
Virtual Disk may not suspend to S3 or S4.
Change:
Set the flags for storage device properly.
Impact:
Notes:
2. Request:
On some systems, scsi miniport may not get notification
when resuming from S3.
Change:
Force a bus rescan in the bus driver.
Impact:
Notes:
Version 1.0.0.2 - May 13, 2010
----------------------------------------
Enhancements:
=============
1. Request:
Single INF file to install both drivers.
Change:
Impact:
Notes:
2. Request:
Initial AMD64/X64 support.
Change:
Impact:
Notes:
3. Request:
Enabled virtual disk io to test UM functionality.
Change:
Impact:
Notes:
Restrictions + known issues (will be fixed in later versions):
==============================================================
1. Does not recover from hardware access timeout.
System will hang, BSOD when hardware access failure.
2. Does not support ECC.
3. DMA has to be disabled when building FTL mapping table.
On some system, FTL table may take more than 30 seconds
build. The media will not appear until the FTL table
is built.
4. No power management (sleep, resume ..)
5. Media may not be detected when the driver starts with
media inserted. To workaround this, one should insert
the media after the driver started or unplug and plug in
the media.
6. x86 only
7. Limited SCSI command emulation.
Version 1.0.0.0 - May 01, 2010
----------------------------------------
Enhancements:
=============
1. Request:
Initial release
Change:
Impact:
Notes:
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.