cket?
>
> (And yes the timestamps are treated as uint32's.)
>
> Regards,
> /Ulrika
>
> --
> *From:* Tim Pearce [mailto:timothy.pea...@gmail.com]
> *Sent:* Thursday, February 18, 2010 9:35 PM
> *To:* Ulrika Uppman
> *Cc:* Discuss-gnurad
egards,
/Ulrika
From: Tim Pearce [mailto:timothy.pea...@gmail.com]
Sent: Thursday, February 18, 2010 9:35 PM
To: Ulrika Uppman
Cc: Discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Timestamp value
Ulrika,
I agree with how you think the timestamps are generated -- it seems to work for
me
Ulrika,
I agree with how you think the timestamps are generated -- it seems to work
for me that way anyway!
I did it with a custom source block that added the counter*decimation rate
after the first sample, the trap I fell into there is that (particuarly at
lower decimation rates) rx_*_handler()
Hi,
I wonder how the timestamps are being generated for each ethernet-packet sent
from the USRP2 to the host? My initial idea about how it works was that
timestamps are generated at 100MHz (same as the samples) and then the timestamp
associated with the first sample in an ethernet data packet wi
