stikonas has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
gavlee has quit [Read error: Connection reset by peer]
gavlee has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 272 seconds]
camus is now known as kaspter
<wens>
nanopi r4s launched, r2s with rk3399 and pcie ethernet instead
<wens>
worried about the lpddr4 though... I have a nanopi m4v2 which is useless :(
<tuxd3v>
wens, thanks for the info :)
<tuxd3v>
I have nanopi r2s
<tuxd3v>
why they choosed the rk3399? its a monster :)
<tuxd3v>
4 GB lpddr4
field^Zzz3 has joined #linux-rockchip
<tuxd3v>
on the other hand, they don't need a usb-to-ethernet controller
<tuxd3v>
maybe they wighted in the extra heat of the usb-to-ethernet port, and decided that to have same heat, better to go with a more powerfull SoC
<tuxd3v>
err, weighted
field^Zzz2 has quit [Ping timeout: 260 seconds]
<wens>
weighed :)
<tuxd3v>
thanks :)
<wens>
not sure if pcie-to-ethernet is cooler than usb-to-ethernet
<tuxd3v>
maybe because r2s still lacks a usb 3.0 driver in mainline
<tuxd3v>
there are some patchs from upstream, and recent Peter Geis from 2020-11-16
<tuxd3v>
have you tried the last usb 3.0 patch's from Peter Geis?
<tuxd3v>
I tried them, without success, but I already closed my metal case :( so no serial debug
tchebb has joined #linux-rockchip
<wens>
I have a somewhat working patch set from Cameron Nemo
<wens>
somewhat working in that disconnect doesn't work
<wens>
perfectly fine for something that is always attached
<tuxd3v>
does you have fixed macadress?
<tuxd3v>
I am using the upstream old version
<tuxd3v>
but in mainline 5.10.rc5
<tuxd3v>
I have fixed mac
<tuxd3v>
I tried several times to connect and disconnect a pendrive to usb2.0 just to see if it looses the state, and everything seems to continue to work
<tuxd3v>
ofcourse usb3.0 is always attached :)
<wens>
mac address is empty
<wens>
eeprom is missing
<tuxd3v>
so you have always a new macaddress when you reboot?
<tuxd3v>
I fixed it in the DT
<wens>
I have it in my network config
<wens>
hwaddress xx:xx:xx:xx:xx:xx in /etc/network/interfaces
kaspter has quit [Remote host closed the connection]
camus is now known as kaspter
<wens>
tuxd3v: thanks, so I got the function number wrong in my tree :p
<tuxd3v>
wens, you welcome :)
<tuxd3v>
that is what I have been using and it seems okish :)
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-rockchip
ldevulder_ is now known as ldevulder
matthias_bgg has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery has joined #linux-rockchip
stikonas has joined #linux-rockchip
mps has quit [Ping timeout: 264 seconds]
matthias_bgg has quit [Ping timeout: 272 seconds]
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
mps has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
<nomis>
tuxd3v: oh wow. Are you using that usb3 driver with a 3328 or a 3399?
<nomis>
(and did you change anything, or are these just straight the peter geis patches?
<nomis>
hm, seems a different patch than the peter geis stuff, different authors listed in the patch.
sphalerite is now known as L1nuxH4ckerm4n
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
L1nuxH4ckerm4n is now known as sphalerite
vicencb has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-rockchip
mps has quit [Ping timeout: 265 seconds]
kaspter has quit [Quit: kaspter]
mps has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
indy has quit [Ping timeout: 240 seconds]
kevery1 has joined #linux-rockchip
indy has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
JohnDoe_71Rus has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 264 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
matthias_bgg has joined #linux-rockchip
kaspter has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
jelly has quit [Read error: Connection reset by peer]
_whitelogger has joined #linux-rockchip
robmur01 has quit [Quit: Leaving]
robmur01 has joined #linux-rockchip
<tuxd3v>
nomis, the driver is being used with a rk3328( nanopi r2s )
<tuxd3v>
its not the same as Peter Geis, this is the upstream version
<tuxd3v>
I tried to test the Peter Geis driver from 2020-11-16, but my usb-to-ethernet doesn't come up, and I already had the metal case closed couldn't debug via uart
kevery1 has joined #linux-rockchip
<tuxd3v>
So I anded up with my previous patch for the DT with the upstream driver
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
matthias_bgg has quit [Quit: Leaving]
jelly-home has joined #linux-rockchip
kaspter has quit [Quit: kaspter]
<tuxd3v>
err, upstream-> downstream
<tuxd3v>
that driver is the rockchip one
<tuxd3v>
but Peter Geis seems to find out that that are some problems with the Innosilicon USB Phy, related with events, plug/unplug
<tuxd3v>
in the case of nanopi r2s I never found that problem, first because we pnly have 1 usb2 port availlable, second because usb3.0 is all the time connected to usb-to-ethernet controller, so there are no plug/unplug events
<nomis>
tuxd3v: so do you use the ancient rockchip kernel or did you forward-port the driver to somewhat recent?
<nomis>
or is there a version of the rockchip driver for a 5.x kernel?
<tuxd3v>
yes I am using the ancient rockchip driver :)
<tuxd3v>
on mainline 5.10.rc5
<tuxd3v>
with some changes in the DT, but that's it :)
<nomis>
ah, I did not dare to port that from the 4.x rockchip kernel. I feared that this would end up in a mess.
<tuxd3v>
maybe I will try again the Peter Geis driver, if I open my metal case
<tuxd3v>
I have then a chance to debug :)
<nomis>
I might want to try it. I have a tv box based on a 3328, serial console is not a problem there...
<tuxd3v>
my concern have only to do with the new twermal pad that comes with the metal case for rk3328
<tuxd3v>
twermal-> thermal
<tuxd3v>
its very tinny and I feared if I remove it will destroy it :/
<tuxd3v>
but If I gain some trust on open it again, surely I will test the Peter Geis Driver, with a serial debugger attached, lets see
<tuxd3v>
anyway the ancient driver is working very nice for me ;)
<tuxd3v>
but I still need yet, to do stress tests on the usb-to-ethernet nic port, to check speeds
<tuxd3v>
nomis, I am also using a small patch to activate the leds on nanopi r2s 8153b: