Changes between Version 109 and Version 110 of GSoC/2017

Timestamp:

07/19/17 14:51:04 (7 years ago)

Author:

Sichen Zhao

Comment:

--

GSoC/2017

@@ -272 +272 @@
  * Regarding the WPA: It is much harder than WEP. On Linux, BSD, Windows and other OS, WPA is managed by wpa_supplicant software. So we need port wpa_supplicant on RTEMS.
  * Currently, we think there are some difficult points during the porting:
- * 1. "Big" operating systems like Linux, BSD or Windows clean up when a process terminates. RTEMS doesn't have a process separation (at least not on most targets).
-Therefore all programs have to take care to free their resources before they exit. The normal way for services is to thoroughly review them for any mallocs that are not freed again and for every open that has no close. So that will be one point of the port. Reviewing the code for resource leaks.
+ * 1. "Big" operating systems like Linux, BSD or Windows clean up when a process terminates. RTEMS doesn't have a process separation (at least not on most targets). Therefore all programs have to take care to free their resources before they exit. The normal way for services is to thoroughly review them for any mallocs that are not freed again and for every open that has no close. So that will be one point of the port. Reviewing the code for resource leaks.
  * 2.RTEMS lacks of any memory protection (again: on most targets). That causes problems with every global variable. I'm not sure if it is possible that multiple instances of wpa_supplicant can run at the same time. That might could be necessary for multiple WiFi interfaces. But if it is, we can't have any global variables. So that is the second big part.
  * Next week, i will working on the porting wpa_supplicant.