Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Writing plugins: how to provide a "technology"?
(Sergey 'Jin' Bostandzhyan)
----------------------------------------------------------------------
Date: Wed, 12 Aug 2020 20:41:49 +0200
From: Sergey 'Jin' Bostandzhyan <[email protected]>
Subject: Writing plugins: how to provide a "technology"?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi,
I am currently learning how connman plugins work, I started with
plugin-api.txt and also looked the sources, then tried to follow the plugin
document to get a "proof of concept" going.
So far I can see that the init function of my plugin is being called,
but that's it.
I did register tech, network and device callbacks via
connman_network_driver_register(), connman_device_driver_register() and
connman_technology_driver_register(), but I do not see any printouts in
the callbacks, no probes, nothing.
Could someone please explain what needs to be done in order for a technology
to become visible? I guess same is valid for "device" and "network".
When I look at other plugins (for instance ethernet), the only thing their
probes do is to return 0.
So how exactly does it work? Am I supposed to use some notification
mechanisms that are not mentioned in the plugin documentation or what am I
missing?
Kind regards,
Jin
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 58, Issue 3
**************************************
