qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<pie_> lejonet: ahaa
MichaelRaskin has quit [Quit: MichaelRaskin]
vilhalmer has quit [Quit: :qa!]
vilhalmer has joined #spectrum
cole-h has quit [Ping timeout: 260 seconds]
nicoo has quit [Remote host closed the connection]
nicoo has joined #spectrum
<Profpatsch> > We just compiled the first working program using a Reduced Binary Seed bootstrap'ped*) TinyCC for ARM:
<Profpatsch> 21:55:01 janneke@banana:~/src/tinycc [env]
<Profpatsch> $ ./mes-tcc-hello
<Profpatsch> Hello, Mescc!
<Profpatsch> [42]
<qyliss> !!
<qyliss> At some point it would be interesting to evaluate whether we'd be better using cloud-hypervisor and porting the bits we need from crosvm, than the other way around.
cation21- has joined #spectrum
cation21 has quit [Ping timeout: 260 seconds]
cation21- is now known as cation21
<IdleBot_6d92ac96> What cloud-hypervisor has better?
<qyliss> Code is much cleaner, has hotplugging and vhost-user
<IdleBot_6d92ac96> The drawback, I guess, being that a part of the dirty code in CrosVM is device support?
<qyliss> Well, the device API is actually basically the same
<qyliss> so it's reasonable to move device code between the two
ehmry has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cole-h has joined #spectrum
ehmry has joined #spectrum
kylie has joined #spectrum