Next-in-Thread Next Message

None The card is not the problem

Re: Question one last question (Jochen Kirsch)
Date: 2000, Apr 08
From: David Hinds <dhinds@pcmcia.sourceforge.org>

The tulip driver is not the problem.  The problem is with the Cardbus
bridge in your laptop, which is not delivering interrupts properly.

-- Dave

Messages Inline: 0 All Outline: 1 2 All

Question buggy cardbus bridge - consequence for other cards; workaround?

Re: None The card is not the problem (David Hinds)
Date: 2000, Apr 08
From: Jochen Kirsch cerise

Thank you for your answer, David.

I'm sorry bothering you again, but here are two other questions (which perhaps may be of some interest for others, too; and I don't know anybody else knowing the answer).

1) As the cardbus bridge in my laptop has obviously problems in delivering the interrupt properly, is the problem likely to appear with other network cards, too? I.e., only with 32bit cardbus cards or also with 16bit pc cards; of which type should my next card be?

2) Facing the fact that the d-link card works under windoze (windoze or the win driver (?) obviously not taking care of the delivery problems...), the following came to my mind: ok, you said that the driver is not the problem. I admit that, as long as one has "normal" hardware (cardbus bridge) that behaves correctly. Would it be theoretically possible to either modify the driver or the piece of code in any other program concerned with receiving the improperly delivered interrupt, so that the hardware bug is ignored?

Thanx.

Jochen Kirsch.

1. None I don't know by David Hinds, 2000, Apr 11
(_ None ok by Jochen Kirsch, 2000, Apr 12
The card is not the problem


Add Message to: "The card is not the problem"

Members Subscribe Admin Mode No Frames New Base Frame Help for HyperNews at pcmcia-cs.sourceforge.net 1.10