From: Alexander Aring <alex.aring@gmail.com>
To: Andrey Yurovsky <yurovsky@gmail.com>
Cc: linux-zigbee-devel@lists.sourceforge.net, linux-wpan@vger.kernel.org
Subject: Re: [Linux-zigbee-devel] 802.15.4 scan, scan_req and ieee802154_nl_scan_confirm()
Date: Thu, 18 Sep 2014 23:52:59 +0200 [thread overview]
Message-ID: <20140918215250.GB15411@omega> (raw)
In-Reply-To: <20140918213653.GA15411@omega>
On Thu, Sep 18, 2014 at 11:36:53PM +0200, Alexander Aring wrote:
> On Thu, Sep 18, 2014 at 02:07:21PM -0700, Andrey Yurovsky wrote:
> > I'm troubleshooting issues with an Atmel AT86RF212 radio on mainline
> > (3.17-rc5 at this time) and was wondering about forcing an active scan
> > via the "iz scan" command. This comes back as not supported so I
> > wanted to understand why.
> >
> > It looks like ieee802154_scan_req() should be invoked in nl-mac.c in
> > response to a netlink message, this will return -EOPNOTSUPP when
> > ieee802154_mlme_ops(dev)->scan_req is NULL, and indeed that appears to
> > be the case. I can't find anyone in the soft-MAC setting .scan_req in
> > the MLME ops structure, is that correct?
> >
> > The only place I see it set is the fake full-MAC radio (fakehard.c)
> > where it's implemented as fake_scan_req() which in turn calls
> > ieee802154_nl_scan_confirm() to report the fake scan result.
> >
> > I then tried to find anything else calling
> > ieee802154_nl_scan_confirm() and was unable to, is that right or am I
> > missing something?
> >
> > Please forgive my ignorance but is scanning "broken" at this time?
>
> yep, I would say the mac802154, netlink interface is completely broken.
> And didn't work ever at any mainline status.
>
but hey I still accept patches for bug fixes. :-)
New features depends -> if it's useful to integrate it in the rework
branch. I tried to figure out how the netlink interface works, I gave up
when I saw the "extern struct nl_policy foo" in the netlink interface
header. This is normally a uapi header, so I don't know why
this is there. netlink is one piece which is completely different in the
rework.
Sorry, if you thought that the 802.15.4 branch is in any useful state.
:-(
- Alex
prev parent reply other threads:[~2014-09-18 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAkeqgW=Y4-L1uhGfS7=2-4ZLKWzhKTgJjmxKvOW74N9jNVREw@mail.gmail.com>
2014-09-18 21:36 ` [Linux-zigbee-devel] 802.15.4 scan, scan_req and ieee802154_nl_scan_confirm() Alexander Aring
2014-09-18 21:52 ` Alexander Aring [this message]
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=20140918215250.GB15411@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=yurovsky@gmail.com \
/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