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
stikonas has quit [Remote host closed the connection]
aalm has quit [Quit: xyz 2.3]
aalm has joined #linux-rockchip
<wens> fALSO: there's an ffmpeg fork that can use the request API
imsherlock has quit [Ping timeout: 240 seconds]
return0e has joined #linux-rockchip
return0e has quit [Ping timeout: 240 seconds]
imsherlock has joined #linux-rockchip
imsherlock has quit [Client Quit]
<kevery> anarsoul: The HDMI driver should be work for rk3399, but I'm not expert on this driver, you will need to make sure it's probed first, it needs pro-relocate tag.
<kevery> levd: For the USB issue, the simple way is to disblae "CONFIG_ROCKCHIP_USB2_PHY=y" for rk3288.
<anarsoul> kevery: both vops have pre-reloc tag
<levd> kevery: rockusb & ums both work for rk3288. I need to bring them up for rk3399. Seems the dwc3 otg support is broken at my last attempt.
<anarsoul> *sigh* todays git master stucks in SPL on rockpro64 for me :\
<anarsoul> on "Trying to boot from MMC1"
return0e has joined #linux-rockchip
return0e has quit [Ping timeout: 240 seconds]
elektirnis has quit [Read error: Connection reset by peer]
elektirnis has joined #linux-rockchip
yann has quit [Ping timeout: 246 seconds]
ldevulder_ is now known as ldevulder
stikonas has joined #linux-rockchip
yann|work has joined #linux-rockchip
<sigmaris> fALSO: the userspace API (v4l2 request API) for the hantro VPU is not quite stable
<sigmaris> fALSO: if you use this branch https://github.com/Kwiboo/FFmpeg/tree/v4l2-request-hwaccel-4.0.4-hantro it *should* work
<sigmaris> but a large caveat applies; I'm building experimental kernels with patches from the mailing list
<sigmaris> the uapi is likely to change, and that means future kernels might not work with that FFmpeg
<fALSO> ;-D
<fALSO> i've been following your branch
<fALSO> i saw some new hantro patches no patchworks
<fALSO> you need to update ;-D
<fALSO> i found the patchworks website yesterday
<fALSO> didnt even knew it ;-D
<fALSO> yes that one
<sigmaris> problem is, I've applied https://patchwork.kernel.org/project/linux-rockchip/list/?series=168159 to my branch, and it conflicts with some of the other patches
<sigmaris> like I said - everything is unstable atm ;)
<sigmaris> not meaning it crashes, but I mean changing rapidly
<fALSO> ahhhhh
<fALSO> hehe
<fALSO> no prob
<fALSO> previously i've been playing with "sunxi" allwinner devices
<fALSO> recently they also started to have "cedrus" is the same as hantro i belive
<fALSO> ;-D
<sigmaris> it also uses the v4l2-request API, yes
<wens> there's still some subtle differences, but that's mostly up to the driver and application
<fALSO> yes sigmaris
<sigmaris> the build process I use for the kernel is public, btw, and you can run your own builds if you want
<sigmaris> I set up a free project on Azure Pipelines, using this: https://github.com/sigmaris/linux/blob/ci-5.4-rc3-hantro-ayufan-v1/azure-pipelines.yml
<sigmaris> and it uses a Docker image built from this to run in: https://github.com/sigmaris/dockerfiles/blob/master/aarch64-linux-crossbuilder/Dockerfile
elektirnis has quit [Quit: elektirnis]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-rockchip
drrty has quit [Remote host closed the connection]
drrty has joined #linux-rockchip
return0e has joined #linux-rockchip
adjtm has quit [Ping timeout: 240 seconds]
return0e_ has joined #linux-rockchip
return0e has quit [Ping timeout: 240 seconds]
kevery has quit [Ping timeout: 276 seconds]
return0e_ has quit []
adjtm has joined #linux-rockchip
vicencb has joined #linux-rockchip
return0e has joined #linux-rockchip
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
BenG83 has joined #linux-rockchip
field^Mop has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-rockchip
ldevulder has joined #linux-rockchip
ayaka has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-rockchip
ayaka has joined #linux-rockchip
ldevulder has quit [Read error: Connection reset by peer]
ldevulder has joined #linux-rockchip
yann|work has quit [Ping timeout: 240 seconds]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 240 seconds]
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
adjtm has quit [Ping timeout: 240 seconds]
adjtm has joined #linux-rockchip
aalm has quit [Ping timeout: 265 seconds]
aalm has joined #linux-rockchip
<anarsoul> are there any known issues with u-boot on rk3399? the same build booted fine for me on rockpro64 one day, and then it doesn't work on another
ganbold has quit [Ping timeout: 265 seconds]
JohnDoe_71Rus has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
jwerner has quit [Quit: leaving]
jwerner has joined #linux-rockchip
<mmind00> anarsoul: I'm puzzled about boot reports often anyway ... aka on most Rockchip SoCs there is an issue doing dma between mmc and sram (when spl loads the atf sram part)
<anarsoul> mmind00: any workarounds?
<mmind00> anarsoul: yep ... give me a second to find it again ... (resolving that is one thing sitting on my todo list)
<mmind00> anarsoul: https://patchwork.ozlabs.org/patch/1096413/ + the patches listed under "Related"
<anarsoul> thanks
<anarsoul> why it hasn't landed in master yet?
<mmind00> and as we ran into that issue on multiple socs, I'm always not sure how people actually make it work ;-)
<mmind00> anarsoul: why not landed - see discussion in that patch ... it's on my figure out how to convince Simon list :-D
<anarsoul> :\
<anarsoul> I'll try the patches tonight, thanks
<anarsoul> mmind00: why not to just disable DMA for mmc driver?
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
<anarsoul> I assume https://gist.github.com/anarsoul/f5f6e66e5adc962337f38802fec78115 should do the trick and can probably be accepted upstream until dma issue is resolved
<mmind00> anarsoul: downside being that then nothing can dma from sdmmc sources (like loading kernel, initramfs, etc) - which might slow things down considerably ... but yeah, would be better than not starting at all
<anarsoul> mmind00: well, emmc already uses pio (neither DMA mode is enabled by default for sdhci driver)
<anarsoul> btw it's quite surprising to see 2 kinds of sd/mmc controllers in one soc :)
<mmind00> anarsoul: maybe the arasan-sdhci was less quirky ... or cheaper ;-)
<anarsoul> but they likely bought licenses for dwmmc and sdhci
<anarsoul> so it's not clear why not to use 2 of the same kind
imsherlock has joined #linux-rockchip
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
ifbizo_ has quit [Remote host closed the connection]
ifbizo_ has joined #linux-rockchip
robmur01 has quit [Ping timeout: 246 seconds]
drrty has quit [Remote host closed the connection]
drrty has joined #linux-rockchip
warpme_ has quit [Quit: Connection closed for inactivity]
BenG83 has quit [Quit: Leaving]
field^Mop has quit [Ping timeout: 240 seconds]