14 Commits

Author	SHA1	Message	Date
exelix	a6c409ac69	add nifmSetServiceType to set which nifm service to init	2019-03-15 21:07:47 +01:00
exelix	19dc760d52	Update nifm.c	2019-03-08 17:45:05 +01:00
exelix	cc18ea8cd3	Update nifm.c	2019-03-08 14:56:29 +01:00
exelix	d2e41e16e2	Check nifm permissions for nifmSetWirelessCommunicationEnabled	2019-03-08 14:34:48 +01:00
exelix	af349dc2a1	Update nifm.c	2019-03-03 19:23:57 +01:00
exelix	9d260c36bd	Update nifm.c	2019-03-03 19:15:05 +01:00
exelix	d80db4ce69	remove unneeded include	2019-03-03 19:08:03 +01:00
exelix	9fd18f4d02	Change initialization mode	2019-03-03 18:39:21 +01:00
exelix	d8c631b65c	Init nifm in the proper context, add SetWirelessCommunicationEnabled	2019-03-03 15:42:25 +01:00
fincs	11b7bece4a	Change all services except fatal to use hosversion* instead of kernelAboveXYZ	2019-02-18 21:48:49 +01:00
shibbs	131b92a8c8	Add in more NIFM functionality (#236)	2019-01-27 00:12:15 +01:00
yellows8	318562d13b	Init/exit nifm in socketInitialize/socketExit, the user app no longer has to manually handle this when using gethostid/gethostname. Use domains for nifm. Style adjustments in nifm.c.	2018-10-23 14:04:58 -04:00
David Marcec	d91c315f77	Fixed nifm not initializing properly for < 3.0.0	2018-08-27 16:10:53 +02:00
Somebody Whoisbored	ad4af954c2	Added nifm service (#110) ... * Added nifm service * Properly implemented gethostid * Implemented gethostname	2018-06-07 18:00:51 -04:00