<xdarklight>
BlueMatt: on a Meson8m2 board without hub: USB devices are hot-pluggable, everything works fine
<xdarklight>
BlueMatt: on my Odroid-C1 (IIRC it has the same USB hub as the Odroid-C2): it's weird...
<xdarklight>
C1 without devices plugged during boot: hot-plugging is not working
<xdarklight>
C1 with USB thumb drive plugged during boot: thumb drive is not detect, hot-plugging is not working
<xdarklight>
C1 with USB thumb drive and USB serial adapter plugged in during boot: all devices are detected at boot, hot-plugging doesn't work either
<Xogium>
xdarklight: turns out upgrading from 4.19.3 to 4.19.56 fixed my strange issues with ethernet and giant ping rtt
<saintdev>
xdarklight: I can't find a good guide for an Arch cross env. The only docs they have are for a distcc setup....which won't really work without network...
<Xogium>
saintdev: what are you trying to do, traditional kernel compilation with a cross toolchain ?
<saintdev>
Xogium: trying to compile the arch kernel with an additional patch, to (maybe) "fix" detecting the network PHY
<Xogium>
with pkgbuild ?
<Xogium>
I'd recommand a traditional kernel compilation for that tbh
<Xogium>
that said
<Xogium>
I suppose you could toy with makepkg somewhat
<Xogium>
I think if you define the CROSS_COMPILE, CARCH and ARCH variables before your makepkg command on a x86 build machine, you can make it behave
<Xogium>
what arm architecture is this ?
<saintdev>
Xogium: i'm fine with the traditional compilation using the Arch config for testing, it would just make it far easier to be able to copy the package onto the sd card
<saintdev>
armv7 (odroid-c1)
<Xogium>
iirc, that's how I've done it, for testing packages
<Xogium>
let me see
<Xogium>
take the x-tools-armv7-bin package from aur
<Xogium>
its going to install a toolchain under /opt
<Xogium>
then when you want to compile the kernel you'll have to do like this
<Xogium>
I take my own toolchain as example you will need to adjust settings of course