You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found very interesting blog about very similar problem with WiFi driver and LuCI configuration possibility. Here it is.
From my investigation I have understood, that if we want to have complete support iNIC driver in LuCI(or GNU/Linux), we have two possible ways:
Add fullMAC ieee802.11 support to current driver. This means implement cfg80211_ops API support and export wiphy struct.
Adopt scripts from link to our reality.
IMHO first way more difficult, but will realize modern interface and will stay actual for long period. Second is more simple, but outdated and can be dropped by kernel maintainers at any time.
Personally I vote for fullMAC cfg80211 interface support. proper wext support can be done in parallel.
In short: I personally would also prefer a cfg80211_ops API support.
Think of the recently introduced changes of the kernel makes future development (more than needed) tricky (I had to revert an upstream patch with that one 1e18a85 just to get this running. I'm afraid that in future more of these are needed. ).
Don't know much about WiFi internals. So can only answer in a superficial way:
Of course the solution is preferable which promises to be more stable in the future.
Which you explained is "fullMAC ieee802.11".
I have found very interesting blog about very similar problem with WiFi driver and LuCI configuration possibility. Here it is.
From my investigation I have understood, that if we want to have complete support iNIC driver in LuCI(or GNU/Linux), we have two possible ways:
IMHO first way more difficult, but will realize modern interface and will stay actual for long period. Second is more simple, but outdated and can be dropped by kernel maintainers at any time.
Personally I vote for fullMAC cfg80211 interface support. proper wext support can be done in parallel.
@arnysch @Quallenauge @linusw what do you think?
@linusw we have discussed iNIC driver in private chat
The text was updated successfully, but these errors were encountered: