Re: Binder interface for wpa_supplicant?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2016-01-06 at 22:04 +0100, Johannes Berg wrote:
> 
> It seems to me that it would be possible to define, in some object-
> oriented fashion, the API used, and then map that to the different
> interfaces (socket/ctrl-iface, dbus, binder) in some build-time step.
> 
Looking at this, it might even make sense to roll in some config file
handling as well, since for example network properties are pretty much
directly coming from the config file to the control interfaces.

At which point it probably makes sense to unify all this between
hostapd and wpa_supplicant too ;-)

johannes

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap




[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux