-
Notifications
You must be signed in to change notification settings - Fork 122
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add RSSI for all platforms and Frame Control (supporting Raspberry PI…
… only for now)
- Loading branch information
Showing
2 changed files
with
11 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot. What is the meaning of adding this line 'and [3,off1], 0xff, [4,off5]'?
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[3,off1] is the Frame Control byte.
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mzakharo Thank you so much for your quick reply!! What is the purpose of framecontrol here? Originally, I was thinking the change of 'last_rssi = wlc_rxhdr->rssi' should do this job, but it seems some additional framecontrol is needed, any reason for this? If we do not need to report framecontrol information to user space, then can we ignore the changed line of 'and [3,off1], 0xff, [4,off5]'?
Another question is that could we add this line and corresponding defination of 'last_rssi = wlc_rxhdr->rssi' to BCM 4339?
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
frame control byte and rssi have nothing to do with each other. just lumped together in one CL. you can cherry pick as you please
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mzakharo Thank you a lot for the reply. I have following two questions:
Thanks a lot.
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much @mzakharo , I checked the rssi on Nexus 6P. They worked. But, I found that the RSSI on two cores are different. Should they be same value?
7e3f9f7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
never looked at RSSI of anything but core 0. However, I cannot explain this value being different on different cores. 'last_rssi' should not get changed in between switching of cores. From my understanding, the D11 microcode should just loop through all cores back to back without getting to the section that updates last_rssi until the next new packet.