#linux-rockchip on 2020-12-02 — irc logs at freenode.irclog.whitequark.org

2017-05-08 04:47 ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip

00:15 kevery1 has joined #linux-rockchip

00:18 kevery has quit [Ping timeout: 246 seconds]

00:18 kevery1 is now known as kevery

00:34 archetech has joined #linux-rockchip

00:50 stikonas has quit [Remote host closed the connection]

00:51 stikonas has joined #linux-rockchip

01:03 stikonas has quit [Remote host closed the connection]

01:06 stikonas has joined #linux-rockchip

01:16 kevery1 has joined #linux-rockchip

01:18 kevery has quit [Ping timeout: 260 seconds]

01:18 kevery1 is now known as kevery

01:31 stikonas has quit [Remote host closed the connection]

01:36 stikonas has joined #linux-rockchip

01:38 stikonas has quit [Remote host closed the connection]

01:53 kaspter has joined #linux-rockchip

01:58 kevery1 has joined #linux-rockchip

02:01 kevery has quit [Ping timeout: 272 seconds]

02:01 kevery1 is now known as kevery

02:04 vstehle has quit [Ping timeout: 260 seconds]

02:21 urjaman has quit [Read error: Connection reset by peer]

02:22 urjaman has joined #linux-rockchip

03:17 chewitt has quit [Quit: Zzz..]

03:51 kevery has quit [Read error: Connection reset by peer]

03:55 field^Zzz4 has joined #linux-rockchip

03:56 kevery has joined #linux-rockchip

03:57 field^Zzz3 has quit [Ping timeout: 240 seconds]

04:28 kevery1 has joined #linux-rockchip

04:29 kevery has quit [Ping timeout: 240 seconds]

04:29 kevery1 is now known as kevery

04:53 camus has joined #linux-rockchip

04:54 kaspter has quit [Ping timeout: 246 seconds]

04:54 camus is now known as kaspter

04:57 kevery1 has joined #linux-rockchip

04:57 kevery has quit [Ping timeout: 246 seconds]

04:57 kevery1 is now known as kevery

05:08 archetech has quit [Quit: Konversation terminated!]

05:23 ldevulder_ has joined #linux-rockchip

05:26 ldevulder has quit [Ping timeout: 260 seconds]

05:50 kaspter has quit [Ping timeout: 256 seconds]

05:50 kaspter has joined #linux-rockchip

06:00 vstehle has joined #linux-rockchip

06:35 t3st3r has quit [Ping timeout: 240 seconds]

06:37 t3st3r has joined #linux-rockchip

07:02 tlwoerner has quit [Remote host closed the connection]

07:02 tlwoerner has joined #linux-rockchip

07:18 jelly-home is now known as jelly

07:31 camus has joined #linux-rockchip

07:32 kaspter has quit [Ping timeout: 260 seconds]

07:32 camus is now known as kaspter

07:44 kevery1 has joined #linux-rockchip

07:46 kevery has quit [Ping timeout: 256 seconds]

07:46 kevery1 is now known as kevery

07:53 matthias_bgg has joined #linux-rockchip

07:54 <wens> tuxd3v: not sure, but I think there needs to be a node level between the dwc3 node and the rtl8153 node to represent the hub?

07:55 <wens> ugh, nevermind

08:16 kaspter has quit [Ping timeout: 240 seconds]

08:16 kaspter has joined #linux-rockchip

08:17 ldevulder_ is now known as ldevulder

08:42 kevery has quit [Ping timeout: 240 seconds]

08:44 kevery has joined #linux-rockchip

09:28 kaspter has quit [Ping timeout: 240 seconds]

09:29 kaspter has joined #linux-rockchip

09:57 kevery has quit [Remote host closed the connection]

09:57 stikonas has joined #linux-rockchip

10:05 kevery has joined #linux-rockchip

10:10 matthias_bgg has quit [Ping timeout: 240 seconds]

10:15 kevery1 has joined #linux-rockchip

10:16 kevery has quit [Ping timeout: 240 seconds]

10:16 kevery1 is now known as kevery

10:24 matthias_bgg has joined #linux-rockchip

11:13 kaspter has quit [Ping timeout: 260 seconds]

11:13 kaspter has joined #linux-rockchip

11:25 vicencb has joined #linux-rockchip

11:43 kevery1 has joined #linux-rockchip

11:45 kevery has quit [Ping timeout: 256 seconds]

11:45 kevery1 is now known as kevery

12:22 samtux has joined #linux-rockchip

13:04 kevery1 has joined #linux-rockchip

13:06 kevery has quit [Ping timeout: 260 seconds]

13:06 kevery1 is now known as kevery

13:22 t3st3r has quit [Remote host closed the connection]

13:23 t3st3r has joined #linux-rockchip

13:43 kaspter has quit [Quit: kaspter]

13:57 alpernebbi has joined #linux-rockchip

14:22 chewitt has joined #linux-rockchip

14:44 kevery has quit [Ping timeout: 256 seconds]

14:50 kevery has joined #linux-rockchip

15:18 kaspter has joined #linux-rockchip

15:49 kaspter has quit [Quit: kaspter]

15:52 robmur01 has quit [Ping timeout: 260 seconds]

15:57 robmur01 has joined #linux-rockchip

16:18 vagrantc has joined #linux-rockchip

16:19 JohnDoe_71Rus has joined #linux-rockchip

16:41 kevery has quit [Remote host closed the connection]

16:41 kevery has joined #linux-rockchip

17:36 robmur01_ has joined #linux-rockchip

17:37 robmur01 has quit [Ping timeout: 260 seconds]

17:42 robmur01_ has quit [Ping timeout: 240 seconds]

17:49 niceplace has joined #linux-rockchip

18:03 <tuxd3v> wens the dts I an using is the mainline 'rk3328-nanopi-r2s.dts', there are there a 00 revision and also a 20 revision, but those I just ignore, I will delete them, in the future probably because I don't know about the hardware revisions..

18:03 <tuxd3v> I have hardware revision 1, its in the sbc board

18:03 <tuxd3v> I never saw shcematics for diferent revisions

18:04 <tuxd3v> Does you know what revision you have?its in the board writen..

18:04 <tuxd3v> but I doubt the existence of 3 hardware revisions

18:05 <tuxd3v> so the 00, and 20 revisions will probably go way in the future, currently I am not using them

18:06 <tuxd3v> I just updated the mainline 'rk3328-nanopi-r2s.dts', with some stuff :)

18:06 <tuxd3v> and it is working very nicely ;)

18:07 <tuxd3v> I also never expperience usb event problems with usb 2.0, maybe I need to test it some 20 times, plug and unplug..?!

18:08 <tuxd3v> for usb 3.0 we are sure that events will only happens at first when it detects the 8153b conected, then it will always be conected

18:10 <dvergatal> does anyone know what can cause that error: rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing

18:10 <dvergatal> on rk3399 ?

18:12 <tuxd3v> wens, I can sent you my dmesg:

18:14 <tuxd3v> https://paste.debian.net/1175302/

18:15 <tuxd3v> take atention to the renaming of the interfaces lan,wan :)

18:16 <tuxd3v> they are now renamed lan, wan ;)

18:16 <tuxd3v> the 8153b with fixed mac via DT as a nice udev rule, to rename it to 'lan'

18:17 <tuxd3v> SUBSYSTEM=="net", KERNEL=="eth*", ATTR{address}=="b2:54:c3:7b:35:a8", NAME="lan"

18:17 <tuxd3v> the other nic as always a ifindex of '3', so a new rule for it to rename to 'wan'

18:17 <tuxd3v> SUBSYSTEM=="net", KERNEL=="eth*", ATTR{ifindex}=="3", NAME="wan"

18:18 <tuxd3v> err, as always -> has always

18:19 <tuxd3v> currently my board is at 57C

18:19 <tuxd3v> its at full load for 4 consecutive days

18:20 <tuxd3v> at idlle it iddles at around 39-40C

18:20 <tuxd3v> with metal case :)

18:22 <tuxd3v> in the dts 'rk3328-nanopi-r2s.dts' for rk805 PMIC, I adjusted 'vdd_log' to correct levels supported by rk3328

18:22 <tuxd3v> I also adjusted 'vdd_arm' for lower values

18:23 <tuxd3v> the DVFS was also lowered in voltage

18:28 <tuxd3v> and also the DVFS for the Ram, but there we already saw that is fixed at 1.2 volts( vcc_ddr ) for ddr4, its in the schematics, it cannot be adjusted by i2c to the PMIC

18:29 <tuxd3v> I saw that with robmur01, some 1 week ago

18:32 <tuxd3v> overall is seems to be very nice :)

18:34 <tuxd3v> I will have yet to do some basic tests, on speed of interfaces, I will do them probably today :)

18:39 vicencb has quit [Quit: Leaving.]

19:21 stikonas has quit [Remote host closed the connection]

19:22 stikonas has joined #linux-rockchip

19:27 stikonas has quit [Remote host closed the connection]

19:28 stikonas has joined #linux-rockchip

19:34 JohnDoe_71Rus has quit [Quit: KVIrc 5.0.1 Aria http://www.kvirc.net/]

20:03 matthias_bgg has quit [Ping timeout: 256 seconds]

20:11 alpernebbi has quit [Quit: alpernebbi]

20:15 matthias_bgg has joined #linux-rockchip

21:22 matthias_bgg has quit [Ping timeout: 256 seconds]

21:33 Kwiboo has quit [Ping timeout: 256 seconds]

21:35 Kwiboo has joined #linux-rockchip

22:12 t3st3r has quit [Ping timeout: 240 seconds]

22:18 t3st3r has joined #linux-rockchip

22:29 indy has quit [Ping timeout: 264 seconds]

22:34 mrjay has joined #linux-rockchip

22:35 <mrjay> is there something special with current u-boot ? ... it doesn't boot

22:35 <mrjay> ... on pinebook pro

22:46 indy has joined #linux-rockchip

23:00 robmur01 has joined #linux-rockchip

23:04 <mrjay> ok ... spl boots but not u-boot proper ... something must be changed

23:05 robmur01 has quit [Remote host closed the connection]

23:05 <vagrantc> mrjay: current, as in git master? or the last release?

23:07 <mrjay> vagrantc: i'm using current ttps://gitlab.denx.de/u-boot/custodians/u-boot-rockchip.git

23:11 <vagrantc> haven't tested since u-boot 2020.10

23:12 <vagrantc> but at least that should narrow the bisecting needed

23:15 <mrjay> is optee needed by u-boot? or should i use arm trusted firmware

23:15 <mrjay> ?

23:23 <vagrantc> i've only ever used arm-trusted-firmware ... haven't tested 2.4 yet, only 2.3

23:28 ldevulder has quit [Read error: Connection reset by peer]

23:28 ldevulder has joined #linux-rockchip

23:29 <mrjay> ah ok