Changeset 362782e in rtems-libbsd for libbsd.txt
- Timestamp:
- 04/16/12 10:43:49 (12 years ago)
- Branches:
- 4.11, 5, 5-freebsd-12, 6-freebsd-12, freebsd-9.3, master
- Children:
- 459afb1
- Parents:
- 8a4f070
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
libbsd.txt
r8a4f070 r362782e 68 68 69 69 * linker section issues: I have undefined symbols for 70 _bsd__start_set_sysinit_set and _bsd__stop_set_sysinit_set.70 `_bsd__start_set_sysinit_set` and `_bsd__stop_set_sysinit_set`. 71 71 Is this the only type of new section magic? What about the old sysctl_set? 72 72 I added this to my linkcmds. … … 81 81 82 82 ---- 83 84 * Why is the interrupt server used? The BSD interrupt handlers can block on 85 synchronization primitives like mutexes. This is in contrast to RTEMS 86 interrupt service routines. The BSPs using the generic interrupt support must 87 implement the `bsp_interrupt_vector_enable()` and 88 `bsp_interrupt_vector_disable()` routines. They normally enable/disable a 89 particular interrupt source at the interrupt controller. This can be used to 90 implement the interrupt server. The interrupt server is a task that wakes-up 91 in case an associated interrupt happens. The interrupt source is disabled in 92 a generic interrupt handler that wakes-up the interrupt server task. Once the 93 postponed interrupt processing is performed in the interrupt server the 94 interrupt source is enabled again. 83 95 84 96 * Convert all BSP linkcmds to use a linkcmds.base so the sections are
Note: See TracChangeset
for help on using the changeset viewer.