On Fri, 31 Aug 2001, Roman Zippel wrote:
Hello,
> It should wait in parport_wait_event. Could you add some prints there?
> Interesting would be the timeout values. If everything goes ok,
> parport_wait_event should continue with down_interrutible, after
> parport_ieee1284_wakeup was called. The question is now whether we get
> to down_interruptable at all or if something else interrupts it before
> up() is called in parport_ieee1284_wakeup (e.g. a timeout).
Adding prints to wait_event :
printk("wait A");
if (!port->physport->cad->timeout)
return 1;
printk(" B");
init_timer (&timer);
timer.expires = jiffies + timeout;
timer.function = timeout_waiting_on_port;
port_from_cookie[port->number % PARPORT_MAX] = port;
timer.data = port->number;
add_timer (&timer);
ret = down_interruptible (&port->physport->ieee1284.irq);
printk(" %d", ret);
if (!del_timer (&timer) && !ret)
/* Timed out. */
ret = 1;
printk(" %d\n", ret);
return ret;
produces :
Sep 1 08:19:25 enigma kernel: parport0: Amiga built-in port using irq
Sep 1 08:19:25 enigma kernel: lp0: using parport0 (interrupt-driven).
Sep 1 08:19:26 enigma kernel: enable_irq(18) unbalanced
Sep 1 08:19:26 enigma kernel: wait A B 0 0
Sep 1 08:19:26 enigma kernel: wait A B 0 0
Sep 1 08:19:26 enigma kernel: wait A B 0 1
Sep 1 08:19:26 enigma last message repeated 8 times
Sep 1 08:19:27 enigma kernel: enable_irq(18) unbalanced
and bad printing.
I'll do similar to write_compat.
Ken.
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Sat Sep 01 2001 - 04:44:05 EDT