[Discuss-gnuradio] Installation Guide

2005-04-10 Thread mgray
Since there seems to be a lot of questions on getting all the software installed for GNU radio, I've put together an installation guide and shell scripts to hopefully greatly simplify the process: http://www.kd7lmo.net/ground_gnuradio_install.html All comments and suggestions are appreciated.

Re: [Discuss-gnuradio] Affordable A/D board available soon

2005-04-10 Thread Rick Parrish
Will Ware wrote: http://comsec.com/wiki?N1ibtSoftwareRadioBoard. I like it! -rick ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] pipe trick

2005-04-10 Thread Bob Vincent
I examined the internal buffering and thread scheduling code in the GnuRadio core. The scheduler is "sink-driven", as I understand it, relying on USRP polling to pull data from the internal buffers. It has been arranged to have sufficient data ready to go, since the USRP must transmit isochronous

[Discuss-gnuradio] Affordable A/D board available soon

2005-04-10 Thread Will Ware
I am working on a low-cost A/D board that samples at 24 MSPS with 12 bits of resolution and expect to have ten boards ready by the end of April. There is information about it at http://comsec.com/wiki?N1ibtSoftwareRadioBoard. I wanted to let people on this list know about it for a couple of reasons

Re: [Discuss-gnuradio] pipe trick

2005-04-10 Thread Frank Brickle
Proviso: I could be *seriously* misunderstanding what's up here. If so, my apologies and please ignore. Have you tried setting the pipe reads/writes to O_NONBLOCK, and checking on read to see whether anything actually arrived? Obviously you wouldn't want to be spinning on empty reads, so selec

Re: [Discuss-gnuradio] pipe trick

2005-04-10 Thread Chuck Swiger
At 03:02 AM 4/10/2005 -0400, you wrote: How are you _reading_ the data from the pipe? Even if you're flushing the data into the pipe after every write, the reader could be buffering it. Tks Dave - yes, yesterday I put a vector_sink_b after the file_descriptor_source of the pipe and verified that