ONYX BOOX Go 6 (onyx-go6)
Appearance
Onyx BOOX Go 6 Onyx BOOX Go 6 | |
Manufacturer | ONYX BOOX |
---|---|
Name | Go 6 |
Codename | onyx-go6 |
Model | Go6 |
Released | 2023 |
Type | ebook reader |
Hardware | |
Chipset | Qualcomm Snapdragon 662 (SM6115) |
CPU | 4x Kryo 260 Gold @ 2.0 GHz + 4x Kryo 260 Silver @ 1.8 GHz |
GPU | Adreno 610 |
Display | 6" Carta 1300 (1448x1072) |
Storage | 32GB |
Memory | 2GB |
Architecture | aarch64 |
Software | |
Original software | Android |
Original version | 11 |
postmarketOS | |
Category | testing |
Pre-built images | no |
Unixbench Whet/Dhry score | 0.0 |
This device is marked as not booting.
Device owners
Notes
I (User:Knuxify) haven't fully looked into this device yet; here's some information I've gathered from a brief look:
- ONYX BOOX notably does not release kernel sources for their products; as such, using a downstream kernel is likely out of the question.
- Using mainline may not be easy either; while the SoC appears to be supported, I don't know how the display is connected. Some other SoCs (e.g. the chip used in the PineNote) have dedicated EPD control chips for e-paper displays, which are not supported in mainline (there was an attempt to add DRM helpers for EPD chips in general, but it never got followed up on past its initial submission in 2022). TODO - How do the various kobo e-readers handle this? Don't they run mainline?
- There is no proper codename for this device, it seems; Android reports the hardware field as "BOOX", and the DTB compatibles appear to be taken from a dev board, "bengal-idp", with "BOOX" added at the end (TODO verify with a dumped DTB instead of reading contents of
/proc/cmdline
- You can reboot to EDL mode with
adb reboot edl
, and it seems to be fully functional (or at least, it can read/write to the eMMC).adb reboot bootloader
reboots to the bootloader (fastboot), but all commands return "unknown command".
Components
Element type | Element | In mainline? | Works? | Notes |
---|---|---|---|---|
Chipset | Qualcomm Snapdragon 662 (SM6115) | Y | Supported in mainline | |
Backlight | ??? (onyx,backlight), Texas Instruments LM3630A? | ? | No idea what the exact model is, downstream handles this through the "onyx,backlight" driver. Exposes two separate controls - "onyx_bl_br" for brightness and "onyx_bl_ct" for color temperature. A separate driver is also enabled - lm3630a (at i2c bus 0 @ 0x38) - but while the device is present at that address, it's not yet clear whether it actually controls the backlight (notably, it's a driver for white LEDs and does not provide any sort of color control - to check?) | |
E-Ink display | ??? | N | Driven by an Onyx-specific "software EPDC" driver. | |
EBC | tc358762 (Toshiba TC358762?) | Y | According to the internet, this is a DSI <-> DPI/DBI bridge chip, which might hint at how the display is connected. EBC might stand for "E-Book Controller" like it does on Rockchip chips. | |
Hall effect sensor | GPIO | Y | Uses onyx,onyx-hall driver downstream but appears to be a regular GPIO-controlled sensor. TODO. | |
Touchscreen | Focaltech FTS (FT5436?) | P | DTS lists chip type to 0x54360402, according to this random file I found it appears to correspond to the FT5436. There was a mainline driver submitted for FTS chips, but doesn't have a compatible for this particular model; most likely it's very similar, though. | |
Display PMIC | Texas Instruments TPS6518x | N | "PMIC for E Ink"; provides some regulators. | |
USB-C mux | Fairchild Semiconductor FSA4480 | Y | Presumably required for USB-C audio dongles. | |
PMIC | Qualcomm PM6125/PMI632 (SMB5?) | Y | Both PM6125 and PMI632 are supported. Not 100% sure if PMI632 is configured correctly (some errors in dmesg?), but PM6125 is used for most regulators. | |
WiFi/Bluetooth | Qualcomm WCN3950? / WCNSS | N | Found in string extracted from bluetooth_a partition dump. Not 100% sure if it's the correct chip yet. |