Skip to content
Snippets Groups Projects

device-xiaomi-tissot: Initial device support

Merged Imported Administrator requested to merge device/xiaomi-tissot into master
All threads resolved!

Initial support for Xiaomi A1 aka xiaomi-tissot using LineageOS 15.1 kernel, has similar board to Xiaomi Redmi 4 aka xiaomi-mido with some differences that had to be patched such as reversing skip_initramfs and ignoring dm param. 16.0 kernel boots but display fb init doesn't work.

Works:

  • USB RNDIS with SSH (applied a patch to only WARN_ON once instead of dmesg spam which is only triggered when USB network is active)
  • Display with Wayland: Weston and Plasma (software rendering)
  • Touchscreen with several fingers
  • reboot/poweroff

Kinda works:

  • Display with Xorg after issuing the command cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode, for some reason none of hacks related to mdss/msm fb works because the command has to be issued after some time and then Xorg must be started. Xorg without this trick reports "FBIOPUT_VSCREENINFO: Invalid argument"... Any idea?
  • Already plugged USB devices via OTG/Host when kernel is booting

Requires firmware:

  • WiFi
  • Baseband (probably)

Not working:

  • Bluetooth (kernel doesn't report any error and shows device but rfkill is empty)
  • WiFi
  • Audio
  • New USB devices via OTG/Host after boot
  • Baseband
Edited by Administrator

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Administrator changed title from device-xiaomi: Initial device support to device-xiaomi-tissot: Initial device support · Imported

    changed title from device-xiaomi: Initial device support to device-xiaomi-tissot: Initial device support

    By Bart Ribbers on 2019-01-21T21:29:57

  • Administrator changed the description · Imported

    changed the description

    By Bart Ribbers on 2019-01-21T21:29:57

  • Administrator added 1 commit · Imported

    added 1 commit

    Compare with previous version

    By Ion A on 2019-01-21T21:40:56

  • Administrator added 12 commits · Imported

    added 12 commits

    Compare with previous version

    By Oliver Smith on 2019-01-22T06:20:00

  • Author Owner

    Not looked at the patch yet, but I have rebased it on master, so the continuous integration (CI) scripts will run properly. (In the future, it will be more obvious when that is necessary, created !167 (merged) for that.)

    Thank you very much for the device port and merge request @IonAgorria!

    By Oliver Smith on 2019-01-22T06:22:21

  • Author Owner

    CI is failing, because the checksums of the device package need to be updated. Please fix it, and (if there should be any) all following errors until CI passes.

    By Oliver Smith on 2019-01-22T06:54:48

  • Administrator added 1 commit · Imported

    added 1 commit

    • 4437a53d - Fix device-xiaomi-tissot checksum

    Compare with previous version

    By Ion A on 2019-01-22T07:03:49

  • Administrator added 5 commits · Imported

    added 5 commits

    Compare with previous version

    By Oliver Smith on 2019-01-23T08:19:39

  • Administrator approved this merge request · Imported

    approved this merge request

    By Oliver Smith on 2019-01-23T08:19:49

  • Author Owner

    Aport and patches look good, thanks for the port @IonAgorria!

    I know this is based off xiaomi-mido, therefore using an older kernel aport template. Consider modernizing it in a new MR: https://wiki.postmarketos.org/wiki/Vendor_kernel_specific_package#Modernize_your_aport

    • Display with Xorg after issuing the command cat /sys/class/graphics/fb0/modes > /sys/class/graphics/fb0/mode, for some reason none of hacks related to mdss/msm fb works because the command has to be issued after some time and then Xorg must be started. Xorg without this trick reports "FBIOPUT_VSCREENINFO: Invalid argument"... Any idea?

    Consider making a new issue for this (if there isn't any). Some spontaneous ideas without looking into it too much:

    • Does the mido device have a fix for that?
    • Try to search for that message in the kernel source and read the surrounding code
    • Add debug prints there etc., until you figure out how to configure it properly without starting xorg.

    By Oliver Smith on 2019-01-23T08:24:20

  • Administrator added 1 commit · Imported

    added 1 commit

    Compare with previous version

    By Oliver Smith on 2019-01-23T08:42:16

  • Administrator approved this merge request · Imported

    approved this merge request

    By Oliver Smith on 2019-01-23T08:42:29

  • Administrator resolved all discussions · Imported

    resolved all discussions

    By Oliver Smith on 2019-01-23T08:42:34

  • Administrator merged · Imported

    merged

    By Oliver Smith on 2019-01-23T08:43:04

  • Administrator mentioned in issue #177 (closed) · Imported

    mentioned in issue #177 (closed)

    By Ion A on 2019-01-23T18:12:50

  • Administrator mentioned in merge request !173 (merged) · Imported

    mentioned in merge request !173 (merged)

    By Ion A on 2019-01-24T19:05:55

  • Administrator mentioned in commit f0f50479 · Imported

    mentioned in commit f0f50479

    By Bart Ribbers on 2019-02-11T21:36:41

  • Administrator mentioned in commit 26592daa · Imported

    mentioned in commit 26592daa

    By Bart Ribbers on 2019-02-13T14:19:48

  • Administrator mentioned in commit 5e92794d · Imported

    mentioned in commit 5e92794d

    By Bart Ribbers on 2019-02-14T19:42:54

  • Administrator mentioned in commit e594d236 · Imported

    mentioned in commit e594d236

    By Bart Ribbers on 2019-02-14T19:42:55

  • Administrator mentioned in merge request !1485 (merged) · Imported

    mentioned in merge request !1485 (merged)

    By Rian McGuire on 2020-08-17T21:41:31

  • Please register or sign in to reply
    Loading