On Tue, 1 Feb 2000, Jens David wrote:
> > > We should start phase out "struct sockaddr_ax25" now, BTW. We're
> > > carrying this thing with us for too long now and I doubt any
> > > application still uses it. I don't know if it even works nowadays.
> > sockaddr_ax25 ?
> > Programs use full_sockaddr_ax25 but sockaddr_ax25 is part of it. You
> > mean removing it as a separate struct ?
> Thats exacty what I mean. The API (including but not limited to the socket
> interface) is far from being complete. Instead of caring about every possible
> combination of application and sub-revision API we should sit together and
> redesign that stuff once for all.
>
Yes thats right .. DG2FEF rewrote ax25 but has not touched API .. so it is
now a bit mess. Some values are not used by kernel etc.
I think it would be very nice to have also unified API for drivers. Now
many drivers have own configuration utilities which is not wery good.
Most of drivers just need irq/io/dma/number of channels (which in some
cases could be replaced by just com/lpt number).
Plus baudrate, half/full-duplex, txd etc. which should be urgently
replaced by one configuration utility since all drivers need that.
Jan
