ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log | Community GH | Rockchip GH | ML
vicencb has quit [Quit: Leaving.]
asciilifeform has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-rockchip
vstehle has quit [Ping timeout: 272 seconds]
afaerber has quit [Quit: Leaving]
asciilifeform has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
akaizen has quit [Quit: Textual IRC Client:]
akaizen has joined #linux-rockchip
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 -]
MoeIcenowy has joined #linux-rockchip
vstehle has joined #linux-rockchip
hipboi has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
tlwoerner has quit [Ping timeout: 252 seconds]
vicencb has joined #linux-rockchip
vagrantc has quit [Ping timeout: 260 seconds]
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
fischerm has joined #linux-rockchip
s_frit has quit [Ping timeout: 240 seconds]
chewitt has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
JohnDoe_71Rus has joined #linux-rockchip
vicencb has joined #linux-rockchip
<nashpa> hello, does anyone have a recipe for fixing firefly-rk3399 PCIe link training timeout (-110) error?
<nashpa> does this point to my hardware being broken?
<nashpa> (I'm using mainline U-Boot and linux-next)
<mmind00> nashpa: good question ... I think there was a problem with pcie gen2 link training having issues in some cases, but I thought there was already a patch limiting that ... let me check
<mmind00> nashpa: ... and just verified that I did apply it
<mmind00> nashpa: basic problem was that the pcie can have link-training issues in gen2 with some devices, while other people reported that it works actually nicely ... so we defaulted to gen1 ... so I guess link-training should actually work nicely
<mmind00> nashpa: can you try some older kernel versions to check if the problem is present on them as well?
<mmind00> just to check if that is a newly introduced regression
<nashpa> mmind00: I have that change
<nashpa> mmind00: let me try a different question then: should the PCIe training work without any device being plugged in?
<nashpa> mmind00: and if not, does the number of lines in the DTS have to match what the connected device has?
<nashpa> mmind00: I don't know which older kernel version I should try, the one that Firefly provides in their image doesn't work either (times out as well)
<mmind00> nashpa: I'm really not that versed in pcie stuff ... I do have one of the m.2 -> sata adapters in my firefly-rk3399 board and it is working
<mmind00> nashpa: is something actually in your pcie port
<mmind00> ?
<nashpa> mmind00: hmm, I wonder if there is any magic in that adapter.
<nashpa> mmind00: I've put a Toshiba RC100 NVME SSD
<mmind00> i.e. I'd think link training should fail if nothing is in the slot
<nashpa> which I think it is an x2 PCIe 3.1 device (hopefully compatible with the PCIe from RK3399 as well)
<mmind00> nashpa: I'm really not sure, but if the vendor kernel is also not working, and also something like 4.12 or so ... I'd guess there may be some sort of issue with the ssd itself, but as I said, I'm really not sure
<mmind00> nashpa: I only have the sata adapter in my firefly and a full pcie-usb3 card in my rk3399-puma
<nashpa> mmind00: OK, thanks for your time, I'll try to see if I can get some alternative to that SSD that matches closer to what Firefly-RK3399 expects
<nashpa> mmind00: I'm waiting on the Renegade board to show up to have another RK3399, wanted to use the Firefly to prepare for that
<mmind00> nashpa: glad to help or at least try to :-)
<nashpa> I've managed to get a fully open-source stack after a lot of pain trying to recover a bad emmc bootloader
<nashpa> but now I have a method of recovering
<mmind00> :-)
<nashpa> unfortunately you still need to use the rk3399_loader_v1.08.106.bin to flash the SPL, U-Boot doesn't seem to be capable of writing to the eMMC
<nashpa> it can erase it just fine, but nothing else, env in eMMC is a no-go :-(
<Esmil> Did anyone look at the mwifiex scheduling while atomic bug in 4.19 on kevin? It seems I can avoid them by reverting 5188d5453bc9380ccd4ae1086138dd485d13aef2 and 5631909364e1e74b6188ec860d2a4cf216150a26
scelestic has quit [Remote host closed the connection]
scelestic has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
anarsoul|2 has joined #linux-rockchip
chewitt has quit [Ping timeout: 246 seconds]
tlwoerner has joined #linux-rockchip
phh has quit [*.net *.split]
PoueT has quit [*.net *.split]
phh has joined #linux-rockchip
PoueT has joined #linux-rockchip
vagrantc has joined #linux-rockchip
Kelsar has quit [Quit: - Chat comfortably. Anywhere.]
Kelsar has joined #linux-rockchip
tlwoerner has quit [Remote host closed the connection]
tlwoerner has joined #linux-rockchip
jwerner_ has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria]
lkcl has joined #linux-rockchip
<beeble> nashpa: link training will fail if nothing is attached
tlwoerner has quit [Remote host closed the connection]
<beeble> devices with a bridge inside will fail often
<beeble> or mostly
<beeble> but that would end with a kernel crash in most cases
<beeble> so at least link training should work if everything in your pcie setup is correct
tlwoerner has joined #linux-rockchip
<nashpa> beeble: yeah, I'm not sure if the SSD I have (PCIe 3.0) is capable of downgrading to RK3399 PCIe 2.1
<nashpa> beeble: I've ordered from Aliexpress the PCIe M.2 to SATA adapter from firefly, when it arrives I should be able to validate my HW
s_frit has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
tlwoerner has quit [Remote host closed the connection]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-rockchip
tlwoerner has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]