htc-evita: New device
Merge request reports
Activity
- Resolved by Administrator
mentioned in issue #174 (closed)
By mirh on 2019-01-25T12:59:50
Hi.
I try to port to htc-ville. Kernel is compiled correctly and also starting but always rebooting with
RAMDISK: Couldn't find valid RAM disk image starting at 0.
The same ramdisk is booting with twrp/cm/los kernel without problems.Did you experience similar problems and have maybe the solution?
By escoand on 2019-01-25T13:26:11
Hi @escoand I had no issues what so ever building and compiling the kernel, then booting it.
I got the offsets from the newest TWRP image when I kicked of pmbootstrap init the first time. I just followed the kernel configuration page in the wiki and also disabled CONFIG_MSM_KGSL, and added the device package mdss-fb-init-hack to the APKBUILD file.
Never had an issue with ramdisk errors, sorry.
By Simon Utter on 2019-01-26T00:09:02
Edited by AdministratorYes man, now booting without problems. Don't know what the problem was with the ramdisk. Anyway, CONFIG_MSM_KGSL seems to be needed, but not mdss-fb-init-hack. Thanks...
By escoand on 2019-01-26T13:46:35
Edited by AdministratorI'm not sure if I got you right. Is !177 (merged) what you want from me?
By escoand on 2019-01-27T07:19:27
@PureTryOut Just giving this a bump up, think it's ready to be merged :) CI finishes successful and wiki has been updated!
By Simon Utter on 2019-01-28T06:33:13
Beyond that htc-evita uses 3.4.72 and htc-ville uses 3.4.110 a diff of the kernel configs shows over 150 differences. Is this in your eyes the same kernel?
By escoand on 2019-01-28T12:22:13
Edited by Administrator@escoand The above comments made me a bit unsure, so had to check and I haven't used the same commit number as you (mistake from my side). I'll try building your linux-htc-ville package and check if it boots on my device. If all well we can give it a common name and package as other have suggested?
By Simon Utter on 2019-01-28T12:33:09
LineageOS and Cyanogen used HTC S4 as common repo for HTC One S/One XL/EVO 4G LTE/DROID Incredible 4G LTE.
- https://github.com/LineageOS/android_device_htc_s4-common
- https://github.com/CyanogenMod/android_device_htc_s4-common
By escoand on 2019-01-28T13:31:54
In the associated kernel repo I can only find the config file for ville: https://github.com/LineageOS/android_kernel_htc_msm8960/tree/cm-12.1/arch/arm/configs
I used the cm-12.1 branch as this was the last official release for htc-ville.
By escoand on 2019-01-28T13:37:53
Ok, I've found the used defconfig files in BoardConfig.mk:
htc-evita elite_defconfig htc-jewel jet_defconfig htc-fireball fighter_defconfig htc-ville ville_defconfig
So at the end they use the same source code but a different defconfig. And they are actually also slightly different.
By escoand on 2019-01-28T13:51:16
added 12 commits
-
c3667ebf...f0f50479 - 11 commits from branch
postmarketOS:master
- c6e5ec1d - htc-evita: new device (HTC One XL) (!175 (merged))
By Oliver Smith on 2019-01-28T20:10:23
-
c3667ebf...f0f50479 - 11 commits from branch
So at the end they use the same source code but a different defconfig. And they are actually also slightly different.
I'd go with a different kernel package then. If you want to optimize it a bit, you could base it off the same source tarball, so people building both kernels (i.e. binary package repository) may only need to download it once.
Real unifying can be done with kernels based on mainline.
By Oliver Smith on 2019-01-28T20:12:32
mentioned in commit wiki@893ee463
By postmarketOS Wiki bot on 2019-01-28T20:42:44
mentioned in commit c6e5ec1d
By Simon Utter on 2019-02-11T21:36:40
mentioned in commit 5765ace2
By Simon Utter on 2019-02-14T19:42:54
mentioned in issue #340 (closed)
By Ghost User on 2019-12-08T20:17:04