On Thu, Oct 23, 2008 at 05:52:18PM -0400, Ed Criscuolo wrote:
> Eric Blossom wrote:
>> On Thu, Oct 23, 2008 at 04:56:04PM -0400, Ed Criscuolo wrote:
> >
>>> At this point, I think I'll embed all the packet reading AND
>>> hdlc processing into a single source block with no flow
>>> inputs. This way
Eric Blossom wrote:
On Thu, Oct 23, 2008 at 04:56:04PM -0400, Ed Criscuolo wrote:
>
At this point, I think I'll embed all the packet reading AND
hdlc processing into a single source block with no flow
inputs. This way the block can check for packets on the TUN
device, read them, bitstuff and h
On Thu, Oct 23, 2008 at 04:56:04PM -0400, Ed Criscuolo wrote:
> Eric Blossom wrote:
>>
>> Ed,
>>
>> The problem is that you need to know when the output is about to
>> underrun, and only then insert flags.
>>
>> Is there any external reference clock or other way to tell when the
>> external stream
Eric Blossom wrote:
Ed,
The problem is that you need to know when the output is about to
underrun, and only then insert flags.
Is there any external reference clock or other way to tell when the
external stream needs data? In general, GR has no tie to an external
timebase, except indirectl
On Tue, Oct 21, 2008 at 11:01:51AM -0400, Ed Criscuolo wrote:
> I'm building a set of blocks to implement the HDLC link-layer
> functions for a spacecraft communication system.
> These blocks deal with IP packets from/to the stack on one side,
> and a bitstream to/from the modulator/demodulator on
I'm building a set of blocks to implement the HDLC link-layer
functions for a spacecraft communication system.
These blocks deal with IP packets from/to the stack on one side,
and a bitstream to/from the modulator/demodulator on the other side.
The receive block is already done and working. It ta
