farhan/i3e_template_driver
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updating README structure and content

Browse Source
This commit is contained in:
farhan 2025-03-30 00:09:46 -04:00
parent 1b1e0317ba
commit 29882a5e68
Signed by: farhan
GPG Key ID: 64D62A2AD0D3A2B5
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -29,7 +29,17 @@ ifconfig wlan create wlandev i3e0
## How to read
Like all drivers, this might come off like a wall of code with no context.
The order to read this code is:
I hope this explanation breaks it down into manageable blocks. The code is minimal and heavily documented.
Since there is no PCI or USB bus, I simulated the BUS through `callout`s with detailed explanations of what they are intended to replace.
The driver sub-routines are as follows:
1) The attachment, probe and initiation process
2) The state change function
3) Beacon frame scanning and association
## Atachment, Probe and Initiation
1) `i3e_attach` - Executed after the device is identified by
the `probe` function. Note, because this driver is a software-only
implementation, not a real USB, PCI or SDIO driver. It should power on the device, read any hardcoded values (ie, device version, MAC address, etc) and enable the device accordingly. The end result will be the `i3e0` interface.
@ -41,6 +51,17 @@ implementation, not a real USB, PCI or SDIO driver. It should power on the devic
### Explanation
## Scanning Process
When the device is turned on in XXX mode, it begins to scan. The following tasks are done:
1) The `vp_newstate` handler is called with the `nstate` value set to `IEEE211_S_SCAN`. Real device drivers set the physical device to scan mode. This allows them to receive arbitrary beacon frames.
2) ieee80211 will call the `ic_scan_start`, `ic_set_channel` through all channels, and finally `ic->scan_end`.
2) At this point, the device should receiving beacon frames from nearby stations. In a real driver, this would happen via:
* In USB, the Rx bulk callback handler
* In PCI, a PCI interrupt with the read flag set
Both implementations would read the raw frame, perform any modifications as needed, and send the frame to the ieee80211 layer via `ieee80211_input`.
## Source Files
## ieee80211com