Re: [Discuss-gnuradio] how to test sse2 support using cmake
How about looking at the libvolk components and see how SSE is done and mimic? On Sep 17, 2012 12:51 AM, "Kyle Zhou" wrote: > I have a block which depends on sse2. I need to tell cmake to check if the > cpu support sse2 in order to determine if the sse2 acceleated version or a > generic version should be used. > This should be straight forward. However, I just cannot find an example > CMakeLists.txt to get me a quick start. > Any suggested readings? thanks > K Z > ___ > 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
Re: [Discuss-gnuradio] how to test sse2 support using cmake
Kyle, This sounds like a job for VOLK! Seriously, sounds like your block could benefit from all the nice housekeeping that Volk takes care of for you, including runtime auto-detection of platform support, conditional compiling based on compiler support, and alignment reporting. Consider including at least the crunchy SSE core in libvolk. Check out the Volk guide in the documentation for instructions. --n On Sun, Sep 16, 2012 at 9:50 PM, Kyle Zhou wrote: > I have a block which depends on sse2. I need to tell cmake to check if the > cpu support sse2 in order to determine if the sse2 acceleated version or a > generic version should be used. > This should be straight forward. However, I just cannot find an example > CMakeLists.txt to get me a quick start. > Any suggested readings? thanks > K Z > ___ > 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] Is there python code to automatically find USRP2 devices
Hi, Instead of specifying the device address in instantiating the usrp_resouce, I would like to let my python code to automatically detect the connected USRP and return the device addresses, just like the UHD_FIND_DEVICES does. After I get all the addresses of the connected USRPs, then the pyhon code can instantiate the instance of USRP_Source. I am wondering if there are existing code doing such kind of things. If no I will implement by myself. Best regards, -- Alex, *Dreams can come true – just believe.* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Is there python code to automatically find USRP2 devices
Just found the swig interface for this feature is already provided... On Mon, Sep 17, 2012 at 5:32 PM, Alex Zhang wrote: > Hi, > > Instead of specifying the device address in instantiating the > usrp_resouce, I would like to let my python code to automatically detect > the connected USRP and return the device addresses, just like the > UHD_FIND_DEVICES does. After I get all the addresses of the connected > USRPs, then the pyhon code can instantiate the instance of USRP_Source. > I am wondering if there are existing code doing such kind of things. If no > I will implement by myself. > > Best regards, > > -- > > Alex, > *Dreams can come true – just believe.* > > -- Alex, *Dreams can come true – just believe.* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Explanation about gr0
When we run tunnel.py we set gr0 interface as "sudo gr0 192.168.200.1". As per my understanding ,in tunnel.py internally maintains routing table like in NAT which has entry name as gr0 with mapping of USRP IP address to gr0 IP address at network layer.So is my understanding correct? *and If I want to change or modify interface gr0 ,In what part of code I should look?* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP on Switch
Hi all i have 2 USRP N210 connected via switch i want to make cognitive network on USRP's, for this i need multiple USRP's connection, i implemented 2X MIMO connection but there is allot of delay on slave USRP. software specs : linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.002-34-stable -- -- UHD Device 0 -- Device Address: type: usrp2 addr: 192.168.10.3 name: serial: E1R12VBNW -- -- UHD Device 1 -- Device Address: type: usrp2 addr: 192.168.10.2 name: serial: E1R12VCNW Dose any one know how to configure UHD sink block for multiple USRP's connection; i have got fallowing error... Error : Using Volk machine: sse4_2_32 Registered event listener change listener: true LSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSL Thanks Regards Muhammad Junaid m_junaid0...@yahoo.com http://junaidmuhammad.webs.com/___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP on Switch
> Dose any one know how to configure UHD sink block for multiple USRP's > connection; > > i have got fallowing error... > > Error : > > Using Volk machine: sse4_2_32 > Registered event listener change listener: true > LSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSLSSL > S = sequence error or dropped transmit packet, L = late transmit packet However, the FPGA could also interpret junk packets as being late or sequence errors as well. So it depends on what is really happening. Switches can sometimes be problematic. I have have very good luck with those little blue netgear switches. Can I recommend: 1) Ensure you can successfully use one USRP with the switch 2) Ensure the switch is 1 gigE supporting (obviously) 3) Also make sure that total bandwidth < 1gigE, because 2 USRP N210 at full rate can exceed gigE bandwidth easily -josh > Thanks > > Regards > Muhammad Junaid > m_junaid0...@yahoo.com > http://junaidmuhammad.webs.com/ > > > > ___ > 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
Re: [Discuss-gnuradio] Explanation about gr0
On 09/17/2012 08:58 PM, usrp n210 wrote: > When we run tunnel.py we set gr0 interface as "sudo gr0 192.168.200.1". > As per my understanding ,in tunnel.py internally maintains routing table > like in NAT which has entry name as gr0 with mapping of tunnely.py just opens a virtual ethernet interface. In the place of an ethernet card, the tunnel.py application handles the inbound and outbound ethernet traffic for this virtual interface. The inbound and outbound packets interface directly with a packet framer and packet correlation. Its so simple like that, there is no NAT involved. > USRP IP address to gr0 IP address at network layer.So is my understanding > correct? The N120 interfaces with the PC using a network interface. But, hey, some USRPs use USB. Basically, the fact that the USRP has an IP address has zero relation to the IP addresses in the tunnel.py example. > *and If I want to change or modify interface gr0 ,In what part of code I > should look?* > You can read more about tun/tap: https://en.wikipedia.org/wiki/TUN/TAP If you are really trying to get into gnuradio. gnuradio-companion is really the place to start. All of the modulation and framer blocks in the tunnel.py example are in GRC with the GUI environment and all. -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
