There's a linux proxy program, if I remember correctly, called tgtxvi020, which in turn use libxvi020.so. This proxy program basically tunnel request and response between windows connection manager to linux side. I was doing a contract work with US army while I am porting wimax solution to a special military device. The Beceem contact was generated from our partner company which I may not able to disclose the info in the public. But I believe you can just try to call them, explain what you want to do, they may release you the linux package with some NDA agreement. Last time I was able to get the above linux scenario working with a windows laptop sitting at side. Later on I switched to Motorola as myself was in Motorola Wimax team before I join in my current company. Good luck.
Charles -----Original Message----- From: LOEWENTHAL Simon [mailto:si...@klunky.co.uk] Sent: Friday, May 29, 2009 9:38 AM To: charles zhuang Cc: wimax@linuxwimax.org Subject: Re: Beceem BCS200 Mobile WiMAX USB - Seeks Linux modules Hi Charles, This is more positive than I had expected. As noted I have the Beceem windows connection manager running with WINE. I am unsure how to tunnel the commands to this or even what this might involve. I have sent an Email to Beceem asking them for the modules. It was the general contacts address. Have you got any other contact details for them so that I might get them to send me the modules or source? Simon. charles zhuang wrote: > BCS200 has linux release, you need to work with Beceem to get them > release you the source code. > For binary, linux has following components: > drxvi314.ko - kernel driver > macxvi200.bin - firmware > macxvi.cfg - configuration file for firmware > On user space, as of 2/2009, Beceem doesn't have a linux version of > connection manager, nor do they have supplicant, you need to run a proxy > program to tunnel the request to Beceem windows connection manager and > also use windows supplicant. > Last time when I spoke to Beceem they told me there's no plan to > complete those components in the linux platform. > > Charles > > -----Original Message----- > From: wimax-boun...@linuxwimax.org [mailto:wimax-boun...@linuxwimax.org] > On Behalf Of Simon L > Sent: Friday, May 29, 2009 7:05 AM > To: wimax@linuxwimax.org > Subject: Beceem BCS200 Mobile WiMAX USB - Seeks Linux modules > > Dear all, > > I am looking for a driver for this USB Wimax card I bought. It came > with a subscription for a WiMax company in Holland called aerea.nl. > The USB casing has written on it: Alcatel-Lucent 9799 MIMO USB > Dongle, 3.5Mhz, P/N: 1AF16115ABAA However, the o/p of lsusb -v shows > that this is actually a USB device made by Beceem. > > The kernel on my laptop is 2.6.28-11-generic Ubuntu i686 > > I installed the s/w that came with the card with WINE. Its a connection > manager and the GUI installs and runs. Of course, it does not pick up > the > card. > > > In the Wine directory these drivers are installed for Windows. I seem > to > remember there was a way of loading Windows drivers in Linux. Cannot > remember what the programme was called. > > ~/.wine/drive_c/Program Files/Alcatel-Lucent/WCM/Driver/USB# ls -1 > bcmbusctr.cat > BcmBusCtr.inf > BcmBusCtr.sys > drxvi314.cat > drxvi314.inf > drxvi314.sys > macxvi200.bin > macxvi.cfg > > Does anyone know of anyway of getting this to run on Linux? > > Regards, Simon. > > > # lsusb -v > Bus 002 Device 008: ID 198f:0210 Beceem Communications Inc. > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize0 64 > idVendor 0x198f Beceem Communications Inc. > idProduct 0x0210 > bcdDevice 0.01 > iManufacturer 1 Beceem Communications > iProduct 2 BCS200 Mobile WiMAX > iSerial 3 N/A > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 111 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 500mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 6 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x04 EP 4 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0000 1x 0 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x85 EP 5 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 6 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x06 EP 6 OUT > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 6 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 1 > bNumEndpoints 6 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 255 Vendor Specific Subclass > bInterfaceProtocol 255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x04 EP 4 OUT > bmAttributes 1 > Transfer Type Isochronous > Synch Type None > Usage Type Data > wMaxPacketSize 0x0020 1x 32 bytes > bInterval 1 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x85 EP 5 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 6 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x06 EP 6 OUT > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 6 > Device Qualifier (for other device speed): > bLength 10 > bDescriptorType 6 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize0 64 > bNumConfigurations 1 > Device Status: 0x0000 > (Bus Powered) > > > > > _______________________________________________ > wimax mailing list > wimax@linuxwimax.org > http://lists.linuxwimax.org/listinfo/wimax > > _______________________________________________ wimax mailing list wimax@linuxwimax.org http://lists.linuxwimax.org/listinfo/wimax
