Re: inet_ntop( )

I wondered, why does inet_ntop() returns addresses in the format x:x:x:x:x:x:x.x.x.x ? This can be very annoying if that's not what you want. Is there another standard function, other than inet_ntop(), to do the same work ? I am going to guess you're asking why you're getting that format instead o

Re: regarding timeout/untimeout kernel functions

le to use it , so i just want to discuss it . thanks - pradeep Joseph M Link <[EMAIL PROTECTED]> wrote: If you're willing to take some precautions, you could run the timer code with select/usleep in a separate thread. However, since the callbacks would originate from that thread

Re: regarding timeout/untimeout kernel functions

If you're willing to take some precautions, you could run the timer code with select/usleep in a separate thread. However, since the callbacks would originate from that thread, you would need mutexes to protect any data that the function accesses that could also be accessed by the normal progr

xpt_schedule() and start interface context question.

Hello, I have been looking at the targ driver written by Nate Lawson and Justin Gibbs. I am seeing some access of user memory outside of what is obviously user context (the call to copyin and cam_periph_mapmem() by way of the targstart() interface). I am wondering how xpt_schedule() works and