On Mon, Sep 10, 2001 at 09:51:00PM +0200, Mark Santcroos wrote:
> Do you know the exact reason for this problem or can I help by exactly
> finding out what change of code causes this problems?

I deciced to track it down. I narrowed it down to the commit to pcic_pci.c

For that version it had the following relevant change:

<       DEVMETHOD(bus_setup_intr,       pcic_pci_setup_intr),
<       DEVMETHOD(bus_teardown_intr,    pcic_pci_teardown_intr),
>       DEVMETHOD(bus_setup_intr,       bus_generic_setup_intr),
>       DEVMETHOD(bus_teardown_intr,    bus_generic_teardown_intr),

I translated that back to the -current code and it comes to the following

diff /tmp/pccardd/current/pcic.c ./pcic.c
<       return (bus_generic_teardown_intr(dev, child, irq, cookie));
>       return 0;
diff /tmp/pccardd/current/pcic_pci.c ./pcic_pci.c
<       DEVMETHOD(bus_teardown_intr,    bus_generic_teardown_intr),
>       DEVMETHOD(bus_teardown_intr,    pcic_teardown_intr),

IOW, just skip the bus_generic_teardown_intr(). I called it a workaround,
cause I don't know if this is really a fix or a hack. (Don't know the code
well enough for that) 
However, my problems disappeared with this patch.

Please shine your light on this, or give a suggestion for a nice fix.
Anyway, the fix seems close (and trivial).



Mark Santcroos                          RIPE Network Coordination Centre
http://www.ripe.net/home/mark/          New Projects Group/TTM

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to