From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: vt6655 implementation of cfg80211 subsystem
Date: Wed, 3 Aug 2022 06:37:13 +0200 [thread overview]
Message-ID: <63114b67-66fe-f324-3dcd-7986483fac48@gmail.com> (raw)
Hi,
to further improve the driver vt6655 I was reading through the cfg80211
subsystem documentation.
https://www.kernel.org/doc/html/latest/driver-api/80211/cfg80211.html#device-registration
The following table shows structs/functions named in the documentation
with driver vt6655 implementation status:
Documentation in v6655 implemented
struct ieee80211_channel yes
struct ieee80211_rate yes
struct ieee80211_sta_ht_cap no
struct ieee80211_supported_band yes
struct ieee80211_iface_limit no
struct ieee80211_iface_combination no
struct wiphy minimal used
struct wiphy *wiphy_new(...) no
int wiphy_register(struct wiphy *wiphy) no
void wiphy_unregister(...) no
void wiphy_free(struct wiphy *wiphy) no
struct wireless_dev no
struct net_device no
Does it make sense to start the implementation here?
With which struct/function start first?
Thanks for your support.
Bye Philipp
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2022-08-03 4:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63114b67-66fe-f324-3dcd-7986483fac48@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).