Hi,
> > I am tying to add one method in src/manager.c file in connman-0.59.
> >
> > I added "RequestLoadDriver" method as below.
> >
> > static GDBusMethodTable manager_methods[] = {
> > { "GetProperties", "", "a{sv}", get_properties },
> > { "SetProperty", "sv", "", set_property },
> > { "GetState", "", "s", get_state },
> > { "CreateProfile", "s", "o", create_profile },
> > { "RemoveProfile", "o", "", remove_profile },
> > { "RemoveProvider", "s", "", remove_provider },
> > { "RequestScan", "s", "", request_scan },
> > * * { "RequestLoadDriver", "s", "o",
> > request_load_driver },
> *> * { "EnableTechnology", "s", "", enable_technology,
> >
> > I had defined
> > static DBusMessage *request_load_driver(DBusConnection *conn,
> > DBusMessage *msg, void *data)
> >
> > I compiled and executed with "connmand -d -n".
> >
> > Now when I try to request load driver using dbus-send
> > # dbus-send --system --print-reply --dest=org.moblin.connman /
> > org.moblin.connman.Manager.RequestLoadDriver string:"LoadDriver"
> > variant:boolean:true
> > *Error org.freedesktop.DBus.Error.UnknownMethod: Method
> "RequestLoadDriver"
> > with signature "sv" on interface "org.moblin.connman.Manager" doesn't
> exist*
can you please fix your email client. This usage of * and breaking the
threading is not acceptable. I can't even read through your response
properly.
> *the signature has to match for obvious reasons.*
> **
> [Raghu]: I hope you are telling *{ "RequestLoadDriver", "s", "o",
> request_load_driver }, is wrong. *
> Will you please tell me what should be the signature here and where/how I
> should modify?
>
> Here my requirement is user will request:
> dbus-send --system --print-reply --dest=org.moblin.connman
> / org.moblin.connman.Manager.RequestLoadDriver
> string:"LoadDriver" variant:boolean:*true*
> true/false to set interface up/down.
>
>
>
> *However what is this method suppose to be doing anyway?*
>
> [Raghu]: I want to add load/remove of Wi-Fi driver functionality in ConnMan.
> So that I can request connman to load the driver and it will execute the
> script present in the path say /usr/etc/load_driver.sh
This is the wrong approach. ConnMan will never load WiFi drivers
directly. That is the job of udev or the kernel itself.
> I found one issue with connman, assume we had loaded wifi driver and wifi
> interface is down. When I run connman with "connmand -d -n", it is bringing
> wifi interface UP and tries to run wpa_supplicant.
>
> I think actually it should be like, if wifi interface is UP, then connmand
> should try running wpa_supplicant?
Actually no. ConnMan tries to load wpa_supplicant anyway since that
daemon can run in the background and idle. ConnMan decides when to
activate a WiFi device and then wpa_supplicant is used.
Your wpa_supplicant version is broken or your kernel WiFi driver has an
issue. Please fix that part.
Regards
Marcel
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
