ChanServ changed the topic of #msm8937-mainline to: Boot Linux on your MSM8917/37/40 and QM215 mobile! | GitHub: https://github.com/msm89x7-mainline | Logs: https://oftc.irclog.whitequark.org/msm8937-mainline | Bridged to #msm8937-mainline:kde.org on Matrix
NekoCWD[m] has joined #msm8937-mainline
<x0-9-f[m]> Thanks folks! I've flashed 6.11. But usb doesn't work. I've installed the old 3.18 kernel to check hardware, there was power, messages in the dmesg, ttyACM was created. now I connected ZigBee CC2531 usb, there is no power, no messages in the dmesg... What can I check?
<barni2000[m]> usb should work
<barni2000[m]> but there is an issue in initramfs what can cause some issue sometimes
<x0-9-f[m]> <barni2000[m]> "but there is an issue in..." <- could you please show me where I can read about
<barni2000[m]> <x0-9-f[m]> "could you please show me where I..." <- You need to just reboot your device couple of time
<barni2000[m]> Maybe something missing from the kernel config let me check
<x0-9-f[m]> What do you think https://gitlab.com/postmarketOS/pmaports/-/issues/2762 i'm trying
<barni2000[m]> i will check the config
<x0-9-f[m]> I've changed dr_mode to host and it detects a usb keyboard but not my zigbee (
<barni2000[m]> otg is not working with mainline
<barni2000[m]> i am not investigated yet what is needed for it
<x0-9-f[m]> how can i check., is it charging?
<barni2000[m]> supply should be set for otg
<barni2000[m]> x0-9-f[m]: downstream or mainline?
<x0-9-f[m]> mainline
<barni2000[m]> there is no charging driver in the repo yet
<barni2000[m]> i have not cherry-picked it
<x0-9-f[m]> are you going ? )
<barni2000[m]> yes, but i have not reached that point yet i am working on msm8917 upstreaming and that caused a lot of change what should be changed in msm8937 and msm8940 also so i am going to clean up the repo first
<x0-9-f[m]> barni2000[m]: That's great! Thank you so much for your work. You are doing our world better
<barni2000[m]> some stuff reached from 6.13 previous versions
<barni2000[m]> i have prepared v7, but as far as i know i should not send it until 6.13-rc1
<Danct12[m]> <barni2000[m]> "i have prepared v7, but as far..." <- just develop on linux-next
<barni2000[m]> it is on top of linux-next
<Danct12[m]> doesn't stop you from submitting it
<Danct12[m]> 6.13-rc1 are just linux-next patches backported
<Danct12[m]> though it's best to double check everything (and testing) before submitting
<barni2000[m]> tbh i don't find any information about when i should not submit but people said some info about "merge window"
<barni2000[m]> i have 3 different information so idk
<barni2000[m]> so you said i can submit my pathces any time
<Danct12[m]> <barni2000[m]> "tbh i don't find any information..." <- > At the beginning of each development cycle, the “merge window” is said to be open. At that time, code which is deemed to be sufficiently stable (and which is accepted by the development community) is merged into the mainline kernel.
<barni2000[m]> ik subsystem maintainers have 2 weeks to send PRs
<Danct12[m]> merge window doesn't really matter if you're submitting your works
<barni2000[m]> merge window is for subsytem maintainers
<Danct12[m]> Danct12[m]: but what really matters is code compatibility, that's why linux-next is recommended when you do your development
<barni2000[m]> i am always using linux-next as a base
<Danct12[m]> s/code/api/
<Danct12[m]> so yeah, just go and submit your patches when you feel like it's good
<barni2000[m]> ok in this case i will send v7 because ig it will be the last or last before the last :D
<barni2000[m]> i need to check maybe something was applied just they forgot to send it
<barni2000[m]> i mean the applied message
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #msm8937-mainline
readerman[m] has joined #msm8937-mainline
<x0-9-f[m]> btw with dr_mode: "host" zigbee is detected and working
<barni2000[m]> mainline?
<x0-9-f[m]> <barni2000[m]> "mainline?" <- yep
<barni2000[m]> good to know
<barni2000[m]> you can try remove dr_mode or set to otg
<x0-9-f[m]> but usb networking seems doesn't work on "host"
<x0-9-f[m]> dr_mode otg checked, zigbee didn't work
<x0-9-f[m]> I'll check to remove dr_mode
<x0-9-f[m]> i think tomorrow