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
return0e has quit [Ping timeout: 265 seconds]
return0e has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
BenG83 has quit [Quit: Leaving]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 240 seconds]
perr_ has joined #linux-rockchip
field^Mop has quit [Ping timeout: 268 seconds]
perr__ has joined #linux-rockchip
perr_ has quit [Ping timeout: 240 seconds]
perr__ has quit [Ping timeout: 240 seconds]
stikonas has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 245 seconds]
<anarsoul> micken: configuring aclk and hclk is not enough to get it working :(
<anarsoul> USB doesn't for for me in u-boot either
<anarsoul> that's annoying :\
<anarsoul> basically sd, emmc and serial are the only things that work
<anarsoul> mmind00: any idea how to get usb working in u-boot on rockpro64?
<anarsoul> from what I can tell there's no power on USB
<anarsoul> but according to 'dm tree' regulators are probed
kaspter has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
PoueT7 has quit [Ping timeout: 244 seconds]
<anarsoul> kevery: ping
PoueT7 has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vstehle has joined #linux-rockchip
<anarsoul> vagrantc: did you get usb working in u-boot on your rockpro64?
<vagrantc> anarsoul: i don't recall
ayaka has quit [Ping timeout: 250 seconds]
ayaka has joined #linux-rockchip
ayaka has quit [Ping timeout: 240 seconds]
perr__ has joined #linux-rockchip
perr__ has quit [Excess Flood]
perr__ has joined #linux-rockchip
ldevulder_ is now known as ldevulder
imsherlock has quit [Remote host closed the connection]
perr__ has quit [Ping timeout: 268 seconds]
vagrantc has quit [Quit: leaving]
<mmind00> anarsoul: can you compare kernel dts and uboot dts? making sure that regulators are the same
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 265 seconds]
camus is now known as kaspter
<kevery> anarsoul: You want to enable usb host driver on rockpro64? there are multi usb host ports, You need to make sure the VBUS is on for the USB port, and then make sure the usb driver is probed.
nlhowell has joined #linux-rockchip
<nlhowell> can anyone advise me on compiling mainline for my c201 chromebook (rk3288, speedy-veyron)?
<nlhowell> i tried using the kernel config and patches from PrawnOS, but wasn't able to succeed using gcc-8.3.0-r1
<nlhowell> err gcc-8.3.0
<EmilKarlson> why patches?
<nlhowell> you can take a look at the list, but the important ones have to do with weird partitioning issues on internal mmc on chromebooks
<nlhowell> and some unreliability with emmc resets (iiuc)
<nlhowell> is someone here booting pure mainline on a c201?
<nlhowell> if so, i would love to ask a couple questions about toolchain and kconfig
<nlhowell> sorry, "the list" refers to PrawnOS
<nlhowell> i had compiled a working 5.3.2 kernel, but accidentally lost it
<nlhowell> (note to self: don't dd kernels to the system partition)
<nlhowell> and haven't been able to reproduce since reinstalling my system
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 268 seconds]
kaspter has joined #linux-rockchip
<urjaman> nlhowell: i build a mainline-ish kernel for my c201 - https://github.com/urjaman/arch-c201/tree/master/linux-test currently has the pkgbuild for 5.4-rc6 (+ a small pile of patches, including that emmc thing...)
<urjaman> dunno if you're running arch tho (and dunno what it has to do with the gcc used - the 8.3 that arch ships works fine for me...)
matthias_bgg has joined #linux-rockchip
<nlhowell> ok, and you compile on-device, not cross-compile?
<nlhowell> urjaman: ^
<urjaman> if you cant build the kernel because you cant boot the system because you dont have a booting kernel, i do have some (not often updated, but i updated it right now) kernel packages at https://urja.dev/linux-c201/test/
<urjaman> yeah on-device
<nlhowell> i have a debian rescue disk
<nlhowell> which i can use, but it is very inconvenient
<nlhowell> but thank-you, i will download and try your precompiled kernel
<nlhowell> because right now i am just looking for *any* kernel that can boot my system
<nlhowell> what are the differences between the two files? one has "-chromebook" in its name, but both say "c201"...
<urjaman> the -chromebook has the chromebook-style kernel partition image
<urjaman> you need the other one always (has the modules)
<nlhowell> ok
<nlhowell> chromebook-style partition image means vboot-signed fit?
<urjaman> it' installed as boot/vmlinux.kpart and then stuffed into the partition by an arch hook usually
<nlhowell> ah ok
nlhowell has quit [Quit: WeeChat 2.6]
<urjaman> i boot with u-boot these days so i havent tested the -chromebook one (especially as you can only practically have one kernel like that...), but it's built...
<urjaman> and he left.
field^Mop has joined #linux-rockchip
vicencb has joined #linux-rockchip
perr__ has joined #linux-rockchip
perr_ has joined #linux-rockchip
perr__ has quit [Ping timeout: 250 seconds]
perr_ has quit [Ping timeout: 276 seconds]
perr_ has joined #linux-rockchip
chewitt has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
<micken> anarsoul: usb works for me in u-boot
<micken> anarsoul: did you try the hdcp thing?
ldevulder has quit [Ping timeout: 240 seconds]
perr has joined #linux-rockchip
perr_ has quit [Ping timeout: 240 seconds]
perr has quit [Ping timeout: 265 seconds]
<micken> anarsoul: that version works pretty well, I use tftp boot with it and use it to power up usb
<micken> anarsoul: but I havent checked the functionality of the usb driver
<micken> anarsoul: I just do usb start before I load my osimage
perr has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
camus has joined #linux-rockchip
<micken> anarsoul: but I think usb shouldnt be any problem , if using ehci (one port on rockpro64). I use our standard ehci driver , by just popping in echi base address
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
perr has quit [Ping timeout: 276 seconds]
<micken> anarsoul: do you know if I can trick u-boot to use A72 from bootup instead of 53?
<robmur01> micken: AFAICS you'd have to hack in a whole bunch of SMP bringup code
<robmur01> can't really see that being worthwhile :/
<micken> ok
<micken> I just was curious if it was easy , because I want to see what happens if riscos starts on A72
<robmur01> in principle it should be somewhat easier to switch right at the *end* of u-boot, i.e. when you bootm (or whatever)
<micken> ok thats exactly what I want to do
<micken> right now I do switch to aarch32 at that time
<micken> a hack
<robmur01> by that point PSCI should be ready, and hopefully the target is expecting to initialise CPUs from scratch anyway
<micken> ok I have no clue in how that works :D
<micken> it isnt important right now, but it is something I want at a later stage
JohnDoe_71Rus has joined #linux-rockchip
<robmur01> essentially, if you're not relying on any CPU state left over from u-boot, then making a PSCI CPU_ON call to launch a different CPU into your entrypoint ought to work
<micken> robmur01: thanks, will look at that
cyteen has quit [Ping timeout: 276 seconds]
<hanetzer> sphalerite: oh, its a bob. I've never dealt with the cr50-bearing devices
<anarsoul> micken: I use mainline u-boot. HDCP thing didn't work
<anarsoul> mmind00: kevery: vcc5v0_host is probed and it's regulator-fixed with gpio = <&gpio4 RK_PD2 GPIO_ACTIVE_HIGH>;
<anarsoul> host drivers are also probed
ganbold has quit [Remote host closed the connection]
ldevulder__ has joined #linux-rockchip
aalm has quit [Quit: xyz 2.3]
ldevulder_ has quit [Ping timeout: 268 seconds]
ldevulder__ is now known as ldevulder
matthias_bgg has quit [Quit: Leaving]
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
camus is now known as kaspter
camus has joined #linux-rockchip
robmur01 has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 268 seconds]
camus is now known as kaspter
robmur01 has joined #linux-rockchip
vagrantc has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
robmur01 has quit [Remote host closed the connection]
robmur01 has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
camus has joined #linux-rockchip
camus is now known as kaspter
aalm has joined #linux-rockchip
marvs has joined #linux-rockchip
stikonas has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 268 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
imsherlock has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
inode has quit [Quit: ]
adjtm has joined #linux-rockchip
imsherlock has quit [Remote host closed the connection]
imsherlock has joined #linux-rockchip
imsherlock has quit [Read error: No route to host]
imsherlock has joined #linux-rockchip
imsherlock has quit [Remote host closed the connection]
imsherlock has joined #linux-rockchip
imsherlock has quit [Read error: Connection reset by peer]
vicencb has quit [Quit: Leaving.]
<anarsoul> kevery: I can't find a driver in u-boot that supports usb phys on rk3399
<anarsoul> is it even supposed to work?
<stikonas> anarsoul: I was able to boot from usb on rk3399, so there must be usb driver...
<wbn> can someone explain how u-boot for rockpi is built differently than u-boot for any other board?
<anarsoul> stikonas: mainline u-boot? what commit?
<anarsoul> stikonas: "egrep -R rockchip,rk3399-usb2phy u-boot" finds something only in dts
<anarsoul> same for "rockchip,rk3399-typec-phy"
<stikonas> anarsoul: well, I think it was stable...
<stikonas> when I tried
<anarsoul> stable what?
<anarsoul> what u-boot you were running at the time?
<stikonas> 2019.10
<anarsoul> well, doesn't work for me :(
<stikonas> which rk3399 board?
<stikonas> mine is rockpro64...
<anarsoul> rockpro64
<stikonas> ok, so the same...
<anarsoul> are you using mainline ATF and SPL?
<stikonas> yes
<anarsoul> or you're using miniloader from rockchip?
<stikonas> mainline
<stikonas> blob free....
<stikonas> at the moment I'm actually updated to ATF git master (2.2)
<anarsoul> right, saw your post
<stikonas> which needed one extra u-boot config change
<stikonas> but still works after that
<anarsoul> try updating your u-boot? :)
<stikonas> yeah, updated...
<stikonas> well, the needed change was in defconfig
<stikonas> so need to change config manually anyway if I run make oldconfig
<anarsoul> CONFIG_ROCKCHIP_SPL_RESERVE_IRAM=0x0 I suppose
<stikonas> so I think I tried debian cd...
<stikonas> yeah, right
<stikonas> although, debian's kernel is too old, so kernel itself did not boot
<anarsoul> well
<anarsoul> 'usb start' doesn't detect my usb devices
<stikonas> is that what is run by distroboot cmd?
<anarsoul> 'usb tree' shows only hubs
<anarsoul> likely
<stikonas> hmm, well, I haven't tried these commands, just used distroboot to boot live usb...
<anarsoul> what's your 'git describe' output for u-boot tree?