#avr Logs

Aug 27 2019

03:12 AM janco_ is now known as janco
03:27 AM vmt: day: you've still been unable to tell me what's the crucial security angle in terms of game consoles
03:49 AM skz81: <day> [...] how does femtoOS prevent a program from accessing the hardware/memory directly? >> Memory protection is a HW feature. Either full MMU with address virtualization, or a light weight MPU that allow a given task to access some pages (using real addresses)
03:58 AM vmt: skz81: you *could* implement it in software too, kind of... for maximum idiocy
04:17 AM vmt: well, you can't implement mmu/mpu functionality completely, no
04:24 AM cehteh: catch every instruction with a debug trap :D
04:25 AM cehteh: not on avr's but some archs can do that
04:27 AM cehteh: day: on a microcontroller the very small OSes are about resource sharing and management, not security you can still shoot in your foot
04:30 AM vmt: ...not to mention the resources on an mcu are scarce enough not to warrant an "operating system" of any kind on it
04:30 AM vmt: though, you could call your implementation an operating system but that's just kind of nitpicking
04:33 AM cehteh: yeah
04:34 AM cehteh: mµscheduler sounds dumb thus i named it mµOS :D
04:35 AM cehteh: there isnt some definitive point where something starts to be an OS
04:38 AM cehteh: the overhead of a so-called OS becomes justified when it safes things on the other side, like almost all timinig, even from distinct parts of a program can use a single hardware timer for scheduling
04:38 AM cehteh: or io is properly locked and serialized by the api
04:48 AM Helle: look up co-operative multitasking
04:49 AM skz81: or that : https://github.com/zserge/pt
04:51 AM vmt: highly curious of the use-cases here
05:15 AM cehteh: Helle: thats what i am doing
05:16 AM cehteh: not protothreads because they are just too ugly
06:27 AM proteusguy is now known as proteusdude
07:26 PM day__ is now known as day
07:42 PM day__ is now known as day
11:32 PM day__ is now known as day