Next-in-Thread Next Message

News PCMCIA driver release 3.1.16 

Forum: Announcements of PCMCIA driver updates
Date: 2000, Jun 23
From: David Hinds <>

I've done a fairly major update of the 3c575_cb driver, folding in most of the changes from Donald Becker's latest 3c59x release. I've fixed one old bug with 3CXFE575CT card initialization, where transmits would be "stuck" for 15-30 seconds. I still have a number of unresolved problem reports with this driver, with cards that seem to work fine in my hands. I think these problems will probably turn out to be with the low-level CardBus socket driver code rather than with the 3c575_cb driver, but they have been hard to track down. Some may also relate to undocumented differences between minor chipset revisions. There seem to be cases where several chipset product codes all have the same product name.

This release enables "PCI read prefetch" on Ricoh CardBus bridges. This significantly improves performance of system-to-card bus master operations; I have a report that this made a big difference for 100baseT transmit performance. Normally I would expect the BIOS to take care of this but it seems that can't be relied on.

Some Toshiba users have been reporting an "oops" at startup time with CardBus cards. The basic problem seems to be a Toshiba chipset quirk, that causes the bridge to register an "eject" event right after a card is first powered up. The result was a race between the insert and eject handlers. I've fixed the race to prevent the oops. I'm told that increasing the setup_time and vcc_settle parameters for the pcmcia_core module prevents the insert/eject/insert flipping.

This release also fixes some compatibility problems both with older 2.0.* kernels, and the latest 2.4.0-test1 kernels.

Next-in-Thread Next Message

Select this message: PCMCIA driver release 3.1.16

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.

If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination

If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages

Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

Members Subscribe No Admin Mode Show Frames Help for HyperNews at 1.10
[ Edit This Forum ]