summaryrefslogtreecommitdiff
path: root/src/technology.c
AgeCommit message (Collapse)AuthorFilesLines
2017-04-25Added some logs for debuggingSeonah Moon1-0/+4
Change-Id: I3a133fa6aebd28dea42f7dfd9ecb42d04c45f291 Signed-off-by: Seonah Moon <seonah1.moon@samsung.com>
2017-04-18Initialize a local variable (WGID-202395)chleun.moon1-1/+1
Change-Id: I6878ce2844c6ca821b0bff827edd248b559c6c6f Signed-off-by: cheoleun <chleun.moon@samsung.com>
2017-04-12[connman] Send ScanChanged signal.Niraj Kumar Goit1-6/+26
Send ScanChanged signal when device scanning status change. Change-Id: I9878cbb29d6c40363e6e629d6e6e7c855952ed0c Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
2017-03-21[connman] Added DBus method to get scanning status.Niraj Kumar Goit1-0/+40
Change-Id: Ib84cb1c218b6c468ffe413b63af2fe7a33c2a63e Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
2017-03-10When scan is started send signal ScanStarted to application.Niraj Kumar Goit1-0/+11
Change-Id: I034c3317a346140006e1d23d1389894c867012cc Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
2016-11-17[connman] Add new ScanDone signal for notification to upper layerSaurav Babu1-0/+15
Change-Id: I1c6f5d7a162ef7da9942ae41cdbbf64017b37aab Signed-off-by: Saurav Babu <saurav.babu@samsung.com>
2015-08-07Base Code merged to SPIN 2.4submit/tizen/20150810.034432hyunuktak1-12/+35
Signed-off-by: hyunuktak <hyunuk.tak@samsung.com> Change-Id: I84a42375b5c59739e4caca1f726699ea7647ef17
2015-07-08Disable rfkill block featuretaesub.kim1-4/+6
Change-Id: I279ad9d0e623872f4dcf37a6c3c9cd012842e448 Signed-off-by: Taesub Kim <taesub.kim@samsung.com>
2014-11-07multi-user: Add multi-user support in technologyZhang zhengguang1-0/+15
Use case: Given 2 users: UserA and UserB If UserA is connected to a wifi service, then UserB is not allowed to set wifi technology properties. Change-Id: Ia783b22bc28e9e487ddfa3a4c249c9d1ea76bde8
2014-10-31Tethering: Add hidden access point support in technologyChengyi Zhao1-1/+32
Change-Id: I73fccf5f322ee2597f8f58d5e3d7f60ddeb0a641
2014-10-31Tethering: Add open access point support in technologyChengyi Zhao1-13/+23
Change-Id: I86f4a22567f5df2fbd5d0c0c03c6cc5b6fc24a2d
2014-10-31Tethering: Notify listeners when station connection changesChengyi Zhao1-0/+10
Change-Id: I048c1a8a348b6f862ca104ad2fbe971f580fe180
2014-07-17Imported Upstream version 1.24upstream/1.24Zhang zhengguang1-439/+486
2013-06-10technology: Offlinemode could not be disabled if no technology was poweredJukka Rissanen1-5/+9
If all the technologies were powered off, then offline mode could not be disabled. Fixes BMC#26018
2013-05-06main: Rename AllowedTetheringTechnologies to TetheringTechnologiesPatrik Flykt1-1/+1
2013-04-30technology: Disable tethering when device disappearsJukka Rissanen1-0/+4
If tethering is active when device is removed, then shutdown tethering cleanly so that tether interface and bridge are properly removed.
2013-04-26technology: Auto start tethering if enabled and configuredJukka Rissanen1-65/+125
If the user has enabled persistent tethering mode in main.conf, then try to activate tethering when technology is re-enabled, or we are returning from offline mode, or after the device has rebooted.
2013-04-26ethernet: Add tethering supportJukka Rissanen1-0/+31
2013-02-26technology: Provide a function to get WiFi tethering informationTomasz Bursztyka1-16/+39
2013-01-30technology: Support multiple technology driversPatrik Flykt1-49/+111
As tethering is enabled on the technology level, both the bluetooth and the bluetooth_legacy plugin need to register technology drivers for CONNMAN_SERVICE_TYPE_BLUETOOTH. Modify the technology code to create a list of registered technology drivers instead of a single technology driver pointer.
2013-01-30technology: Enable/disable individual devices also with rfkillPatrik Flykt1-4/+16
In order to keep ConnMan devices in sync with Bluz 5 adapters, the individual devices need to be enabled/disabled also when unblocking/blocking them with rfkill. Thus enable devices after unblocking and disable devices before blocking with rfkill.
2013-01-30technology: Check technology driver probe function before callingPatrik Flykt1-1/+5
2013-01-30technology: Remove technology driver by pointerPatrik Flykt1-2/+4
Compare the technology driver pointer to the driver being unregistered as the function is supposed to remove only the given driver. Also check if the driver has a remove function before calling it.
2013-01-30technology: Remove unnecessary comparison and gotoPatrik Flykt1-5/+1
2013-01-04core: Remove WiMAX definitions from codePatrik Flykt1-4/+0
2012-12-12technology: Soft block on offline mode or disabled technologyPatrik Flykt1-2/+2
When adding an rfkill device which is unblocked, soft block it immediately if offline mode is enabled or the technology (enable_persistent) is disabled. Fixes BMC#25858
2012-10-26technology: Do not proceed with tethering if technology is not enabledTomasz Bursztyka1-0/+4
Fixes BMC#25846
2012-10-25technology: Do not presume a technology being hardblocked when createdTomasz Bursztyka1-6/+2
This fixes an issue with the TechnologyAdded signal when the first un-hardblock event occurs: - when a technology was created, D-Bus registration was done and hardblock was set to TRUE even if there was no evidence that the technology was rfkill driven - when the technology was updated to be rfkill driven, hardblock was already set to TRUE and thus the technology was not unregistered - when an rfkill event un-hardblocks the technology, the TechnologyAdded signal was not sent since the technology was already registered to D-Bus
2012-10-16technology: Fix hardblocked state on non hw rfkillable switch addedTomasz Bursztyka1-13/+17
If hardblock is on and a new device is inserted and detected as not hardblocked, then it will be possible to enable/disable it (soft rfkill) independently to the main hw rfkill switch.
2012-10-16technology: Recompute hardblocked state on rfkill remove eventTomasz Bursztyka1-0/+7
This fixes the case of cascading rfkill switches: if enabled, hard rfkilling such technology might generate contradictory events. 1 - first all switches are hardblocked 2 - then one of these switch (usually: device's switch) gets fully unblocked 3 - then this same switch gets removed Step 2 is in contradiction with step 1, so we need to care about such switch getting removed by recomputing the hardblocked state.
2012-10-16technology: Properly handle rfkill driven stateTomasz Bursztyka1-9/+43
2012-10-16technology: Use the right method to enable or disableTomasz Bursztyka1-22/+27
If rfkill driven, use rfkill soft block/unblock. If not, request the device to be enabled or disabled.
2012-10-16technology: Change enabled to a boolean and refactor accordinglyTomasz Bursztyka1-25/+20
2012-10-16technology: Refactor and split functions setting enabled stateTomasz Bursztyka1-25/+29
2012-10-16technology: Refactor rfkill event handling according to soft/hard blockTomasz Bursztyka1-22/+35
No need to proceed with softblocked if technology is already hardblocked. Apply offlinemode and persistant state according to softblocked state. (saner logic and helped to cleanup code from style point of view too)
2012-10-16technology: Add and handle a marker for softblock statusTomasz Bursztyka1-5/+11
2012-10-16technology: Add a marker to know if a technology is rfkill drivenTomasz Bursztyka1-3/+10
Useful for coming patches: enabling/disabling technologies will be done differently whether technology is rfkill driven or not: - if rfkill driven -> enabled will rely on rfkill states - if not -> enabled will rely on driver/devices states
2012-10-16technology: Refactor how a technology is enabled or disabledTomasz Bursztyka1-38/+28
Refactor how a device list is enabled/disabled: this will be useful for coming patches. Simplify also the code, and remove useless gotos.
2012-10-03technology: Do not expose a technology which is hard rfkilledTomasz Bursztyka1-4/+8
If hard rfkilled, a technology will not be exposed through DBus via GetTechnologies. If hard rfkill status changes, TechnologyAdded and TechnologyRemoved signals will be sent accordingly.
2012-10-03technology: Add helpers for (un)registering a technology in D-BusTomasz Bursztyka1-11/+34
2012-10-03technology: Do not apply Powered setting change if hardblock is onTomasz Bursztyka1-1/+7
2012-10-03technology: Simplify set_powered functionTomasz Bursztyka1-7/+3
2012-10-03technology: Link hard rfkill with actual device's stateTomasz Bursztyka1-8/+18
When hardblocking a technology, it should disable the devices which belongs to that technology. When un-hardblocking it should do the same but taking care about user setting (it will enable the devices if only enable_persistent is on).
2012-10-03technology: Handle harblock if all of them have identical typeTomasz Bursztyka1-0/+19
On some hardware, there exist two rfkill entities for the same type with a cascading issue: if one is soft blocked, the other one is hardblocked. But if the hardblock switch is set, all are hardblocked. This patch figures out that a technology is hardblocked only if all related rkill events get the same hardblock value.
2012-10-03technology: Handle rfkill hardblockTomasz Bursztyka1-12/+28
2012-10-03technology: Handle rfkill hash table in a saner wayTomasz Bursztyka1-6/+6
2012-10-01technology: Update tethering properties when relevantTomasz Bursztyka1-6/+22
2012-09-13technology: Returns the right error when setting tetheringTomasz Bursztyka1-2/+6
Fixes BMC#25721
2012-09-07technology: Fix memory leak as the tethering strings were not freedJukka Rissanen1-0/+4
2012-09-04Use g_slist_prepend() where appropriatePatrik Flykt1-2/+2
Convert usage of g_slist_append() to g_slist_prepend() where appropriate. gdbus, dnsproxy, resolver, rtnl, session and session unit test have ordering requirements and thus not touched.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-04 17:00:39 +0000