Would an extra bit of hardware such as a PCI card with PLX's PCI9030
breaking out to the USRP with something like an 80 wire IDE cable be
suitable for high bandwidth, low latency and lowish cost?
(http://www.plxtech.com/products/io_accelerators/PCI9030/default.htm)
You might be able to do
On Thu, Jul 27, 2006 at 12:47:46AM +0200, Jens Elsner wrote:
Hello,
I'd like to calculate the complex dot product with GNU Radio.
Is there a way to do it faster that this? This correlation takes
ages...
You can probably repurpose the existing gr_fir_ccc.h code.
See
On Thu, Jul 27, 2006 at 04:09:24PM +1000, Jason Hecker wrote:
Would an extra bit of hardware such as a PCI card with PLX's PCI9030
breaking out to the USRP with something like an 80 wire IDE cable be
suitable for high bandwidth, low latency and lowish cost?
On Thursday 27 July 2006 15:39, Jason Hecker wrote:
Would an extra bit of hardware such as a PCI card with PLX's PCI9030
breaking out to the USRP with something like an 80 wire IDE cable be
suitable for high bandwidth, low latency and lowish cost?
Was that really ethernet framing? Or just using the CAT5 cable as 4
differential pairs?
No, from memory he just used the driver chips and implemented his own
bit toggling and framing magic in the FPGA. He just used the drivers
and transformers to get the data on and off the cable.
If you
(http://www.plxtech.com/products/io_accelerators/PCI9030/default.htm)
That's one route, though 32-bit 33-MHz PCI is pretty much the bottom
of the barrel these days. Hence the interest in PCI-Express and/or
Express Card.
True. At a glance I couldn't see any alternative from PLX for faster
On Wed, 26 Jul 2006, Marcus Leech wrote:
[...]
o Is it time to think about moving away from USB for USRP? Perhaps to
PCI-X 2.0, or PCI-Express?
http://comsec.com/wiki?USRPnotUSB
--
Stephane
PS: I would cast my vote for GigE.
___
On Wed, Jul 26, 2006 at 11:08:25PM -0700, Eric Blossom wrote:
On Thu, Jul 27, 2006 at 12:47:46AM +0200, Jens Elsner wrote:
Hello,
I'd like to calculate the complex dot product with GNU Radio.
Is there a way to do it faster that this? This correlation takes
ages...
You can
On Thursday 27 July 2006 16:09, Jason Hecker wrote:
That's one route, though 32-bit 33-MHz PCI is pretty much the bottom
of the barrel these days. Hence the interest in PCI-Express and/or
Express Card.
True. At a glance I couldn't see any alternative from PLX for faster
PCI busses.
On Thu, Jul 27, 2006 at 04:02:00PM +0930, Daniel O'Connor wrote:
On Thursday 27 July 2006 15:39, Jason Hecker wrote:
Would an extra bit of hardware such as a PCI card with PLX's PCI9030
breaking out to the USRP with something like an 80 wire IDE cable be
suitable for high bandwidth, low
On Thu, Jul 27, 2006 at 04:39:43PM +1000, Jason Hecker wrote:
(http://www.plxtech.com/products/io_accelerators/PCI9030/default.htm)
That's one route, though 32-bit 33-MHz PCI is pretty much the bottom
of the barrel these days. Hence the interest in PCI-Express and/or
Express Card.
True.
Hello,
a quick question regarding gr_block::history() etc.
Say I've called set_history(2) in the constructor and
my work function pointers look like this:
gr_complex const *in = (const gr_complex *) input_items[0];
gr_complex *out = (gr_complex *) output_items[0];
What does in point to? Is
On Friday 28 July 2006 01:33, Eric Blossom wrote:
A 9030 is target only, you'd need a 9054, 9056, 9060 or 9080 otherwise
the performance would not be very great.
Good point. I've written drivers using the 9080 before it was pretty
easy to use. The scatter/gather stuff worked fine for me,
HiI am looking at the usrp_std.v module and the schematics for the FPGA and the FX2/FPGA interface.It seems to me that the data of course arrives as a serial input to the FX2 chip. Then, it gets to the FPGA as a 16bit parallel input from the GPIF bus. That input is called usb_data in the FPGA.
On Thu, Jul 27, 2006 at 09:59:16PM +0200, Jens Elsner wrote:
Hello,
a quick question regarding gr_block::history() etc.
Say I've called set_history(2) in the constructor and
my work function pointers look like this:
gr_complex const *in = (const gr_complex *) input_items[0];
15 matches
Mail list logo
