low level access to wimax device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2011-05-03 at 19:51 +0400, Anton Novikov wrote:
> Well, i've obtained L3_L4_OPCODE_REPORT_SCAN_RESULT message :)
> 
> Inaky, will you tell me, messages L3_L4_OPCODE_REPORT_BS_INFO,
> L3_L4_OPCODE_REPORT_SII, L3_L4_OPCODE_REPORT_BS_INFO can be received or not?
> Them are contains very significant information for me.

?? They are received by the wimaxd daemon -- I think I am
misinterpreting your question.

> 
> 29.04.2011 12:33, Anton Novikov ?????:
> > Yes, it is, but power managenemt not is aim. I need to obtain
> > information about all observable NAPs (BSID, frequency, CINR, RSSI etc)
> > of each NSP. This seems to be accessible in ScanUpdateCB callback
> > function (can be registered by wmx_RegisterScanUpdateCB) or
> > wmxNds_ScanReportArrived called on L3_L4_OPCODE_REPORT_SCAN_RESULT
> > messade arrival.
> > Unfortunately, NAP list inaccessible in common API functions - it causes
> > me to use internal SDK and PipeHandler functions. Common API provides
> > only tabulated information about NSPs as I understood.
> 
> _______________________________________________
> wimax mailing list
> wimax at linuxwimax.org
> http://lists.linuxwimax.org/listinfo/wimax





[Index of Archives]     [Linux Kernel]     [Linux Wireless]     [Linux Bluetooth]     [Linux Netdev]     [Linux Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux