I sent a PR with a doc fix for this. Interleaver uses this (since it does round-robin on the input). Also ofdm_chanest and header_payload_demux.
On Sun, Jan 21, 2018 at 1:54 PM, Jeff Long <willco...@gmail.com> wrote: > I sent a PR with a doc fix for this. Interleaver uses this (since it does > round-robin on the input). Also ofdm_chanest and header_payload_demux. > > On Sun, Jan 21, 2018 at 1:34 PM, Michael Dickens < > michael.dick...@ettus.com> wrote: > >> In theory, yes, you can call "produce()" for each output stream with a >> different number of items (or, the same), then return >> gr::block::WORK_CALLED_PRODUCE to tell the scheduler that produce was >> handled inside "general_work()". I know of no blocks that actually do this, >> but I don't know everything. That said, the GR runtime internals support my >> statement & hence this is worth trying. If you do try & succeed, please do >> let the list know. Cheers! - MLD >> >> On Sun, Jan 21, 2018, at 1:19 PM, Dave NotTelling wrote: >> > I found in the docs that general_work only supports outputting the same >> number of samples to each output port (https://github.com/gnuradio/g >> nuradio/blob/master/gnuradio-runtime/include/gnuradio/block.h#L47-L49) >> but the produce method seems to tell otherwise ( >> https://github.com/gnuradio/gnuradio/blob/master/gnuradio-r >> untime/include/gnuradio/block.h#L241-L248) and even has its own return >> flag for general_work. So, question is: can general_work output different >> numbers of samples to each output port by use of the produce() function and >> returning -2 in general_work? >> >> _______________________________________________ >> 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
