From Fedora Project Wiki

Revision as of 12:34, 14 July 2017 by Jreznik (talk | contribs) (Ready for FESCo)

Improved Bay- and Cherry-Trail device support

Summary

Improve support for hardware using Intel Bay Trail and Cherry Trail SoCs.

Owner

Current status

  • Targeted release: Fedora 27
  • Last updated: 2017-07-14
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

There are many affordable x86 laptops / tablets using Intel Bay Trail and Cherry Trail SoCs this change is about improving support for these SoCs and the peripherals typically found on devices with these SoCs. Examples of improvements in progress are fixing battery monitoring, touchscreen, audio and accelerometers (sometimes) not working.

Benefit to Fedora

Making Fedora work (better) on this hardware.

Scope

  • Proposal owners:
    • Most of the work on this is kernel work and most of this is being done upstream
    • The Fedora kernel package needs to have the right drivers enabled as well as some patches backported
    • Some small userspace changes like adding new entries to hwdb for accelerometer orientation
  • Other developers: The non-upstream kernel and hwdb changes need to be coordinated with their resp. package owners
  • Release engineering: [1] (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

All changes are in base packages, so on upgrade all users will automatically get these improvements

How To Test

  1. Take a device with an Intel Bay- or Cherry-Trail SoC
  2. Install Fedora 27 on it
  3. Everything, except for the (web)cameras which are not supported, should work normally. See here for a list of possible things to test.

User Experience

Users of Intel Bay- or Cherry-Trail devices may see the following improvements:

  • LCD panel working
  • Wifi working
  • Battery monitoring working
  • Touchscreen working
  • Accelerometer working

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: The changes consist of small fixes in various places, these will get added when ready. Fixes which are not ready in time will be added at a later time through updates or in the next release.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change)

Documentation

N/A (not a System Wide Change)

Release Notes

TODO