Hi Jakub,
what is the benefit of call_t being based on kobject? Isn't that making
thins unnecessarily complicated? Why would you want to, e.g. pass around a
call like a capability?
Best regards,
Jiri
---------- Původní e-mail ----------
Od: Jakub Jermář <[email protected]>
Komu: [email protected]
Datum: 9. 11. 2017 23:50:54
Předmět: [HelenOS-devel] Minutes of today's hangout
"JJ:
- started kobject type for call_t, not finished yet
- fixed phone and irq kobject and capability leak on task destruction
- added recursive mutex
JZr: missing some barriers?
- analyzing and fixing ticket #700
JS:
- conversion of legacy drivers to use DDF
- devctl manual unload of driver
JJi:
- C++, have worked for 1 month, 14000 LOC
- io, algorithm, containers
- tests + tesing framework
- pcut cannot handle iterators
OH:
- XHCI: QEMU + XHCI + mouse
- JJi plans QEMU device with endpoints with all types, measure
bandwidth, test functionality
- control + interrupt transfers work, bulk transfers unknown,
isochronous not implemented
JZr:
- breaking Makefiles
- plans libuv for coastline
- plans to rationalize thread interface usable with async framework
- plans -helenos triplet for gcc and clang
VH:
- libmusl
- newly amd64 examples
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
"
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
