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
ARMed has quit [Ping timeout: 268 seconds]
ARMed has joined #armlinux
ARMed has quit [Read error: No route to host]
ARMed has joined #armlinux
ARMed has quit [Quit: Leaving.]
ARMed has joined #armlinux
ARMed has quit [Ping timeout: 252 seconds]
rvalue has joined #armlinux
Misotauros has quit [Ping timeout: 268 seconds]
Misotauros has joined #armlinux
cbeznea has joined #armlinux
amitk has joined #armlinux
NikhilAmd has joined #armlinux
iivanov has joined #armlinux
Pali has joined #armlinux
viorel1 has joined #armlinux
Pali has quit [Ping timeout: 244 seconds]
nipung has joined #armlinux
nipung has quit [Client Quit]
tre has joined #armlinux
frieder has joined #armlinux
prabhakarlad has joined #armlinux
matthias_bgg has joined #armlinux
krzk has quit [Read error: Connection reset by peer]
headless has joined #armlinux
monstr has joined #armlinux
Norkle has quit [Killed (NickServ (GHOST command used by norkle_))]
Norkle has joined #armlinux
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
apritzel has joined #armlinux
headless has quit [Quit: Konversation terminated!]
NikhilAmd has quit [Quit: Client closed]
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
bochenchen has quit [Remote host closed the connection]
bochenchen has joined #armlinux
apritzel has quit [Ping timeout: 240 seconds]
nsaenz has joined #armlinux
Lucanis has quit [Ping timeout: 255 seconds]
nsaenz has quit [Client Quit]
apritzel has joined #armlinux
bochenchen has quit [Remote host closed the connection]
bochenchen has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
krzk has joined #armlinux
headless has joined #armlinux
frieder has quit [Ping timeout: 260 seconds]
frieder has joined #armlinux
headless has quit [Quit: Konversation terminated!]
<robher>
mwalle: No, #address-cells only matters if there is a 'reg' property.
<robher>
mwalle: Though mixing child nodes with and without addresses is not a great design (though the root node does that).
cambrian_invader has joined #armlinux
<Xogium>
hiya :) I think, I am not 100000% sure of what I claim... That whatever this console over usb gadget issue is, is a hardware problem from the v3s SoC. Things have gotten even more nut since I asked about this the other day, mainly that 3 things can happen with this board
headless has quit [Quit: Konversation terminated!]
nsaenz has joined #armlinux
<Xogium>
1. If powering via the vin pin of the v3s using a cp2110 rather than over micro usb with OTG support, uart0 console freezes (ttyS0), right after systemd prints, 'detected architecture arm'.
<Xogium>
2. If powering through micro usb with OTG support instead, the system will boot further along, up to systemd printing 'reached target path units'. Then the board is immediately flung back all the way to u-boot.
<Xogium>
It is not a panic, not a lockup, not a triggered reboot. It is a violent reset, pure and simple.
<Xogium>
3. If powering via usb once again but connecting something to listen on the gadget that appears on host (e.g: screen) before it disappears due to the reset, the whole system boots normally.
<Xogium>
I thought of driver issue at some point, but checking with an orange pi zero which uses a h3 SoC instead of v3s, I notice they use the exact same usb driver. The orange pi does not behave this way with the same kernel version, same systemd version, generally same buildroot release actually
<Xogium>
so why I think this is a real hardware issue
nsaenz has quit [Client Quit]
<mwalle>
robher: ah ok thanks!
<Xogium>
I tried with 3 different boards in total, they all go insane as soon as I enable usb serial gadget
cbeznea has quit [Ping timeout: 260 seconds]
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
<Xogium>
I suppose it could be the lichee zero that's buggy but, how you manage to cause that sort of problem while you just expose the usb headers of the SoC in a micro usb plug would be beyond me. I think the SoC itself has a problem
cambrian_invader has quit [Ping timeout: 252 seconds]