ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
russ has joined #armlinux
apritzel_ has quit [Ping timeout: 256 seconds]
Guest1610 has quit [Ping timeout: 260 seconds]
nsc has joined #armlinux
nsc is now known as Guest8881
XV8 has quit [Remote host closed the connection]
lag has quit [Ping timeout: 252 seconds]
lag has joined #armlinux
jclsn has quit [Ping timeout: 248 seconds]
jclsn has joined #armlinux
elastic_dog has quit [Read error: Connection reset by peer]
<bjdooks>
tagr: did you manage to get anything looked at for wiifi? I'm going to try and do a diff of gpios from 4.9-tegra to 5.x
headless has joined #armlinux
Guest8881 is now known as nsc
<geertu>
bjdooks: if there is no difference, it could be that the GPIO must be asserted after some specific moment.
<geertu>
I recently ran into that with a CAN-FD transceiver: using a gpio-hog for the enable pin didn't work, while it did work with gpioset from userspace
<bjdooks>
geertu: annoyinly I don't have gpioset on this system
<bjdooks>
I might just use devmem2 and prod registers
<geertu>
bjdooks: /sys/class/gpio?
<bjdooks>
doesn't seem to exist on newer kernels, or theyve hiddne it?
<bjdooks>
frieder: ok, thanks, forgot I could just go read the kcnfig
<bjdooks>
tagr: ok, so the working dtb seems to have H5 as reset and N0 as enable, but the /sys/kernel/debug/gpio is showing both are out-0, not out-1 as thought, it has two specific drivers that grab those as well as gpio hogs...
<geertu>
bjdooks: yummy
biju has joined #armlinux
prabhakarlad has joined #armlinux
guillaume_g has quit [Quit: Konversation terminated!]
headless_ has joined #armlinux
headless has quit [Ping timeout: 252 seconds]
headless_ is now known as headless
frieder has quit [Remote host closed the connection]
monstr has quit [Remote host closed the connection]