stikonas has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 246 seconds]
kaspter has joined #linux-rockchip
azend has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
field^Mop has joined #linux-rockchip
field^Zzz4 has quit [Ping timeout: 260 seconds]
midnight has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 has joined #linux-rockchip
kevery1 is now known as kevery
vagrantc has quit [Quit: leaving]
kevery has quit [Ping timeout: 260 seconds]
kevery has joined #linux-rockchip
cp- has quit [Ping timeout: 260 seconds]
cp- has joined #linux-rockchip
cp- has quit [Ping timeout: 260 seconds]
cp- has joined #linux-rockchip
vstehle has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
JohnDoe_71Rus has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
ldevulder_ is now known as ldevulder
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-rockchip
indy has quit [Ping timeout: 246 seconds]
indy has joined #linux-rockchip
topi` has joined #linux-rockchip
maz has quit [Ping timeout: 264 seconds]
maz has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
vicencb has joined #linux-rockchip
jelly has quit [Remote host closed the connection]
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
jelly-home has joined #linux-rockchip
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
DuClare has quit [Ping timeout: 240 seconds]
DuClare has joined #linux-rockchip
kevery1 has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
matthias_bgg has quit [Ping timeout: 240 seconds]
matthias_bgg has joined #linux-rockchip
jelly-home is now known as jelly
<tuxd3v>
hello guys anybody can help me to fix uboot maccaddress of second ethernet usb card?
<tuxd3v>
setenv eth1addr
<tuxd3v>
in uboot script doesn't work :(
<wens>
tuxd3v: first of all you would need a DT node for that USB card, then an ethernet alias in the DT, so that U-boot knows where to set the MAC address
<ukleinek>
tuxd3v: the alternative is to explicitly configure the mac address in Linux only
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 256 seconds]
mrueg has joined #linux-rockchip
matthias_bgg has quit [Remote host closed the connection]
ldevulder_ is now known as ldevulder
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
kaspter has quit [Ping timeout: 260 seconds]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 272 seconds]
kaspter has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery1 is now known as kevery
<mps>
how to find from dmesg output which source driver in kernel tree drivers/mmc/host/ is used for emmc on rk3399 (gru-kevin chromebook in my case)
<mps>
looks like it is sdhci-of-arasan.c but don't see it in dmesg output
<robmur01>
yes, the eMMC interface is an Arasan SDHCI
<mps>
robmur01: thanks, now comes complicated part to try to hack it to disable ADMA (says someone who have no any idea how e/mmc works0
<robmur01>
that driver isn't obnoxiosly spammy like dwmmc - on mine I just see messages from the MMC core about the controller being registered and the card being detected
<robmur01>
is that not something you can do with the "sdhci.debug_quirks" parameter?
<mps>
I have this on boot 'mmc0: mmc_select_hs400es failed, error -110'
<mps>
emmc works fine if I do not suspend/resume
<mps>
after resume and some undefined time it 'crash'
<mps>
' Got data interrupt 0x00000002 even though no data operation was in progress.'
<mps>
I posted bug report to kernel maintainers few months ago but it is not yet fixed
<mps>
robmur01: debugging this problem is hard because after driver 'crash' running any cmd ends with 'segmentation fault'
vagrantc has joined #linux-rockchip
<robmur01>
put your root filesystem on SD/USB/NFS/etc. - if it's on the device you're trying to debug you're going to have a bad time
<robmur01>
but with something like system suspend involved, beware that you're quite likely to be debugging a symptom of some distant clock/power domain/other bit of SoC glue not being restored/reset properly, so it may not make sense on its own anyway
<mps>
hmm, I thought about that and as I mostly use it with root FS from ssd disk over usb and sometimes from mmc card
<robmur01>
I mean, if it works *before* suspend, it's clearly not fundamentally broken