- Timestamp:
-
08/04/19 11:34:07 (5 years ago)
- Author:
-
Nils Hölscher
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v65
|
v66
|
|
247 | 247 | * Next : |
248 | 248 | * Initializing driver in sample App. |
249 | | * Loading first code to PRU, |
250 | | |
| 249 | * Loading first code to PRU. |
| 250 | |
| 251 | * July 24 |
| 252 | * Progress so far : |
| 253 | * Ported the BSD pruss driver over to rtems-libbsd. |
| 254 | * Moved the driver from my application to the rtems-libbsd repository, it makes more sense to develop it there, I think. |
| 255 | * Blockers/Questions: |
| 256 | * I have got the solution to the clock driver module not loading just today, device tree again. However prcm still loads after the ti_pruss module. |
| 257 | * Next : |
| 258 | * Investigating FreeBSD init process in rtems. |
| 259 | |
| 260 | * July 31 |
| 261 | * Progress so far : |
| 262 | * Investigated libBSD init process in rtems |
| 263 | * Blockers/Questions: |
| 264 | * Need to figure out if it is fdt related or init process related. |
| 265 | * It seems like libbsd-rtems only iterates one time over the fdt. |
251 | 266 | == Vijay Kumar Banerjee == |
252 | 267 | |