ChanServ changed the topic of #linux-msm to:
hipboi has joined #linux-msm
niej_ has joined #linux-msm
niej_ has quit []
hipboi has quit [Quit: hipboi]
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
marc|gonzalez has joined #linux-msm
hipboi has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
hipboi has quit [Quit: hipboi]
hipboi has joined #linux-msm
hipboi has quit [Quit: hipboi]
hipboi has joined #linux-msm
jhovold has joined #linux-msm
hipboi has quit [Quit: hipboi]
hipboi has joined #linux-msm
xelageo_ has joined #linux-msm
xelageo has quit [Ping timeout: 480 seconds]
xelageo_ is now known as xelageo
pevik has joined #linux-msm
srinik has joined #linux-msm
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
hipboi has quit [Quit: hipboi]
gnuiyl has quit []
gnuiyl has joined #linux-msm
hipboi has joined #linux-msm
srinik has quit [Remote host closed the connection]
srinik has joined #linux-msm
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #linux-msm
minecrell has quit [Read error: Connection reset by peer]
minecrell has joined #linux-msm
pespin has joined #linux-msm
hipboi has quit [Quit: hipboi]
<HappY05[m]> Now I don't have usb .. so I unable to take log.. but my kernel got hanged.. is it for "gpi dma controller" ?
<phh> synchronous external abort usually mean someone other than the CPU is doing nasty thing to the memory bus, which would be coherent with a dma controller yes
svarbanov_ has joined #linux-msm
svarbanov has quit [Read error: No route to host]
svarbanov__ has joined #linux-msm
<HappY05[m]> Anyone can please explain it ? What is mean actually?
<HappY05[m]> And 0-0055 is it mean i2c0 & reg address 55 ?
svarbanov_ has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
<phh> HappY05[m]: I'm not sure there is a guarantee that the 0 means i2c0? it does mean first i2c bus, and usually aliases do work. anyway i doubt this is relevant, i2c won't do memory access
<HappY05[m]> So if i2c won't do memory access then fuel gauge will work or won't work?
<HappY05[m]> Because in my device battery status always reporting it to 100%
<HappY05[m]> And I have issues with charging
<phh> I thought you were still working on your issue that you can't boot..
<chalkin[m]> HappY05: You can check this. https://gitlab.com/sdm845-mainline/linux/-/issues/36
<HappY05[m]> <phh> "I thought you were still working..." <- Yes still working on it..
<HappY05[m]> chalkin[m]: Yes exactly was same issue but I am already useing bq27541
<phh> gotta admit i don't understand how you can see 100% charge without booting but ok
<HappY05[m]> phh: I was already booted long time ago with 6.5.0 kernel.. now I just upstream my kernel..
<HappY05[m]> And now I am facing booting issue
<chalkin[m]> <HappY05[m]> "Yes exactly was same issue but I..." <- > <@happy05:matrix.org> Yes exactly was same issue but I am already useing bq27541... (full message at <https://matrix.org/oftc/media/v1/media/download/AfAIdtaue4iCxwWMwPF8x9VQEwHuntpBP_zTbx3jWHb6lHswhnXuTRtGXB-jyM49kbOFg0bB5tVye21jIGfPMJ9CeSflQ7RQAG1hdHJpeC5vcmcveU12UGNETVprT0dEZ0FLQXZaVVBXZGp0>)
jhovold has quit [Ping timeout: 480 seconds]
pespin has quit []
deathmist1 has joined #linux-msm
deathmist has quit [Ping timeout: 480 seconds]
deathmist1 is now known as deathmist
svarbanov__ has quit [Quit: Leaving]
svarbanov__ has joined #linux-msm
<HappY05[m]> <chalkin[m]> "> <@happy05:matrix.org> Yes..." <- > <@chalkin:matrix.org> There may be a mismatch between the driver and the chip. Try to execute the following command to obtain the chip type... (full message at <https://matrix.org/oftc/media/v1/media/download/AWO-gGmOLwGnjsEou-LR9bmP-cg-Kn9z5AWL22zOaC-TezMczAadSjT-JLY7uTKVNq1OmvXP91mLnL9P7_aytD5CeSf4pcHQAG1hdHJpeC5vcmcvdGJhZ1B1U3FRRnd1QW5JQURMbmpFWWtj>)
<HappY05[m]> Now my device booted successfully.. but most probably some kernel configuration is missing.. anyone can help?
<HappY05[m]> dmesg