I guess the next question is how do I know what to put in there. I know our channel plan and I have our center frequencies but I'm not sure how I should represent them in those files. The existing ones look like they're based on a range of frequencies rather than just a center frequency. So if I have a center frequency of 3415, do I add that to the file as <FirstFreq>340500</FirstFreq> and <LastFreq>341500</LastFreq>? As I mentioned previously, we have IOTed with Intel and our channel plan has been submitted to them; as far as I know it is now included in the Windows provisioning databases so I guess it's only a matter of time before it percolates down to the Linux drivers. Any idea how long that normally takes? Thanks, Dermot > -----Original Message----- > From: wimax-bounces at linuxwimax.org [mailto:wimax- > bounces at linuxwimax.org] On Behalf Of Erich Izdepski > Sent: 02 September 2010 21:57 > To: wimax at linuxwimax.org > Subject: Re:WiMAX_VB.bin > > You just need to change some of the parameters in the existing xml > files. Don't bother swapping the files out- just changes some data in > them. Operator, Realm, nsp-id, all the channel plan stuff. The things > your laptop needs to know to connect to your network. > > You will also need to work closely with intel and have your network > validated against their requirements to get your network profile into > their software for Windows. All the data you have to provide for that > effort is what goes into the xml files for linux. > ________________________________________ > From: wimax-bounces at linuxwimax.org [wimax-bounces at linuxwimax.org] on > behalf of wimax-request at linuxwimax.org [wimax-request at linuxwimax.org] > Sent: Thursday, September 02, 2010 3:00 PM > To: wimax at linuxwimax.org > Subject: wimax Digest, Vol 17, Issue 1 > > Send wimax mailing list submissions to > wimax at linuxwimax.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.linuxwimax.org/listinfo/wimax > or, via email, send a message with subject or body 'help' to > wimax-request at linuxwimax.org > > You can reach the person managing the list at > wimax-owner at linuxwimax.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of wimax digest..." > > > Today's Topics: > > 1. WiMAX_VB.bin (Dermot Williams) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 2 Sep 2010 16:46:54 +0100 > From: "Dermot Williams" <Dermot.Williams at imaginegroup.ie> > To: <wimax at linuxwimax.org> > Subject: WiMAX_VB.bin > Message-ID: > > <0B4E432C64EA8B45A001DD6E1F0E1D7206396CFB at dubexc01.imagine.local> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > > > I work for a company that is in the process of deploying a large WiMax > network. We're testing with Intel laptops with the 6250 chipset at the > moment and I wanted to have a play with Linux on them. I've everything > working using a mainline kernel on Ubuntu 10.04 - drivers load, wmx0 is > created, wimaxd starts. > > > > However, the WiMAX_D*.bin files that come with version 1.5 of the Linux > drivers don't have my company's provisioning data. This data is in the > Windows drivers but the windows versions of those two files are binary, > whilst the Linux versions are plain XML. The Linux drivers don't like > it > when I replace the XML format .bins with the Windows versions so I'm > guessing I can't just do a straight swap of the files. > > > > Does anyone know whether or not it's possible to convert the Windows > provisioning databases to XML? > > > > Thanks, > > > > Dermot Williams > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.linuxwimax.org/pipermail/wimax/attachments/20100902/196ea > 3c1/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > wimax mailing list > wimax at linuxwimax.org > http://lists.linuxwimax.org/listinfo/wimax > > End of wimax Digest, Vol 17, Issue 1 > ************************************ > > > This email may contain confidential and privileged material for the > sole use of the intended recipient. Any review, use, distribution or > disclosure by others is strictly prohibited. If you are not the > intended recipient (or authorized to receive for the recipient), please > contact the sender by reply email and delete all copies of this > message. > > > _______________________________________________ > wimax mailing list > wimax at linuxwimax.org > http://lists.linuxwimax.org/listinfo/wimax