#linux-exynos on 2017-05-19 — irc logs at freenode.irclog.whitequark.org

2014-05-14 17:51 Wizzup changed the topic of #linux-exynos to: This channel is logged: http://irclog.whitequark.org/linux-exynos | http://linux-exynos.org | http://lists.linux-exynos.org/listinfo/linux-exynos | https://github.com/linux-exynos

00:23 nighty-- has joined #linux-exynos

02:18 genpaku has quit [Read error: Connection reset by peer]

02:20 genpaku has joined #linux-exynos

04:40 [7] has quit [Ping timeout: 260 seconds]

04:41 TheSeven has joined #linux-exynos

05:20 mszyprow has joined #linux-exynos

09:18 nighty-- has quit [Quit: Disappears in a puff of smoke]

10:15 nighty-- has joined #linux-exynos

13:16 paulk-collins has joined #linux-exynos

13:30 Vasco_O is now known as Vasco

14:09 genii has joined #linux-exynos

14:32 afaerber has quit [Quit: Leaving]

15:23 nighty-- has quit [Quit: Disappears in a puff of smoke]

15:35 mszyprow has quit [Ping timeout: 240 seconds]

16:57 afaerber has joined #linux-exynos

18:34 LiquidAcid has joined #linux-exynos

18:39 glLiquidAcid has joined #linux-exynos

18:39 glLiquidAcid has quit [Remote host closed the connection]

18:44 <LiquidAcid> i was wondering if there is any documentation available for S5P_FIMV_CH_INIT_BUFS and related commands

18:44 <LiquidAcid> used e.g. here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/platform/s5p-mfc/s5p_mfc_opr_v5.c#n504

18:45 <LiquidAcid> it seems that without issuing INIT_BUFS, changes to the DPB addresses above (luma and chroma) are not forwarded to the mfc

18:46 <LiquidAcid> my question is whether it is possible to change DPB addresses "on-the-fly", which would imply that INIT_BUFS doesn't reset any internal state

18:48 <LiquidAcid> another idea would be to use FRAME_START_REALLOC for this, but again, that's speculation based on the name

18:56 libv_ has joined #linux-exynos

18:59 libv has quit [Ping timeout: 240 seconds]

23:46 genii has quit [Remote host closed the connection]