Let me be the first to congratulate you, Richard, and Jamie for all the
hard work you guys put in the software.
> Now, question is where should it go. That winmodem uses interrupts so
> little that it can be nicely done using polling+userspace with zero
> performance lost. Still it is device driver. Should it go into kernel?
> [Well, drivers/sound/modem would be cool :-)]
> Then, there's v34 stack. It is not written yet, but it will eventually
> get written. It needs sort of realtime guarantees. Should it go into
> kernel?
A pointer to the V34 work in progress is in order here:
http://www.enst.fr/~bellard/linmodem.html
IMHO your driver should go into the kernel as a sound variant like you
suggest, and then userland can talk to that driver via a generic
soundmodem interface.
Jeff
-- Custom driver development | Never worry about theory as long Open source programming | as the machinery does what it's | supposed to do. -- R. A. Heinlein- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/