-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Generalize whiptail usage to all platforms #477
Comments
So your issue is making this a common goal of the project? FWIW I think it should be one. IMO this is essential for being broadly usable; especially so during setup. |
Comment deleted. Created #517 instead to track the issue. |
@merge : For the x230 board to become compatible with FBWhiptail, here were the required changes.
This is the list of board owners i've gathered from board config changes "blames". Can you test the above changes on the board config on those boards and adapt linux config files to activate FB and report? @osresearch : leopard, tioga |
leopard/tioga have no video cards at all, r630/s2600wf are almost always headless. |
So something like for the kgpe-d16 for all those.
…On February 8, 2019 4:17:05 PM EST, Trammell Hudson ***@***.***> wrote:
leopard/tioga have no video cards at all, r630/s2600wf are almost
always headless.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#477 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
whiptail is generalized for a while on all coreboot based platforms depending on heads for payload (this project). Otherwise, this issue is more related to linuxboot based boards which never really received any love here since linuxboot is based on u-root on its payload |
I think it might be a good time to replace generic-init by gui-init, and let the board configuration options define if FBWhiptail is desired but default to whiptail. I think that it would be a good base in improving the UX for everyone.
@kylerankin @osresearch @flammit : What do you think?
The text was updated successfully, but these errors were encountered: