FiXos issueshttps://lab.knightsofnii.com/fixos-core-team/fixos/-/issues2018-04-11T20:31:02Zhttps://lab.knightsofnii.com/fixos-core-team/fixos/-/issues/10Case Indication2018-04-11T20:31:02ZEiyeron FulmincendiiCase IndicationAs the keyboard is going to have multiple modes (Shift, Alpha, Alpha Lock and lower/upper cases), we'll need a way to share keyboard status to other devices/systems. How will it be done? An IOCtl call?
How the status will be shown on ...As the keyboard is going to have multiple modes (Shift, Alpha, Alpha Lock and lower/upper cases), we'll need a way to share keyboard status to other devices/systems. How will it be done? An IOCtl call?
How the status will be shown on the terminal? I have in mind two way :
- Changing the cursor (we'll need some bitmaps quite different from the font)
- Add an indicator on a corner when one of the modes is enabled. THis option has a bonus that we could keep the cursor for showing if we're on a insert/replace mode.https://lab.knightsofnii.com/fixos-core-team/fixos/-/issues/4Better dynamic linker2018-04-11T20:31:02ZLéo GrangeBetter dynamic linkerThe current dynamic linker, implemented in-kernel for userspace processes, is more a proof-of-concept than a very usable and powerful design.
We'll have to re-think it, and to determine if a *userspace* dynamic linker isn't a better sol...The current dynamic linker, implemented in-kernel for userspace processes, is more a proof-of-concept than a very usable and powerful design.
We'll have to re-think it, and to determine if a *userspace* dynamic linker isn't a better solution (its the one chosen by many mature OS).
In all cases, the current implementation is flawed because of :
- usage of external tools to create the FiXos-specific sections used to retrieve symbols and their addresses
- no way to provide an external variable from another (shared) object, only functions are linkable
- only one dynamic library by executable, and loaded at the same address each time (not a big deal to change that, but it's a current issue)
0.3