On 07/19/2016 05:13 PM, Marcus Müller wrote:
Question arising: would you want the tag to contain the time when
general_work() was called, or rather the time of the first sample? Note
that sources should usually be designed to be blocking until there's
data available! That way, between entering general_work() and actually
having the first sample, a lot of time could pass. It might make a lot
more sense to let the block that knows the hardware handle tagging
itself, here.
Cheers,
Marcus
The idea is to tag when the first samples come off the hardware.
Indeed, if one had an N-channel "tag these when the samples show up"
block, it would likely be useless, since the scheduler will have
nicely arranged for all of the those channels to have something
useful to do the first time it calls work().
On 19.07.2016 23:00, Marcus D. Leech wrote:
On 07/19/2016 04:53 PM, Sylvain Munaut wrote:
I don't see why this has to be done by the scheduler, I'd do that in
the source, or even as a separate OOT that just inserts that tag.
Doing it in the source means modifying each source to insert, but,
maybe that's the right thing to do.
Cheers,
Sylvain
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
