From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> I suspect that bit can be fixed if need be. Its nice to keep a constant
> naming between cisco/ppp modes. cisco/ppp autodetect is also possible and
would
> be rather nice to support
I can't see getting around moving the net device allocation out of each
low level driver and into the layer above it. That removes
duplicate code and allows syncppp to do the right thing (allocate it itself
for cisco or allow ppp_generic.c do it for PPP). This would make
net device naming consistancy easier.
The low level drivers should not need any awareness of the net device
(possibly other than suggesting a name) as all they do is send and
receive frames.
The rest of the syncppp API should be (re)usable.
> Assuming this is a 'when 2.5 starts' discussion I'd like initially to keep
the
> syncppp api is but the pppd code going via generic ppp - and yes it would
> break configs.
>
> Clearly thats not 2.4 acceptable
Agreed, but it's a good time to call the cats to the herding pen.
Paul Fulghum paulkf@microgate.com
Microgate Corporation http://www.microgate.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 31 2001 - 21:00:20 EST