Skip to content

Commit

Permalink
Merge pull request #18 from joebobbio/main
Browse files Browse the repository at this point in the history
docs? better
  • Loading branch information
joebobbio authored Jun 29, 2023
2 parents b069905 + bb728f3 commit 09fede3
Show file tree
Hide file tree
Showing 4 changed files with 32 additions and 30 deletions.
1 change: 1 addition & 0 deletions docs/altos.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ nav_order: 9

## altOS Pros / Cons

-----------------------


**Windows:**
Expand Down
2 changes: 2 additions & 0 deletions docs/compiling-coreboot.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ nav_order: 16

### Cloning & Building ROMs

<br>

{: .warning }
Building and flashing your own firmware has the potential to brick your device. Do not do this unless you are sure you know what you're doing/have a way to recover from a bad flash. Some level of knowledge with using the Linux command line is required.

Expand Down
40 changes: 25 additions & 15 deletions docs/known-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,45 +8,55 @@ nav_order: 3
The following page is aimed for documenting all issues Chrultrabooks face. Feel free to improve this page by contributing to it.

{: .highlight }
You should avoid buying any device in this list.
You should avoid buying any devices in this list.

-----

## Devices:


### Intel:
* Samsung Chromebook 3 (CELES): Numerous hardware bugs
## Devices
* Samsung Chromebook 3 (CELES): Numerous hardware bugs that make it difficult to use.
* Samsung Galaxy Chromebook (KOHAKU): Badly designed hardware, deteriorating trackpad grounding, possibly faulty backlight circuit.
* Samsung Chromebox Series 3 (STUMPY): DisplayPort output is non-functional under Windows, and VGA output through the DVI port is non-functional.


### AMD:
* **All** AMD Chromebooks: AMD not caring to fix broken PSP blobs


### ARM:
----

## Firmware
* **All** AMD Chromebooks: AMD PSP blobs are broken, and some StoneyRidge devices do not have working Legacy Boot.
* **All** ARM Chromebooks: No support, though development is slowly starting.
* GeminiLake: Legacy boot mode/alternative firmware menu works but does not show payload list



----

## Operating Systems:
## Operating Systems

### Windows:
### Windows

(todo)
* No touchpad support in the installer
* No fingerprint reader support
* No TPM support
* No IPU camera support


### Linux:
### Linux

(todo)
* Broken USB-C on TigerLake and AlderLake (although there is a workaround)
* No fingerprint reader support



### macOS:
### macOS


(todo)
* Broken DRM
* No audio
* No PCIe SD card reader support
* No fingerprint reader support
* Continuity features (AirDrop, Sidecar, etc)


-----
19 changes: 4 additions & 15 deletions docs/supported-devices.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ nav_order: 6
---

## Supported Devices and Platforms
Supported devices are listed in the table below, grouped by platform/family, roughly in chronological order. To reiterate, support is determined entirely and exclusively by the Board Name. Device Names are just for reference, and may be incomplete as many models/sub-models may use the same Board Name. Please don't email me asking if your HP Chromebook 14b-ca0023dx (eg) is supported. Figure out the Board Name and then locate it in the table. If it's not listed, it's not supported.
Supported devices are listed in the table below, grouped by platform/family, roughly in chronological order. To reiterate, support is determined entirely and exclusively by the Board Name. Device Names are just for reference, and may be incomplete as many models/sub-models may use the same Board Name. Figure out the Board Name and then locate it in the table. If it's not listed, it's not supported.

### Determining Device Support
What's in a name? All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anything else. The only thing that matters is the name, so use that when determining support in the table below (or for anything else really).
Expand All @@ -17,15 +17,15 @@ A device having firmware available (either RW_LEGACY or UEFI Full ROM) does not

---------

### Supported Platforms:
### Supported Platforms

| Intel | AMD | ARM |
| ---------------- | --------------------------------------------| ------------- |
| Intel platforms have good support for both Linux and Windows. | Ryzen needs RWL hack in order to install Windows. Stoney is not supported in Windows at all, and has a few issues when running Linux. | Currently unsupported by Windows. [PostmarketOS](https://wiki.postmarketos.org/wiki/Chrome_OS_devices) has support for a few ARM Chromebooks. |

---------

### Firmware (not OS) support for each device.
### Firmware (not OS) support for each device

{: .highlight }
If your device isn't listed, it doesn't have custom firmware support.
Expand Down Expand Up @@ -3333,20 +3333,9 @@ If your device isn't listed, it doesn't have custom firmware support.

</tbody></table>

-----

### Notes:
* STUMPY: The DisplayPort outputs don't seem functional under Windows, but work fine pre-OS and under Linux.
* VGA output (via DVI port) is not functional.
* CELES: Running Windows on CELES requires a post-install workaround.
* CELES can be a highly problematic device running OSes other than ChromeOS. Highly recommended to avoid.
* AMD: Some StoneyRidge devices (CAREENA? BARLA?) may not currently have functional Legacy Boot Mode due to bugs in Google's firmware.
* GeminiLake legacy boot mode/alternative firmware menu works but does not show payload list

//todo: relink footnotes to ### Notes

----
Originally from https://mrchromebox.tech/#devices
Adapted from https://mrchromebox.tech/#devices

<table>
<tr>
Expand Down

0 comments on commit 09fede3

Please sign in to comment.