From: albertofanjul@gmail.com
To: linux-wireless@vger.kernel.org
Subject: Checking p2p capabilities
Date: Tue, 19 Jan 2016 12:34:57 +0100 [thread overview]
Message-ID: <20160119113457.GA32060@archlinux-alberto> (raw)
Hi, I'm maintainer of https://github.com/albfan/miraclecast and as a project with specific hardware needs, I build a hardware tester, but it is to naive:
https://github.com/albfan/miraclecast/blob/master/res/miracle-utils.sh#L68
basically it look for p2p interface modes grepping iw phy <phyname> info.
Lot of people trying miraclecast ask me:why it's device do not support p2p? (while it's documentation says it does, many times is just what they think, not reality).
I wonder if that is a matter of driver, modules or pure hardware. Is there any way to check it directly and not from a grep inside iw ?.
something like:
iw phy wlp3s0 get P2P-client
iw phy wlp3s0 get P2P-GO
About kernel, modules and hardware, are they completely black box for others?, I mean, can I detect if my device hardware supports some interface but my driver or module can't?
At this point my script informs pretty well, and there's a few people ask such things, but I would like to check it in a better way, even with an api inside my project
Something related with this lines I could check by myself (I use that clone for it's line anchors)
https://github.com/cozybit/iw/blob/master/util.c#L124
https://github.com/cozybit/iw/blob/master/info.c#L276
NL80211_ATTR_SUPPORTED_IFTYPES
NL80211_IFTYPE_MAX
next reply other threads:[~2016-01-19 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:34 albertofanjul [this message]
2016-01-19 11:57 ` Checking p2p capabilities Johannes Berg
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=20160119113457.GA32060@archlinux-alberto \
--to=albertofanjul@gmail.com \
--cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.