Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate qubes-hcl-report and web page table for 4.x requirements #3214
Comments
andrewdavidwong
added
C: other
C: website
enhancement
labels
Oct 26, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 26, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Oct 26, 2017
FWIW, web page already shows SLAT.
Remap is collected, but not yet shown. I'm guessing this one is important...
Non-USB keyboard isn't strictly necessary to use R4, but I know there is an Issue somewhere to collect that data.
'USB connected mic' is intriguing, but is this necessary?
Overall, this + other suggested additions may be too much detail to fit in the main table. But perhaps some kind of tooltip or pop-over could be used.
tasket
commented
Oct 26, 2017
|
FWIW, web page already shows SLAT. Remap is collected, but not yet shown. I'm guessing this one is important... Non-USB keyboard isn't strictly necessary to use R4, but I know there is an Issue somewhere to collect that data. 'USB connected mic' is intriguing, but is this necessary? Overall, this + other suggested additions may be too much detail to fit in the main table. But perhaps some kind of tooltip or pop-over could be used. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
GnstheGrain
Oct 26, 2017
FWIW, web page already shows SLAT.
the web page only mention weither or not the HW includes that feature or not. My sheet add a Subdivision to each of those required features, in order to reflect the updated 4x requirements which says that not only the HW must include those features, they must all be properly detected & exposed in the bios.
But perhaps some kind of tooltip or pop-over could be used ?
Totally agree. Will add some tonight. (feel free to add some yourself as well, i'm clearly not the Qubes expert here)
'USB connected mic' is intriguing, but is this necessary?
This is part of updated Qubes's Certified Hardware requirements for the upcoming Qubes 4.x branch
see: https://www.qubes-os.org/news/2016/07/21/new-hw-certification-for-q4/
But this column's title could be reformulated. (or have some tooltip added for precision)
On a side note, Qubes seems to seperate the requirements for the Compatibility list's from those
of the Certified Hardware ones. It's only my personal opinion that those requirements should be merged into the HCL table as well. Perhaps, some visual indication to let the viewer know which requirements stems from either the Certified requirements list vs the compatibility one should be added.
I've made the Spreadsheet open for anyone to edit. I'm no expert so please feel free to edit at will.
GnstheGrain
commented
Oct 26, 2017
•
the web page only mention weither or not the HW includes that feature or not. My sheet add a Subdivision to each of those required features, in order to reflect the updated 4x requirements which says that not only the HW must include those features, they must all be properly detected & exposed in the bios.
Totally agree. Will add some tonight. (feel free to add some yourself as well, i'm clearly not the Qubes expert here)
This is part of updated Qubes's Certified Hardware requirements for the upcoming Qubes 4.x branch On a side note, Qubes seems to seperate the requirements for the Compatibility list's from those I've made the Spreadsheet open for anyone to edit. I'm no expert so please feel free to edit at will. |
andrewdavidwong commentedOct 26, 2017
•
edited
Edited 2 times
-
andrewdavidwong
edited Oct 26, 2017 (most recent)
-
andrewdavidwong
edited Oct 26, 2017
Twitter user @gnsthegrn has suggested that we update the HCL web page table for the new 4.x requirements and provided this example Google spreadsheet.
This would require that we update the
qubes-hcl-reporttool in order to gather the new data. It already checks for SLAT now, but perhaps other things are missing.What do you think, @marmarek and @Zrubi?
Potentially related issues: #2214