Subversion Repositories HelenOS

Rev

Go to most recent revision | Show changed files | Directory listing | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
3674 5592 d 11 h svoboda /branches/dynload/ Merge latest trunk changes to dynload.  
3569 5619 d 22 h svoboda /branches/dynload/ Merge latest trunk changes into dynload.  
3211 5743 d 23 h svoboda /branches/dynload/ Merge latest trunk changes into dynload  
3150 5764 d 20 h svoboda /branches/dynload/ Merge trunk changes up to r3090 into dynload (still broken)  
2927 5797 d 0 h decky /branches/dynload/ added dynload branch  
2678 5932 d 16 h jermar /trunk/uspace/ The IPC_M_SHARE_* and IPC_M_DATA_* calls pass through 3 stages. Rename the send,
receive and deliver wrappers to names ending with 'start', 'receive' and
'finalize', respectively. This should make it clearer for dummies.
 
2677 5932 d 17 h jermar /trunk/ Rename IPC_M_AS_AREA_SEND to IPC_M_SHARE_OUT. Rename IPC_M_AS_AREA_RECV to
IPC_M_SHARE_IN. Provide user-friendly wrappers for these methods so that even
dummies can get it right. Some applications using simpler protocols still use
these methods directly.
 
2637 5959 d 14 h cejka /trunk/ Extended IPC_M_CONNECT_TO_ME to use 3 user defined parameters.
Phone identifier is passed in ARG5.
 
2635 5961 d 14 h cejka /trunk/ Function ipc_connect_me_to sends 3 user defined arguments now.
One argument added also to ipc_forward_fast.
Fixed devmap and improved its test.
 
2621 5971 d 18 h jermar /trunk/uspace/ Modify the async framework to make use of all six syscall arguments.
Supply user-friendly macros as in previous cases.
 
2619 5973 d 12 h jermar /trunk/ Modify ipc_answer_*() to make use of all six syscall arguments. The recommended
means of answering calls is via the ipc_answer_m() macros (where m denotes the
number of return arguments) that automatically decide between the fast register
version or the slow universal version of ipc_answer().
 
2618 5974 d 0 h jermar /trunk/ Modify asynchronous IPC to make use of all six syscall arguments. The preferred
means of asynchronous communication is now via the set of ipc_call_async_m()
macros, where m is the number of payload arguments passed to the kernel. These
macros will automatically decide between the fast and the universal slow version
of ipc_call_async.
 
2566 6022 d 3 h jermar /trunk/uspace/srv/console/ Fix cstyle in console.c.  
2539 6028 d 18 h jermar /trunk/uspace/srv/console/ Cstyle and other minor fixes in the console code.  
2479 6123 d 20 h jermar /trunk/ New, better-structured, directory layout for uspace.  
2071 6280 d 13 h jermar /trunk/ (c) versus (C)  
2070 6280 d 21 h jermar /trunk/ Rather big indentation and formatting changes.
More inteligent long line wrapping.
 
2069 6282 d 11 h jermar /trunk/ Improve formatting.  
2025 6317 d 10 h jermar /trunk/ Coding style fixes.  
1867 6415 d 13 h jermar /trunk/uspace/ Prototype for mmap() should be in mman.h.
Anyway, is there any common sense behind naming of mman.h and mman.c?
 

Show All