Hi Jan,
Jan Wasserbauer wrote:
> 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.
This is the other thing. I would also like to implement another downcall
for telling the device driver the channel status (i.e. if there are VCs
running on the interface, current ppersistence etc.). This could
be used to drive some LEDs. This is especially important for use as
node system.
Another thing is interface setup - currently it�s possible to insert
a device driver module, up an interface and load the ax25 module after-
wards. Of cause this does not work since the DDI layer (which is
part of the ax25 module) was not notified of the up-event. I will try to
solve this stuff by using kmod for loading the ax25 module on demand.
As far as unifying configuration tools in concerned, I don�t think we
can get rid of seperate configuration tools completely. Just think of
for example the smdiag tool for soundmodem monitoring. Parameters as
ppersistence, baudrate, txdelay, txtail etc. should - however - really
be controlled by a AX.25 ioctl() propagating the information down to
the device driver by another downcall.
-- Jens
