narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #linux-amlogic
<Danct12> steev, i did, it's just that it's over 150kb
GNUtoo has quit [Ping timeout: 258 seconds]
<steev> surprised debian doesn't like that
GNUtoo has joined #linux-amlogic
vagrantc has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #linux-amlogic
cphealy_ has quit [Quit: Leaving]
danct12_ has joined #linux-amlogic
<danct12_> steev, i got my kernel from manjaro, i could try to compile my own
<danct12_> is it possible that the sdio just doesnt work because wifi is enabled on android?
<steev> that is unlikely
<steev> a guess without looking at the config, or more importantly, the dts, is that it's not in the dts
<danct12_> it is actually in the dtsi
<danct12_> gtking.dts include w400.dtsi which has brcm wifi in it
<steev> would you mind piping the output of dtc -I fs -O dts /sys/firmware/devicetree/base to a pastebin? (or a file and then the pastebin)
<danct12_> i can do a termbin, i forgot which port was it
<steev> that will give us the dts of what you've got booted
<danct12_> https;//termbin.com/rcho
<danct12_> this is the boot dts
<danct12_> i think i've posted the config somewhere above
<steev> yeah, just wanted to make sure it's there
<danct12_> https://termbin.com/g174 for config.gz
<danct12_> (in a much more human readable language)
<steev> and you don't have anything in /sys/kernel/debug/devices_deferred ?
<danct12_> yep
<danct12_> nothing at all
<steev> huh
<steev> [ 4.385241] meson-gx-mmc ffe03000.sd: allocated mmc-pwrseq
<steev> that's the wifi card, but nothing further
<steev> (you can see it in the termbin for the dts if you search for wifi, it's sd@ffe03000
danct12__ has joined #linux-amlogic
<danct12__> yep, i noticed. the bluetooth driver does load so it does seem to work
<danct12__> it's just the wifi part doesn't want to initialize
danct12_ has quit [Ping timeout: 260 seconds]
<steev> stupid question, and typically it spits out that it's missing it, but do you have the firmware in place for it?
<danct12__> i believe i should
<danct12__> but i have seen this driver before, typically it would show an error if there's no firmware in place
<steev> yeah, that's why i said it normally spits out that it's missing
<danct12__> hmmmmmmmm
<danct12__> maybe we're missing a status = "okay"; somewhere
<steev> iirc, the dts we are booting wouldn't have it if status = disabled
<danct12__> there's actually status disabled in that dts
<steev> you said it's a gtking pro?
<danct12__> gtking, not a pro one
<danct12__> i'm going to try mess around with that, anyway to change the dtb on the fly?
<steev> yeah, you can, kinda
<danct12__> sure that would be enabled which explain our sdio message
<danct12__> alright, will do
<danct12__> i'll connect back to the internet later since now i'm powering the whole thing with a powerrbank
<danct12__> this is a very funny setup
<steev> yeah, these can be pretty neat like that
danct12__ has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
danct12_ has joined #linux-amlogic
<danct12_> wifi still doesnt work but this make me think
<danct12_> i wonder if it's a gpio pin that needs to be pull up or something
<danct12_> because i dont see linux saying anything about new sdio
<danct12_> steev, yup, and it's not at home anymore :P
<danct12_> i've been sitting here troubleshooting wifi for a few hours now
<danct12_> while people look at me with weird eyes
<danct12_> Client: HexChat 2.16.1 • OS: ArchLinux • Memory: Physical: 3.2 GiB Total (3.0 GiB Free) Swap: 4.8 GiB Total (4.8 GiB Free) • Storage: 3.3 GB / 30.7 GB (27.4 GB Free) • Uptime: 15m 56s
camus has quit [Ping timeout: 252 seconds]
danct12_ has quit [Remote host closed the connection]
camus has joined #linux-amlogic
danct12_ has joined #linux-amlogic
danct12_ has quit [Read error: Connection reset by peer]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
dnt12 has joined #linux-amlogic
dnt12 has left #linux-amlogic [#linux-amlogic]
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
jernej has joined #linux-amlogic
chewitt has joined #linux-amlogic
<chewitt> Danct12 the kernel config claims to have BRCMFMAC support
<chewitt> and the dts worked fine on GT-King (non-pro) when I created it and when I last tested it, which is maybe 5.17.y
<chewitt> rather odd to see no probing
<chewitt> one odd thing is CONFIG_CMA_SIZE_MBYTES=384
<chewitt> yet .. Reserved memory: created CMA memory pool at 0x00000000c8000000, size 256 MiB
<chewitt> and 8/10 kernels raid my patch-set which uses https://github.com/chewitt/linux/commit/b9268691e36639be97bd85ee4e0dd7c5ad378222
<chewitt> I was thinking along the lines of whether it was a genuine box (there are fake ones)
<chewitt> but BT probes correctly which implies there's a Broadcom chip .. so meh
<wens> maybe the device tree has a cma region?
<Danct12> chewitt, i'd be surprised if the box i had almost a year is a fake
elastic_dog has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-amlogic
elastic_dog has joined #linux-amlogic
mrec has joined #linux-amlogic
jernej has quit [Quit: Konversation terminated!]
jernej has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
jelly has quit [Ping timeout: 268 seconds]
buzzmarshall has joined #linux-amlogic
jelly has joined #linux-amlogic
jernej has quit [Ping timeout: 252 seconds]