stikonas has quit [Remote host closed the connection]
<tuxd3v>
stikonas, thanks
<tuxd3v>
your idbloader.img is ~473kB in Size, wereas mine is 147KB
<tuxd3v>
don't know what can produce so diferent binaries..
<tuxd3v>
yeah I am compiling bl31.elf with correct compiler for cortex m0
<tuxd3v>
I will try your idbloader.img, with mine u-boot.itb, well several combinations
<tuxd3v>
thanks again
vstehle has quit [Ping timeout: 265 seconds]
cristian__c has quit [Read error: Connection reset by peer]
cristian_c has joined #linux-rockchip
field^Zzz3 has joined #linux-rockchip
chewitt has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
tuxd3v has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-rockchip
vstehle has joined #linux-rockchip
kaspter has joined #linux-rockchip
hessophanes has quit [Ping timeout: 265 seconds]
hessophanes has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
camus1 is now known as kaspter
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
kaspter has quit [Ping timeout: 244 seconds]
kaspter has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 246 seconds]
kevery1 is now known as kevery
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
sb35 has joined #linux-rockchip
jaganteki has joined #linux-rockchip
camus1 has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 260 seconds]
camus1 is now known as kaspter
adjtm has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
stikonas has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
lerc has quit [Quit: No Ping reply in 180 seconds.]
lerc has joined #linux-rockchip
<robmur01>
sphalerite: rebooting - sounds like you're probably using an old Trusted Firmware that doesn't reset the power domains (thus the second boot hangs trying to access something it assumes is powered but isn't)
<robmur01>
that's been fixed upstream since the end of last year
<nomis>
robmur01: ok, slow progress today. I have the usb2 ports, but usb3 port and otg port are not yet funktional.
<robmur01>
nomis: I wouldn't sweat too much over usb3 just yet - it's not (yet) supported upstream, you can make it sort-of-work with hacks, but it's super-dodgy without a phy driver; somebody's tried to work on that, but not managed to get it working well yet
<nomis>
this regulator stuff is dense. The rk3328-evb apparently uses a "rk805" power management IC which doesn't seem to be used on the tv box.
<robmur01>
yeah, the cheapo boxes just use 3(?) adjustable regulators controlled by PWMs for the main voltages
<nomis>
robmur01: I've tried to reverse engineer from the binary dtb-blob from the original filesystem but it stoped working unfortunately.
<robmur01>
if you can find a firmware upgrade image for flashing over USB cable (i.e. not one for Android self-updating via SD card or USB stick), you can unpack those with resource_tool from rkbin
<nomis>
robmur01: the trouble is, that these binary blobs have lost information compared to the dts sources. phandles get introduced and references get translatet into opaque integers.
<robmur01>
indeed - for known bindings like GPIOs and PWMs it's not too bad, since it's clear which part of the specifier is the phandle value, and that can be matched to the relevant bank/channel by the address of the node owning that phandle
<robmur01>
and luckily, there's usually little need to decipher the weird downstream properties that end up as just massive arrays of hex nonsense
<nomis>
robmur01: the remotectl-driver doesn't seem to be upstream yet, right?
<robmur01>
as I said the other day, that's where it comes in handy to start building generic DTBs from the appropriate BSP, then for the bits where the DTBs end up matching you know you have source ;)
<robmur01>
IIRC the remotectl driver doesn't actually do much - just uses the PWM capture to offload some of the pulse-width measurement
<nomis>
robmur01: can you point me to a matching BSP? The chinese manufacturer wasn't that helpful in that regard.
<robmur01>
just use gpio-ir-recv like everything else upstream, works fine
<robmur01>
yeah, I typically start with RK's own BSP mirror - https://github.com/rockchip-linux/kernel/ - but either way that DTS(i) looks like the right basic "box" design (discrete regulators rather than rk805 as in "box plus")
<nomis>
duh, me not noticing that the rockchip kernel also contains tv-box dts's annoys me.
<robmur01>
FWIW I think at least Firefly and Friendlyelec have public copies of the whole actual Android BSPs too
jelly has joined #linux-rockchip
sb35 has quit [*.net *.split]
hessophanes has quit [*.net *.split]
JohnDoe_71Rus has quit [*.net *.split]
jelly-home has quit [*.net *.split]
return0e_ has quit [*.net *.split]
circuit has quit [*.net *.split]
lkcl_ has quit [*.net *.split]
indy has quit [*.net *.split]
jlanda has quit [*.net *.split]
cyrozap has quit [*.net *.split]
<robmur01>
(those can be good for digging out firmwares for dodgy wifi modules, for instance)
JohnDoe_71Rus has joined #linux-rockchip
circuit has joined #linux-rockchip
hessophanes has joined #linux-rockchip
jelly is now known as jelly-home
lkcl_ has joined #linux-rockchip
cyrozap has joined #linux-rockchip
ChanServ has quit [*.net *.split]
ChanServ has joined #linux-rockchip
chiastre has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
chiastre_ has joined #linux-rockchip
chiastre has quit [Remote host closed the connection]
field^Zzz3 has quit [Ping timeout: 244 seconds]
vicencb has joined #linux-rockchip
opennandra has joined #linux-rockchip
<opennandra>
hello, I'm using Neo4 mainline 5.4 kernel. O would like to use USB ethernet + PoE to be conencted to USB-C. Power works fine but OTG doesn't work (OTG seems not to work). Do I need to setup something in order to have this setup working? Thanks.
adjtm_ has joined #linux-rockchip
chiastre_ has quit [Ping timeout: 240 seconds]
adjtm has quit [*.net *.split]
lkcl_ has quit [*.net *.split]
cyrozap has quit [*.net *.split]
hessophanes has quit [*.net *.split]
JohnDoe_71Rus has quit [*.net *.split]
circuit has quit [*.net *.split]
<robmur01>
as in NanoPi NEO4? Unfortunately all of the upstream RK3399 USB-C support only works on Chromebooks via the cros-ec extcon stuff - boards with other Type-C controller chips like the FUSB302 on the nanopi4 series apparently don't have any hope of support without a bunch of work in the Rockchip Type-C phy driver
chiastre_ has joined #linux-rockchip
lkcl_ has joined #linux-rockchip
cyrozap has joined #linux-rockchip
circuit has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
hessophanes has joined #linux-rockchip
lkcl_ has quit [Ping timeout: 269 seconds]
<opennandra>
robmur01: Yes Nanopi NEO4
<opennandra>
robmur01: Even in NEO4 kernel and not mainline?
<robmur01>
oh, I'd probably expect it to work in the 4.4 vendor kernel, but I haven't used that beyond first testing my NanoPC when it arrived :)
<opennandra>
robmu01: OK but 5.4 have support for FUSB302 just for my understanding (I'm not familiar with USB-C at all) what needs to be done to have OTG working in mainline?
ChanServ has quit [*.net *.split]
ChanServ has joined #linux-rockchip
<robmur01>
opennandra: as I understand things, the upstream FUSB302 driver is currently only useful for power delivery - the RK3399 USB (and presumably DisplayPort) phy drivers need converting to use the (relatively new) typec framework instead of extcon for everything to actually tie together
<opennandra>
robmur01: OK thanks a lot
jaganteki has quit [Remote host closed the connection]
<robmur01>
As it happens I spent a while last week trying to hack up the DT connector graph bits for nanopi4 boards, then found out that it wasn't going to work since the phy stuff was still missing, so gave up again :(
chiastre_ has quit [Ping timeout: 240 seconds]
Compy- has left #linux-rockchip [#linux-rockchip]
vicencb has quit [Read error: Connection reset by peer]