sailfish (Google Pixel): Mainlining
No idea where to start. Was suggested by pinoaffe to open an issue.
Using apq8096-db820c-* DTSes as a base.
Right now i've commented out regulators, and changed the compatible/model name. I don't know what else to do, and how to avoid the "purple smoke" (killing your phone).
Activity
msm8996-google-sailfish-pmic-pins.dtsi
msm8996-google-sailfish-pins.dtsi
By Ghost User on 2019-02-17T15:13:24
-
@steamport That's a good start! I'm guessing you've read the three mainlining pages on the Wiki: Mainlining Guide, Mainlining FAQ, and Qualcomm mainlining.
For the regulators, instead of commenting them out, the Wiki says to look at the downstream device tree and change the values in your dtsi to match. A lot of device drivers depend on the regulators, so it's easier to just get the regulators working.
You might also want to comment out nodes in the dtsi that enables hardware that don't exist on your phone (eg the second USB port, (most of?) the GPIOs in -pins.dtsi and -pmic-pins.dtsi, or the serial ports/SD card slot), in case they cause any issues.
You should also look at the reserved memory regions on the downstream device tree and copy them if needed. You can also setup a pstore-ramoops region to get kernel dmesg if your downstream kernel supports it. (I think the Pixel's kernel is new enough)
To boot the device, you need to copy the board and MSM ID from your device revision's dts file (the one I linked is for the -a revision) into your .dts. The bootloader checks this value to determine which device tree to use.
(The DragonBoard uses a tool called skales to automatically add that board ID node, but it's easier to hardcode the ID.)
For kernel config, start with the kernel's own defconfig (make defconfig), and enable some debugging features (eg CONFIG_DEBUG_DRIVER is very useful for finding out which drivers are being probed; CONFIG_PSTORE_RAM, CONFIG_PSTORE_CONSOLE might be useful if you can get pstore-ramoops working)
Honestly, I guess the best way to avoid breaking the phone is to be super careful. It's absolutely possible to fry a phone through a device tree (see Josh Thomas's article). Double check your voltages, GPIO/pinctrl, and anything else that may differ between the DragonBoard and your phone, and get a mentor to check your device tree.
Good luck, and looking forward to your progress.
By Zhuowei Zhang on 2019-02-19T02:45:47
mentioned in merge request !66 (closed)
By Zhuowei Zhang on 2019-03-18T23:10:47
-
Considering that the user who created this issue unfortunately has deleted their account, I'm closing this. If you're interested in porting this phone, come on over to the mainlining or porting channel on Matrix or IRC: https://wiki.postmarketos.org/wiki/Matrix_and_IRC
By Newbyte on 2021-09-24T19:29:47
Edited by Administrator