Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream devices #4

Open
paulmenzel opened this issue Jan 4, 2023 · 2 comments
Open

Upstream devices #4

paulmenzel opened this issue Jan 4, 2023 · 2 comments

Comments

@paulmenzel
Copy link

It’d be great, if you upstreamed the devices to the coreboot project.

@daringer
Copy link
Collaborator

daringer commented Jan 9, 2023

I did not have the impression that these qualify as separate "devices", as all of them are either re-branded from existing upstream devices (nitropc) or from the dasharo repo (nitrowall/nitrowall pro). In detail these are more or less pre-configured with the biggest change being the PL1+2 for one of them inside the devicetree.cb.

Am I judging this wrong? Would this qualify for new devices on coreboot upstream?

@paulmenzel
Copy link
Author

In detail these are more or less pre-configured with the biggest change being the PL1+2 for one of them inside the devicetree.cb.

Can you elaborate please?

Am I judging this wrong? Would this qualify for new devices on coreboot upstream?

At least it would qualify as a variant. If it’s just rebranding, then it’d be great, if the name NitroPC would show up in the documentation and Kconfig description. The goal should be, that the firmware for a device can be easily built from the upstream sources with the upstream build system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants