summaryrefslogtreecommitdiffstats
path: root/sys/dev/mlx
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2003-08-09 21:05:54 +0000
committerimp <imp@FreeBSD.org>2003-08-09 21:05:54 +0000
commitc15bca94e03b98395856f1d67894314c38560989 (patch)
treeccaeb7d52c2985daf148ae68386bd5e9f6beec2d /sys/dev/mlx
parente21ea1cb1ed093b94c182384c779973b56867c14 (diff)
downloadFreeBSD-src-c15bca94e03b98395856f1d67894314c38560989.zip
FreeBSD-src-c15bca94e03b98395856f1d67894314c38560989.tar.gz
Add code to cope more with strange conditions after careful study of
the standard. 1) When the bridge tells us that we have a card that isn't recognized, we use the force register to force the CV_TEST to run. This test causes the bridge to re-evaluate the card. Once this re-evaluation process happens, we get a new interrupt that may say it is ready to process. We try this up to 20 times. Tests have shown that this appears to correctly reset the 'Unknown card type' problem that I saw on my Sony PCG-505TS. 2) Take a page from OLDCARD and always read the CSC register in the ISR. Some TI (and it seems maybe Ricoh) chipsets require this to behave properly. This work around appears to work due to some power management protocols that were improperly implemented. Maybe it can be removed when this driver supports the full PME# protocol described in the standards. 3) Minor additional debug printf when debugging is enabled. 4) Minor additional commentary for things that are obvious only after study. # I'm committing this from my Sony PCG-505TS using shared PCI interrupts # and NEWCARD, but there are some issues with the Ricoh bridge still, but # at least now I can boot with the card inserted and have it work.
Diffstat (limited to 'sys/dev/mlx')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud