On 09/02/2010 01:46 PM, Eric Schneider wrote:
Oh cool! When was that implemented? I missed it...
http://old.nabble.com/UHD-Announcement---August-16th-2010-td29457066.html
I assume there is no problem with timeout = 0?
should be fine
Is the interface thread safe? read/write/recv_async?
On 09/02/2010 01:54 PM, Marc Epard wrote:
On Sep 2, 2010, at 12:23 PM, Josh Blum wrote:
See recv async message:
http://www.ettus.com/uhd_docs/doxygen/html/classuhd_1_1device.html#afe4ec312d71c669fbd86ce9a7d350605
And the async metadata:
http://www.ettus.com/uhd_docs/doxygen/html/structuhd_
On Sep 2, 2010, at 12:23 PM, Josh Blum wrote:
> See recv async message:
> http://www.ettus.com/uhd_docs/doxygen/html/classuhd_1_1device.html#afe4ec312d71c669fbd86ce9a7d350605
>
> And the async metadata:
> http://www.ettus.com/uhd_docs/doxygen/html/structuhd_1_1async__metadata__t.html
Thanks, J
Oh cool! When was that implemented? I missed it...
I assume there is no problem with timeout = 0?
Is the interface thread safe? read/write/recv_async?
--Eric
On Thu, 2010-09-02 at 13:23 -0400, Josh Blum wrote:
> See recv async message:
> http://www.ettus.com/uhd_docs/doxygen/html/classuhd_1_1d
See recv async message:
http://www.ettus.com/uhd_docs/doxygen/html/classuhd_1_1device.html#afe4ec312d71c669fbd86ce9a7d350605
And the async metadata:
http://www.ettus.com/uhd_docs/doxygen/html/structuhd_1_1async__metadata__t.html
-Josh
On 09/02/2010 12:58 PM, Marc Epard wrote:
With UHD, how
With UHD, how can I programmatically detect when transmit underruns have
occurred?
I see Us in the output both on the host and from the USRP2 serial port, but I
haven't spotted an API to test for this condition.
-Marc
___
Discuss-gnuradio mailing li
