Samsung Chromebook 2 XE503C32

From Linux Exynos
Revision as of 19:55, 18 July 2016 by Wizzup (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This page or section is a stub. Ask how you can help improve by sending an e-mail to the mailing list, or by visiting #linux-exynos, or if you are able to contribute to the current page, then you are welcome to do so.

Samsung Chromebook 2 XE503C32
XE503C32 Front.jpg
Manufacturer Samsung
Codename Peach Pi
Dimensions 323 x 224 x 17 mm
Release Date May, 2014
SoC Samsung Exynos 5800
Power Texas Instruments TPS65090 power management unit, Maxim MAX77802 power management IC, 40W AC adapter, 2-cell li-polymer battery (30Wh)
LCD 13.3" 1920x1080
Video Pulse-Width Modulation Backlight, Parade PS8622 - eDP to LVDS bridge, HDMI
Audio Maxim MAX98091, 2x 2W speaker, internal microphone, 3.5mm headphone jack, HDMI digital
Network Marvell WiFi SD8897 802.11 ac/b/g/n, Bluetooth 4.0
Storage 16 GiB SSD via eMMC, MicroSD
USB (Host/OTG) USB 2.0 Host, USB 3.0 Host
Camera 720p
Sensors Intersil ISL29018 sensor light
Other Infineon SLB9635TT TPM




Mainline Linux (Linux 4.2 + enabled fw loader user fallback) supports the following features:

Feature Mainline Linux Kernel
Serial Yes
USB2 Yes
USB3 Mostly - may have some stability issues
eMMC Yes
Display Yes
Keyboard Yes
Touchpad Yes
Clock Seems to work
Webcam Yes (at least on 4.5)
Wifi Yes
HDMI Yes - and in X HDMI can be a separate (not just mirror) screen (using xf86-video-modesetting)
Audio Detected, produces sound, not accurate
G2D (2D acceleration)  ???
Mali (3D Acceleration)  ???
MFC (Video encoding/decoding)  ???
Suspend Yes (Since 4.2)
u-boot version supported
ChromeOS specific Yes
Mainline Yes (peach-pi_defconfig)

SeeSamsung_Chromebook_2_XE503C12/Mainline_Linux_Kernel for a guide on how to build the kernel.



In order to get Wi-Fi to work, you'll have to download the following firmware blob and install it into /lib/firmware.


I use a loadaddr of 0x42000000 to boot a uImage from nv-uboot.

If someone is interested in the firmware blobs (the ones that have to be fetched), the following is a listing of those with links (alternatively, you can also browse this listing to get an idea):