I was also working on something simular with the 1.4.0 version of the Driver. Your dirty hack was the same one that came to my mind. So I have a wimaxd-wmx0, wimaxd-wmx1, wimaxd-wmx2, etc... Same for wimaxcu-wmx0, wimaxcu-wmx1, etc... I changed the code to look for config.wmx0.xml, config.wmx1.xml, etc. Also had to change the listening port in each XML file for each card, 1234, 1235, etc.. It's really a rough work around, but I successfully got 3 different cards working on 1 box last night, so I'm content. Thank you for the advice with the 1.5 version! :) - Kyle On Mon, Sep 27, 2010 at 1:24 PM, Inaky Perez-Gonzalez <inaky at linux.intel.com > wrote: > Hi Kyle > > On Sat, 2010-09-25 at 03:50 -0700, Kyle Williams wrote: > > Hello, > > > > > > I'm trying to use three Intel EchoPeak 5150 cards working on a single > > PC. I noticed with the latest wimaxd has the "-i" option which allows > > the specification of the interface for wimaxd to control, but the > > wimaxcu program does not allow the same type of specification. Is > > there some way to specify which wimaxd instance the wimaxcu program > > controls? > > > > > > The objective is to get three Echopeek 5150 cards to all work on the > > same system. > > Is this possible at this time? > > Will the wimaxcu program support this down the road? > > It is possible but very dirty. Unfortunately the daemon doesn't have > provisions to identify different interfaces at the RPC level. > > The ugly trick I use is configure three builds with three different > prefixes (to avoid the databases getting corrupted) and then modify > each's configuration file (prefix/wimax/config.xml) so that <sdkportnum> > are different. > > somehting like: > > tar xf wimax-1.5.tar.gz > for v in 0 1 2 > do > mkdir build-wmx$v > (cd build-wmx$v && ../wimax/configure --prefix=/opt/wimax/wmx$v/ > --program-suffix=-wmx$v && make install) > done > > [change the port numbers in /opt/wimax/wmx*/etc/wimax/config.xml] > > I then add the /opt/wimax/wmx*/bin paths to my PATH and just have to > start > > $ for v in 0 1 2; do wimaxd-wmx$v -i wmx$v -b; done > > and in the command line > > $ wimaxcu-wmx0 scan .. > etc > > As I said, it is dirty as heck, but it does the trick. > > > > Then start once instance of each daemon with -i IFACENAME and call the > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxwimax.org/pipermail/wimax/attachments/20100927/b94bed5b/attachment.html>
