While playing around with hdlcdrv I came across two problems:
Before arbitration was called by driver and when higher level decided to
transmit driver immediately keyed PTT. Now driver and DDI have separate
timers which results in DDI deciding to transmit BUT driver keying PTT
with some delay when driver gets its own interrupt.
In case of BayCom serial driver its interrupt is called in 10ms
intervals. So in the worst case we might have abt. 10ms delay before
actually keying PTT. I'm not sure how big issue that is but we are
needlesly increasing collision probability.
So question is how big issue that is .. (ie. whether we should implement
some downcall from hdlc to hw-driver to start TX)
I put some printk in ser12fdx driver to see how often that happens ..
Second problem is what should driver do when it receives new data
while sending txtail. Since new ax25 is designed that driver just sends
what it gets from higher level it seems obvious it should send new data
and restart txtail. But shouldn't there be some flag so that does not
happen ?
Jan
