Re: Synchronous board drivers

Jan Kasprzak (kas@informatics.muni.cz)
Sun, 4 Jul 1999 18:26:27 +0200

Alan Cox wrote:
: > I think real sync board driver should be as simple as possible, with
: > the rest done in generic driver. The hardware driver should just provide
: > routines to initialize the board and set parameters, send a HDLC frame,
: > handle an irq when a frame is received, etc.
:
: That was basically the idea of the Z85230 driver and the cisco/ppp layer.
: Someone is doing FR at the moment in the same way.
:
I agree with Krzysztof that sync board driver should be as simple
as possible, and syncppp.c (or whatever it will be named) should do
everything else (registering net device, switching link protocols, etc).

Then we probably should move from library approach (as in current
syncppp.c) to a mid-layer approach (register_hdlc_dev(), struct
hdlc_device_ops).

I can even imagine that syncppp.c (or its descendant) can do
a character device routines for the sync board (/dev/hdlcX).

: The "we ought to use pppd" case is quite valid. Its a 'when someone fixes it'
: task

I haven't looked at the async PPP code yet. What parts of the PPP
is done by the kernel and what by the pppd?

-Yenya

-- 
\ Jan "Yenya" Kasprzak <kas at fi.muni.cz>       http://www.fi.muni.cz/~kas/
\\ PGP: finger kas at aisa.fi.muni.cz   0D99A7FB206605D7 8B35FCDE05B18A5E //
\\\             Czech Linux Homepage:  http://www.linux.cz/              ///
The new code base has not stabilized enough yet for benchmarking. Be patient,
we'll be sure to delay NT5's release a bit, trust me...              (DaveM)


-
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/