Alan Cox a �crit :
> > We are developing an ethernet device driver and we have a problem when
> > using the interruptible_sleep_on or interruptible_sleep_on_timeout
> > functions. Our system hangs and we must reboot the PC.
> >
> > Did someone meet this problem ?
>
> Most network interface code is run out of process context so you cannot
> sleep
Do you have a solution for our problem ?
I explain the context. We have encapsulated two layers in our ethernet
driver and we communicate via RS232. When we receive an ethernet frame from
the TCP/IP stack, if we don't have a connexion, we have to do the connexion
first. In order to establish it, we send a connexion request and must wait
for the connexion confirm in the driver. After, we can send data (ethernet
frame).
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
