Tails

#1 Updated by sajolida 2017-09-19 10:57:56

• Category set to Hardware support
• Target version set to Tails_3.2

#2 Updated by sajolida 2017-09-22 12:17:09

• Assignee changed from sajolida to intrigeri
• QA Check set to Ready for QA
• Feature Branch set to doc/14689-cherry-trail-tablet

Here is a branch. Reassigning to the Foundations team so they can check that I’m not saying silly things (trying to learn what this ‘Cherry Trail’ is all about…).

#3 Updated by sajolida 2017-09-22 12:18:36

• blocks Feature #13423: Core work 2017Q3: Technical writing added

#4 Updated by sajolida 2017-09-22 12:49:43

• Status changed from Confirmed to In Progress

Applied in changeset commit:b89140ec93514c69e60f62f6ddb58bf7d2d281c3.

#5 Updated by intrigeri 2017-09-22 12:51:54

• Assignee changed from intrigeri to sajolida
• % Done changed from 0 to 90
• QA Check changed from Ready for QA to Pass

I’ve tried to understand if the Cherry Trail SoC includes its own sound and Wi-Fi controllers (otherwise, support depends on what sound/Wi-Fi hardware the computer vendor has added). At least it seems to embed a sound controller, for which we’re shipping the firmware in Tails 3.1. Wrt. kernel drivers I see lots of improvements in Cherry Trail support are coming in Linux 4.13 and 4.14, which we’ll likely ship in our January 2018 release. So the proposed doc seems OK, but it will probably be quickly outdated => perhaps file a ticket to update it in time for our January release, depending on what kernel version we ship? Ideally we would have a contact address of someone who can test then and confirm that stuff improves.

With this in mind, feel free to merge :)

#6 Updated by sajolida 2017-09-23 11:08:16

• related to Feature #14709: Remove known issue about Atom Cherry Trail added

#7 Updated by sajolida 2017-09-23 11:11:36

• Status changed from In Progress to Resolved
• Assignee deleted (sajolida)
• QA Check deleted (Pass)

Created Feature #14709 and merged.

NB: I also didn’t know about whether the chip included its own sound and Wi-Fi controllers but thought that this should have been investigated before handing this to me (so I didn’t look that hard). I searched online to understand what this “Cherry Trail” was all about because the initial formulation sounded very obscure to me but I didn’t verify the technical correctness of the initial claim.

#9 Updated by goupille 2017-10-01 12:38:28

• Status changed from Resolved to Confirmed
• Assignee set to sajolida
• Target version changed from Tails_3.2 to Tails_3.3

sorry for the assigning mess…

I just saw that the known-issues entry is talking about “tablets”, however I specificaly used the word computer, since some of the hardware equiped with cherry trails (like the Asus Vivostick TS10) are a kind of pocket-size PC that you plug in the hdmi port of a TV (http://store.asus.com/us/item/201604AM200000016/ASUS+VivoStick+TS10-B017D+Intel+Atom+2GB+32GB+eMMC+Stick+PC).

since this kind of computers are also affected I feel this should be corrected, so I reopen this ticket

#10 Updated by sajolida 2017-10-02 18:16:18

• QA Check set to Dev Needed

I didn’t know that, thanks!

#11 Updated by sajolida 2017-10-02 18:17:10

• blocked by deleted (Feature #13423: Core work 2017Q3: Technical writing)

#12 Updated by sajolida 2017-10-02 18:17:26

• blocks Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing added

#13 Updated by sajolida 2017-11-14 13:20:40

• Target version changed from Tails_3.3 to Tails_3.5

#14 Updated by anonym 2018-01-23 19:52:51

• Target version changed from Tails_3.5 to Tails_3.6

#15 Updated by sajolida 2018-02-23 17:04:18

• Status changed from Confirmed to Resolved
• Assignee deleted (sajolida)
• QA Check deleted (Dev Needed)

Fixed in a1db4b6487.