|
From: | Philip Balister |
Subject: | Re: [Discuss-gnuradio] ARM9? |
Date: | Fri, 27 Nov 2009 13:43:06 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 |
On 11/27/2009 01:36 PM, Doug Geiger wrote:
David Burgess wrote:The only part of GNU Radio we are using is libusrp, but GNU Radio's "kitchen sink" dependencies mean that we have to build all kinds of other crazy stuff to get that, stuff that we do not actually use. (Seems to be a common theme here...) We can write our own fixed point support for the rest of our application, if we can just get libusrp to work. (Maybe the solution is a libusrp replacement that is independent of GNU Radio and builds with minimal external dependencies.)
I seem to have missed David's response ...Before you spend a lot of time on this, make sure the ARM9 you are looking at has an EHCI controller. I never did get the USRP to work with the USB1.1 controllers found on ARM( chips a few years ago. You need to mess with the Cypress/FPGA interface.
There may be some ARM( systems with EHCI controllers these days. I am not 100% certain though.
Philip
Philip-- David David A. Burgess Kestrel Signal Processing, Inc.It seems to me it should be *possible* to setup the autotools to only require the libs needed by libusrp if you --disable-* everything else when you run configure. I would imagine that would be a healthy bit of surgery on the configure.ac file and some of the related files: separating out which dependencies are from which components, etc. Sounds like it might be useful for some of the places GNURadio can end up running though. Doug
[Prev in Thread] | Current Thread | [Next in Thread] |