24b1f269be
The intention of Packet_ref was to allow clients to place opaque references into the packet descriptor itself, which could be observed on packet completion. Currently no component in our sources uses this feature and beyond that it is questionable if it should be used at all: If the server tampers with the ref the client may easily be confused into observing an incorrect or invalid context. It seems better to remove the opaque context from the descriptor and leave the actual implementation to the client and its needs. |
||
|---|---|---|
| .. | ||
| blk_cache | ||
| dynamic_rom | ||
| fs_log | ||
| fs_rom | ||
| input_merger | ||
| iso9660 | ||
| loader | ||
| log_report | ||
| log_terminal | ||
| lx_fs | ||
| mixer | ||
| nic_bridge | ||
| nic_loopback | ||
| nit_fb | ||
| nitpicker | ||
| part_blk | ||
| ram_blk | ||
| ram_fs | ||
| report_rom | ||
| rom_blk | ||
| rom_prefetcher | ||
| tar_fs | ||
| tar_rom | ||
| terminal_crosslink | ||
| terminal_log | ||
| trace_fs | ||
| tz_vmm | ||
| vmm | ||