> > If you have a smart firmware-driven PPP board, then wouldn't it be
> > doing the ppp negotiation itself, thus removing the need for pppd and
> > the kernel ppp driver? Wouldn't it look much more like an ethernet
>
> Yes. However two things apply here that are important
>
> 1. It may do PPP, but if I flip it to X.25 it may not do X.25, so the
> board itself needs a control of how it hands packets around.
>
> 2. I may want to be able to add a board specific ioctl to pick hardware
> (low cpu overhead) v software (multilink, cool feature set) PPP
If a board needs these kinds of controls, I would much prefer that
there is a way to get to it without going through the generic PPP
code. E.g. there could be a character device for the board which can
have its own set of ioctls for controlling the board. Or it could use
a file under /proc or something. I would rather not clutter up the
generic ppp code with stuff for low-level channel control.
With async ttys we already have this, since you can open /dev/ttyXX
and get an fd, set it to ppp line discipline, then do ppp ioctls on
it.
Paul.
-
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/