Support/Braswell - Revision history

Crystal: libera.chat

2021-06-20T02:14:47Z

libera.chat

Reynhout at 18:25, 23 July 2018

2018-07-23T18:25:26Z

Reynhout at 02:40, 23 January 2017

2017-01-23T02:40:41Z

Reynhout at 20:30, 2 January 2017

2017-01-02T20:30:22Z

Reynhout at 20:12, 2 January 2017

2017-01-02T20:12:58Z

Reynhout at 19:47, 2 January 2017

2017-01-02T19:47:01Z

Matt Devo at 21:48, 6 August 2016

2016-08-06T21:48:30Z

Matt Devo at 21:47, 6 August 2016

2016-08-06T21:47:01Z

ColtonDRG at 08:20, 2 April 2016

2016-04-02T08:20:30Z

Reynhout: Created page with "Intel processors with Braswell cores are very new (Dec 2015) and only available in a very small number ChromeOS devices. Braswell seems to be positioned as the replacement for..."

2015-12-24T17:02:18Z

Created page with "Intel processors with Braswell cores are very new (Dec 2015) and only available in a very small number ChromeOS devices. Braswell seems to be positioned as the replacement for..."

New page

Intel processors with Braswell cores are very new (Dec 2015) and only available in a very small number ChromeOS devices. Braswell seems to be positioned as the replacement for Bay Trail, so this will likely change in 2016.

Factory firmware support for coreboot and SeaBIOS is uncertain but considered unlikely. Custom firmware is not presently available.

At the moment, your best option for running Linux on a Braswell ChromeOS device is probably Crouton.

@@ Line 24: / Line 24: @@
 A more casual approach is to ''carefully'' observe your Chromebook for unusual noises/heating around the speaker area while in use (or powered on), and be prepared to return any defective hardware within ordinary return windows if problems occur. We estimate the failure rate at about 2-3% of all devices, and the failure is expected to happen within a short period of use (minutes to single-digit hours).
-At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or that has adequate time remaining on the return window), and which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org or freenode [https://galliumos.org/irc #galliumos]). Thank you!
+At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or that has adequate time remaining on the return window), and which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org or Libera.chat [https://galliumos.org/irc #galliumos]). Thank you!
 <div style="border:1px solid #cccccc; padding:0 0 0 0.5em; margin:0 1em;">

@@ Line 6: / Line 6: @@
 <div style="margin:3em 0; padding:1em; border:1px solid #ff8888;">
-<span style="background-color:#ffcccc;padding:0.2em 0.4em">'''Important&nbsp;Note'''</span>
+<span style="background-color:#ffcccc;padding:0.2em 0.4em">'''Important&nbsp;Note'''</span> '''(Now RESOLVED -- see below for details)'''
 We have received several reports of '''hardware speaker damage''' in Braswell models with the Realtek ALC5650 audio chip. This includes most Braswells, '''except''' the Acer R11 Chromebook (CYAN), which has a Maxim MAX98090 chip instead.
@@ Line 25: / Line 25: @@
 At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or that has adequate time remaining on the return window), and which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org or freenode [https://galliumos.org/irc #galliumos]). Thank you!
 </div>

← Older revision		Revision as of 02:40, 23 January 2017
Line 13:		Line 13:

	When your Chromebook is powered on or rebooted, the ChromeOS bootloader (depthcharge) is loaded first, regardless of what operating system you will be running. Depthcharge performs the first initialization of the audio chip. The chip is re-initialized later by ChromeOS, but if the Chromebook is booted into another operating system instead (or not booted at all), no further initialization is performed. It is ''possible'' that depthcharge is leaving the chip in an inappropriate state, but that should not be an adequate explanation -- unless some percentage of the Realtek chips are faulty.		When your Chromebook is powered on or rebooted, the ChromeOS bootloader (depthcharge) is loaded first, regardless of what operating system you will be running. Depthcharge performs the first initialization of the audio chip. The chip is re-initialized later by ChromeOS, but if the Chromebook is booted into another operating system instead (or not booted at all), no further initialization is performed. It is ''possible'' that depthcharge is leaving the chip in an inappropriate state, but that should not be an adequate explanation -- unless some percentage of the Realtek chips are faulty.
		+
		+	<div style="border:1px solid #cccccc; padding:0 0 0 0.5em; margin:0 1em;">
		+	'''Update 20170118''': GalliumOS now includes audio drivers for the Realtek ALC5650, and so ''does'' perform additional initialization after depthcharge. This ''might'' reduce the risk of speaker damage, but of course the additional initialization is not performed until GalliumOS is booted -- so there remains a period of time between power-on and fully-booted where the chip is only initialized by depthcharge, and might be at risk. Other Linux distros '''do not''' include these drivers yet, but they should be in mainline kernels around version 4.11 or 4.12.
		+	</div>

	Full details and current speculation can be found on the GitHub [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation] ticket.		Full details and current speculation can be found on the GitHub [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation] ticket.

@@ Line 8: / Line 8: @@
 <span style="background-color:#ffcccc;padding:0.2em 0.4em">'''Important&nbsp;Note'''</span>
-We have received several reports of '''hardware speaker damage''' in models with the Realtek ALC5650 audio chip. This includes most Braswells, '''except''' the Acer R11 Chromeboom (CYAN), which has a Maxim MAX98090 chip instead.
+We have received several reports of '''hardware speaker damage''' in Braswell models with the Realtek ALC5650 audio chip. This includes most Braswells, '''except''' the Acer R11 Chromebook (CYAN), which has a Maxim MAX98090 chip instead.
-This issue is not limited to GalliumOS or Linux, but it seems to happen more frequently when the machine is ''not'' booted into ChromeOS (so at the dev mode screen, in firmware, in GRUB, or running Linux). The CromeOS bootloader (depthcharge) initializes the audio chip, and no further initialization is performed until ChromeOS is loaded. If ChromeOS is not loaded, no further initialization is performed at all. It is ''possible'' that depthcharge is leaving the chip in an inappropriate state, but that should not be an adequate explanation -- unless some percentage of the Realtek chips are faulty.
+This issue is not limited to GalliumOS or Linux, but it seems to happen more frequently when the machine is ''not'' booted into ChromeOS (i.e. at the Developer Mode screen, in firmware, in GRUB, or running Linux).
 Full details and current speculation can be found on the GitHub [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation] ticket.
-The ultra-cautious approach is to disconnect your Chromebook speakers until and unless the ultimate cause of the problem can be prevented.
+The cautious approach is to disconnect your Chromebook speakers until and unless the ultimate cause of the problem can be identified and avoided.
 A more casual approach is to ''carefully'' observe your Chromebook for unusual noises/heating around the speaker area while in use (or powered on), and be prepared to return any defective hardware within ordinary return windows if problems occur. We estimate the failure rate at about 2-3% of all devices, and the failure is expected to happen within a short period of use (minutes to single-digit hours).
-At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or you have adequate time remaining on your return window), which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org). Thank you!
+At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or that has adequate time remaining on the return window), and which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org or freenode [https://galliumos.org/irc #galliumos]). Thank you!
 </div>

@@ Line 9: / Line 9: @@
 We have received several reports of '''hardware speaker damage''' in models with the Realtek ALC5650 audio chip. This includes most Braswells, '''except''' the Acer R11 Chromeboom (CYAN), which has a Maxim MAX98090 chip instead.
 Full details and current speculation can be found on the GitHub [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation] ticket.
-The ultra-cautious approach is to disconnect your speakers until and unless the ultimate ultimate cause of the problem can be determined.
+The ultra-cautious approach is to disconnect your Chromebook speakers until and unless the ultimate cause of the problem can be prevented.
-A more casual approach is to ''carefully'' observe the device for unusual noises/heating around the speaker area while in use (or powered on), and be prepared to return any defective hardware within ordinary return windows if problems occur. We estimate the failure rate at about 2-3% of all devices, and the failure is expected to happen within a short period of use (minutes to single-digit hours).
+A more casual approach is to ''carefully'' observe your Chromebook for unusual noises/heating around the speaker area while in use (or powered on), and be prepared to return any defective hardware within ordinary return windows if problems occur. We estimate the failure rate at about 2-3% of all devices, and the failure is expected to happen within a short period of use (minutes to single-digit hours).
-At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return, and are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org)!
+At this time, and for reasons detailed at the aforementioned link, we suspect a hardware problem with the Realtek ALC5650 chips. We are still investigating. If you have a failed device that you have decided not to return (or you have adequate time remaining on your return window), which you are willing to let us borrow for a few days, please get in touch (contact. at. galliumos.org). Thank you!
 </div>

@@ Line 1: / Line 1: @@
-Intel processors with Braswell SoC's are new and available in a handful of ChromeOS devices. Braswell is positioned as the replacement for BayTrail, so more devices are forthcoming throughout 2016.
+Intel processors with Braswell SoC's are the replacement for the previous-generation Bay Trail family.
-Braswell support is in its infancy, the status of which can be seen [https://github.com/GalliumOS/galliumos-distro/issues/270 on the issue tracker here].
+Braswell support incomplete, but being tracked at GitHub: [https://github.com/GalliumOS/galliumos-distro/issues/270 Braswell Platform Validation]. You can subscribe to that ticket for the latest updates.
-Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for most (all?) Braswell models -- see [[Firmware]].
+Braswell models do not include firmware support for booting legacy OSes, but custom firmware is available -- see [[Firmware]].

← Older revision		Revision as of 21:48, 6 August 2016
Line 1:		Line 1:
	Intel processors with Braswell SoC's are new and available in a handful of ChromeOS devices. Braswell is positioned as the replacement for BayTrail, so more devices are forthcoming throughout 2016.		Intel processors with Braswell SoC's are new and available in a handful of ChromeOS devices. Braswell is positioned as the replacement for BayTrail, so more devices are forthcoming throughout 2016.
		+
		+	Braswell support is in its infancy, the status of which can be seen [https://github.com/GalliumOS/galliumos-distro/issues/270 on the issue tracker here].

	Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for most (all?) Braswell models -- see [[Firmware]].		Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for most (all?) Braswell models -- see [[Firmware]].

← Older revision		Revision as of 21:47, 6 August 2016
Line 1:		Line 1:
−	Intel processors with Braswell ~~cores~~ are ~~very~~ new ~~(Dec 2015)~~ and ~~only~~ available in a ~~very small number~~ ChromeOS devices. Braswell ~~seems to be~~ positioned as the replacement for ~~Bay Trail~~, so ~~this will likely change in~~ 2016.	+	Intel processors with Braswell SoC's are new and available in a handful of ChromeOS devices. Braswell is positioned as the replacement for BayTrail, so more devices are forthcoming throughout 2016.

−	Factory firmware support for ~~coreboot and~~ SeaBIOS is ~~uncertain~~ but ~~considered unlikely. Custom~~ firmware is ~~not presently~~ available.	+	Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for most (all?) Braswell models -- see [[Firmware]].
−
−	~~SeaBIOS support on Braswell may be possible, but there is no video BIOS, so SeaBIOS would not be able to initialize the GPU. GPU initialization on Braswell is handled by a UEFI GOP, and~~ for ~~that reason,~~ Braswell ~~support will likely be impossible until UEFI custom firmware becomes available and GalliumOS adds UEFI support. For more information about GalliumOS's plans for UEFI support,~~ see [[~~Support/UEFI~~]].
−
−	~~At the moment, your best option for running Linux on a Braswell ChromeOS device is probably Crouton~~.

← Older revision		Revision as of 08:20, 2 April 2016
Line 2:		Line 2:

	Factory firmware support for coreboot and SeaBIOS is uncertain but considered unlikely. Custom firmware is not presently available.		Factory firmware support for coreboot and SeaBIOS is uncertain but considered unlikely. Custom firmware is not presently available.
		+
		+	SeaBIOS support on Braswell may be possible, but there is no video BIOS, so SeaBIOS would not be able to initialize the GPU. GPU initialization on Braswell is handled by a UEFI GOP, and for that reason, Braswell support will likely be impossible until UEFI custom firmware becomes available and GalliumOS adds UEFI support. For more information about GalliumOS's plans for UEFI support, see [[Support/UEFI]].

	At the moment, your best option for running Linux on a Braswell ChromeOS device is probably Crouton.		At the moment, your best option for running Linux on a Braswell ChromeOS device is probably Crouton.