Hi Mike,
I tried your suggestion below, and for some reason its still assigning the
same interrupt (whichever one I pick) to both the network card and the
wavelan card, and interstingly enough even if I remove one of them, its
still trying to get a routeable interrupt and the wavelan still doesnt
work. Any way that I can get this thing to give me a straight interrupt
on all cards without trying to do funny irq routing?
Thanks
Andrew
On Sun, 5 Aug 2001, Mike Smith wrote:
> > Hi Mike, ok my pci->pcmcia bridge is in slot 0, my network card is in slot
> > 3, below are the dmesg outputs from both oldcard and newcard,
>
> Ok; this is different from the "linked" dmesg you were showing before,
> and what it's highlighting is the weakness in the algorithm that we use
> for picking an interrupt in the "I have no idea what is good" case.
>
> Try taking the "life is tough" loop in sys/i386/pci/pci_cfgreg.c
> :pci_cfgintr_virgin() and change it so that it just loops from 11 to 11,
> ie.
>
> for (i = 11; i < 12; i++) {
> ...
>
> I still haven't worked out a "good" way of dealing with this problem; the
> way we hand out device resources makes it difficult to know in advance
> which interrupts are good choices. 8(
>
> --
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also. But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view. [Dr. Fritz Todt]
> V I C T O R Y N O T V E N G E A N C E
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
