Until now, the valid configuration object's location was not stored, so it had to be looked up every time pdb_config_flash_read was called. Now the valid object's location is stored in config_cur, which is updated every time the configuration's location changes. This means that pdb_config_flash_read only has to do the full routine the first time it's called, or after pdb_config_flash_erase is run. Now other parts of the configuration won't have to cache the location themselves anymore.
|
|
||
27 |
|
27 |
|
28 |
|
28 |
|
29 |
|
29 |
|
|
30 |
|
|
|
31 |
|
|
|
32 |
|
|
|
33 |
|
|
30 |
|
34 |
|
31 |
|
35 |
|
32 |
|
36 |
|
|
|
||
170 |
|
174 |
|
171 |
|
175 |
|
172 |
|
176 |
|
|
177 |
|
|
|
178 |
|
|
|
179 |
|
|
173 |
|
180 |
|
174 |
|
181 |
|
175 |
|
182 |
|
|
|
||
213 |
|
220 |
|
214 |
|
221 |
|
215 |
|
222 |
|
|
223 |
|
|
|
224 |
|
|
|
225 |
|
|
216 |
|
226 |
|
217 |
|
227 |
|
218 |
|
228 |
|
219 |
|
229 |
|
220 |
|
230 |
|
221 |
|
231 |
|
|
232 |
|
|
|
233 |
|
|
|
234 |
|
|
|
235 |
|
|
|
236 |
|
|
|
237 |
|
|
|
238 |
|
|
|
239 |
|
|
222 |
|
240 |
|
223 |
|
241 |
|
224 |
|
242 |
|
|
|
||
228 |
|
246 |
|
229 |
|
247 |
|
230 |
|
248 |
|
231 |
|
|
|
|
249 |
|
|
|
250 |
|
|
232 |
|
251 |
|
233 |
|
252 |
|
234 |
|
253 |
|