jackpot51

No, I do not. Redox OS is hard to install permanently (there is no easy installer yet). Most of us are running Redox OS in a VM, with occasional experiments on real hardware.

The next priorities will be to make the image installable, and to improve how rustc runs on Redox (for self-hosting). After that, it will be easier to develop on Redox OS and work on porting larger pieces of software like Firefox.

I am Jeremy Soller, the creator of Redox OS, please ask me anything!

She

I talked privately with others, and am fairly sure suicide was the cause of death. There were attempts in the past that I was unaware of until right before I wrote this article. I don't see what your point really is with this comment, but I expect just as much from hacker news.

There is an automatic reset to bootloader feature that will be removed prior to production, customer units will always require a physical keypress (Fn+ESC) in order to flash firmware: https://github.com/system76/launch/issues/17

Would you mind creating a GitHub issue to track this on? We may decide to change the behavior before production

EDIT: I have created an issue here: https://github.com/system76/launch/issues/17

We do not intend for the production firmware to include any software reset to bootloader functionality. It will require a physical keypress (Fn+ESC)

The fuck? It is an in house design and hase three USB-C ports, two USB-A ports, all connected through a USB 3.2 Gen 2 hub

Port DRM drivers to userspace and use mesa, probably

iwlwifi, a more complete USB stack, i2c hid, graphics acceleration.

What does work is pretty cool though. Ethernet, input, non-accelerated graphics, nvme and ahci storage

Next up is probably a graphical installer

I am Jeremy Soller, the creator of Redox OS, please let me know if you have questions!

Things like this typically require a monolithic kernel.

NetBSD's rump kernel drivers might be portable to userspace

An update to our gitlab server changed the link, it's fixed now:

https://gitlab.redox-os.org/redox-os/redox/-/releases

Thank you!

core is very comprehensive and alloc adds dynamic allocation once your kernel supports a heap. The complicated data structures in kernels are much easier to write in Rust, in my opinion. And you can be certain of their consistency when you have multiple cores running kernel code because of the ownership model.

I prefer doing bare metal development in Rust if possible

The default shell is ion, a shell written in Rust and maintained as part of Redox. But I don't see it as important what the default is, so long as it is configurable.

We have ported bash and dash, so far. I think porting nushell wouldn't take much work

The microkernel seems long forgotten to me, it is critical for improving security

At some point? Maybe. It would be in quite a long time. Right now writing drivers, porting software, and improving documentation are areas to help.

I'm Jeremy Soller, the creator of Redox OS. Let me know if you have questions!

We will be working on stacking support soon

This is inaccurate, the Lemur Pro supports charging through USB-C with a dead battery.

No, it is not possible to boot a Comet Lake Intel CPU without blobs.

The NVRAM is preserved on firmware updates with this new firmware, so that could fix this issue but I have not encountered it before. Usually it is recommended to install Windows first, and then install Pop!_OS - so that the Windows bootloader has not taken over the default location. Is that how you installed?

oreboot does not support x86 at this time, and does not plan to.

The update to users.html was merged and will be there shortly: https://review.coreboot.org/c/homepage/+/35957/1

Glad to hear that. I certainly like working with laptops, desktops, and servers across a wide spectrum of hardware - from the Galago Pro to the Thelio Massive

Yes, that is me. Here's the right link though ;-)

https://gitlab.redox-os.org/redox-os/redox/-/graphs/master

We will be looking into supporting older models starting with the darp5 and galp3-c.

A few things are going on here.

libgfxinit support for Comet Lake is coming. The Intel GOP driver is a bit different than this, though. There is an Intel PEIM graphics driver that comes from the PSP, that provides a software-rendering framebuffer similar to what libgfxinit does. The Intel GOP driver provides some hardware acceleration, which is useful especially for HiDPI systems but not critical to device functionality.

The HAP bit does not have an effect since ME version 12. ME 12 was used on Coffee Lake systems, and ME 14 is used on Comet Lake systems. These support a different method of disablement using a HECI message, presumably to make dynamic disabling of the ME easier to do. Our firmware always sends this message, having the same effect as setting the HAP bit.

me_cleaner does not appear to function on version 14 of the ME. As soon as it does, we will also utilize me_cleaner to remove ME modules.