Preferences

That means nothing for the community who may need or want to fix and patch issues on their own. Instead we're beholden to Qualcomm to fix major issues on an OS it may or may not care about supporting. It also excludes other open source operating systems such as the BSD's who have to then reverse engineer the undocumented Linux drivers.

A better question: can a small company like Framework or even MNT Research build and support an open laptop around this chip?


While not this chip, MNT Research has been working on a processor module for Qualcomm Dragonwing QCS6490 and is manufacturing the first wave of test PCBs now:

https://source.mnt.re/reform/reform-qcs6490

Framework doesn't even develop their own firmware; most of the engineering in PCs is done by Intel/AMD/ODMs/IBVs. The whole ecosystem is based on vendor support not datasheets.
Firmware is not preventing Framework or anyone from offering a repairable laptop. Firmware also doesn't matter once the kernel is loaded. We need the datasheets.
"Firmware doesn't matter once the kernel is loaded".

ACPI enters the chat... It can send pieces of code interpreted by the kernel on any hardware event.

I have a Framework laptop and yeah the ACPI firmware is totally buggy and the Linux kernel fails at interpreting it in various cases.

I was under the impression that the firmware is responsible for loading the ACPI tables but the OS takes over and runs the code in its ACPI VM once running.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal