Re: [Discuss-gnuradio] SWIG compilation speedup!
2007/1/13, Johnathan Corgan [EMAIL PROTECTED]: On Sat, 2007-01-13 at 16:12 +1030, Berndt Josef Wulf wrote: I can't see the point for doing so. I don't care if its takes me 15 minutes or 30 minutes to compile all GNU Radio. The biggest improvement isn't the compile time, it's the fact that the memory working set for g++ when compiling the previous gnuradio_swig_python.cc file was 650 MB. This would cause massive swap thrashing on machines with say, 512 MB of RAM, or less, and drive the compilation time up to potentially hours. This is great! I have a fairly new machine with 1G ram and a dual core AMD cpu, and compiling GNU Radio used to bring the computer to its knees :), so this is a great improvement. It is also good news as I intend to run GNU Radio on my EKIFA single board computer, which only has 128MB of RAM. -- Trond Danielsen ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] tx_empty continued
After seeing Matt Ettus' and Eric Blossom's responses regarding fixing the transmitter to keep it from repeating the last sample seen and ramp down the value to zero and am left unsure what is the best place to make this modification. I suppose since this is Matt Ettus' baby, we should go with his idea? Has either of you made the modification or shall I make another attempt? I'll be happy to try, and have some ideas, but wouldn't mind any additional input before proceeding. Thanks again for all of your time! -- View this message in context: http://www.nabble.com/tx_empty-continued-tf3014911.html#a8372396 Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] SWIG compilation speedup!
I just got the USRP running with an EFIKA board and OSSIE SCA. I'm using the usrp-0.12 tarball. I had to use a USB2.0 controller in the PCI slot to work around the usrp USB full speed problems I am having. I took a quick look at using openembedded to build gnu radio. Thet already support most of the required dependencies, but I noticed fftw is missing. When I am bored (heh) I'll see about adding fftw and seeing if I can get gnu radio to build in cross environment. Philip On 1/15/07, Trond Danielsen [EMAIL PROTECTED] wrote: 2007/1/13, Johnathan Corgan [EMAIL PROTECTED]: On Sat, 2007-01-13 at 16:12 +1030, Berndt Josef Wulf wrote: I can't see the point for doing so. I don't care if its takes me 15 minutes or 30 minutes to compile all GNU Radio. The biggest improvement isn't the compile time, it's the fact that the memory working set for g++ when compiling the previous gnuradio_swig_python.cc file was 650 MB. This would cause massive swap thrashing on machines with say, 512 MB of RAM, or less, and drive the compilation time up to potentially hours. This is great! I have a fairly new machine with 1G ram and a dual core AMD cpu, and compiling GNU Radio used to bring the computer to its knees :), so this is a great improvement. It is also good news as I intend to run GNU Radio on my EKIFA single board computer, which only has 128MB of RAM. -- Trond Danielsen ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] SWIG compilation speedup!
On Mon, Jan 15, 2007 at 10:19:19AM +0100, Trond Danielsen wrote: 2007/1/13, Johnathan Corgan [EMAIL PROTECTED]: On Sat, 2007-01-13 at 16:12 +1030, Berndt Josef Wulf wrote: I can't see the point for doing so. I don't care if its takes me 15 minutes or 30 minutes to compile all GNU Radio. The biggest improvement isn't the compile time, it's the fact that the memory working set for g++ when compiling the previous gnuradio_swig_python.cc file was 650 MB. This would cause massive swap thrashing on machines with say, 512 MB of RAM, or less, and drive the compilation time up to potentially hours. This is great! I have a fairly new machine with 1G ram and a dual core AMD cpu, and compiling GNU Radio used to bring the computer to its knees :), so this is a great improvement. Glad to hear that it's working for you! It is also good news as I intend to run GNU Radio on my EKIFA single board computer, which only has 128MB of RAM. Trond Danielsen Running in 128 MB should be find. I think that compiling in 128MB may still be a challenge. You may want to consider a cross-development setup. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tx_empty continued
On Mon, Jan 15, 2007 at 06:32:08AM -0800, Brett Trotter wrote: After seeing Matt Ettus' and Eric Blossom's responses regarding fixing the transmitter to keep it from repeating the last sample seen and ramp down the value to zero and am left unsure what is the best place to make this modification. I suppose since this is Matt Ettus' baby, we should go with his idea? Try Matt's version. Basically the one you had in your original message. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] SWIG compilation speedup!
On Mon, Jan 15, 2007 at 11:08:08AM -0500, Philip Balister wrote: I just got the USRP running with an EFIKA board and OSSIE SCA. I'm using the usrp-0.12 tarball. I had to use a USB2.0 controller in the PCI slot to work around the usrp USB full speed problems I am having. I took a quick look at using openembedded to build gnu radio. Thet already support most of the required dependencies, but I noticed fftw is missing. When I am bored (heh) I'll see about adding fftw and seeing if I can get gnu radio to build in cross environment. Philip Thanks for the pointer to openembedded.org Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GSM BTS Tx Signals on USRP
Actually, assuming that you want your Tx coordinated with the Rx, you'll need the not-yet-written code for precise timing synchronization. Actually, I am more interested in getting two Tx signals synchronized. One would be to simulate the BTS and the other the MS. Sharmila Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] PlayStation 3
Hello, So has anyone got their PS3 yet? A store claims to have the 60 gb model a not too far distance away and I am tempted. But I do not want to be first on the block to get one. 73 Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Ebuild for GNU Radio for Gentoo users
For any Gentoo users out there I've created a couple of ebuilds to install GNU Radio and, more importantly, its dependencies. The 3.0.2 tarball based ebuild has been submitted to the Gentoo project and can be found attached to the request at: http://bugs.gentoo.org/show_bug.cgi?id=90667 I have only tested this on x86 and used the check cases to verify a correct build. It would be great if someone with a real USRP would verify that the build is performed correctly. You can enable these dependencies with the package local USE flag 'usrp'. For those interested in building the latest from subversion I've created an ebuild for that on my own host. You can either use the ebuild directly from: http://b83.net/radio_overlay/sci-misc/gnuradio-svn/gnuradio-svn-20070115.ebuild or follow the instruction to set up an overlay I created with both gnuradio-3.0.2 and gnuradio-svn: http://b83.net/wiki/index.php?title=HOWTO_Portage_Overlay I will add instructions to the GNU Radio wiki shortly. Let me know if anyone has any problems or can verify the build is successful on other architectures. Kyle ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] PlayStation 3
On Mon, Jan 15, 2007 at 08:48:22PM -0500, Eric A. Cottrell wrote: Hello, So has anyone got their PS3 yet? A store claims to have the 60 gb model a not too far distance away and I am tempted. But I do not want to be first on the block to get one. 73 Eric I have had access to one remotely for a while, and received one from Fry's a couple of days ago, though I haven't found time to mess with it yet. The remote one I was using was running Fedora Core 5 and had the IBM SDK installed on it. That's how I'm going to set mine up. I have benchmarked the USB throughput on it with the USRP. Input is good (32MB/s), but output is a little slow (28MB/s). This is consistent with what we've seen on other PPC's including dual processor G5's. GNU Radio builds on the PS3, but you've got to be patient. It took about 30 minutes, and that was after splitting gnuradio_swig_python into the 5 pieces. It's currently not passing make check. I haven't spent any time tracking it down, but it may to that I'm generating .so's that are 64-bit while python is compiled in 32-bit mode. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Build errors
I am getting build errors on 3 different machines which heretofore have worked perfectly. It involves the pmt/mblock code. The failure to build comes in the last step of building the libmblock.so and libmblock-qa.so. pmt_nth, pmt_intern, pmt_wrong_type::pmt_wrong_type, are all listed as undefined references in the mblock library link statements and the build fails. Is anyone else experiencing this and have you fixed it? Eric and others are NOT experiencing this so I am trying to figure out what is going wrong on my 3 Ubuntu 6.1 machines with the problem. Bob -- AMSAT Director and VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. ARRL SDR WG Chair If you board the wrong train, it is no use running along the corridor in the other direction. - Dietrich Bonhoeffer ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Python Threads and C Semaphores
Hello, I have a fat C++ extension to a Python 2.3.4 program. In all, I count five threads. Of these, two are started in Python using thread.start_new_thread(), and both of these wait on semaphores in the C++ extension using sem_wait(). There also is one Python thread spawned with gnuradio.gr.gr_threading.Thread.start(), and one thread running wholly in the extension. I notice that when one of the Python threads calls the extension and waits on a semaphore, all but the C++ thread halt even when not waiting on any semaphore. How do we get this working right? Thank you, Jeremy ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
