nighty- has joined #linux-exynos
javier___ has quit [Remote host closed the connection]
genii has joined #linux-exynos
genii has quit [Quit: Howbout dem Leafs?]
Guest70902 has quit [Ping timeout: 250 seconds]
Guest47498 has joined #linux-exynos
Guest47498 has quit [Ping timeout: 258 seconds]
TheSeven has joined #linux-exynos
TheSeven is now known as Guest65624
mszyprow has joined #linux-exynos
javier__ has joined #linux-exynos
paulk-gagarine has quit [Ping timeout: 248 seconds]
paulk-gagarine has joined #linux-exynos
<forkbomb> mszyprow: does exynos4-fimc-is require CONFIG_EXYNOS_IOMMU to work? When trying to load fw, i get "exynos4-fimc-is 12000000.fimc-is: invalid firmware memory alignment: 0x7a500000"
<mszyprow> forkbomb: yes, IOMMU or properly aligned reserved memory
<mszyprow> forkbomb: but IOMMU is better
<mszyprow> forkbomb: besides that it works quite fine, but it requires some plugin to libv4l2 to configure the pipeline
<mszyprow> forkbomb: I'm not sure if it has been finally merged, AJacek Anaszewski was working on it long time ago
<mszyprow> -A
<forkbomb> ok, thanks
kloczek has quit [Ping timeout: 248 seconds]
<forkbomb> i guess it hasn't been merged
<mszyprow> forkbomb: you may try to resend and push libv4l2 maintainers to merge it, afair it was really close to get merged
<forkbomb> yeah it looks like they were waiting on a review that never got done
* forkbomb adds it to the never-ending TODO list
<snawrocki> forkbomb: for testing you could also use media-ctl to configure the pipeline
<snawrocki> IIRC gstreamer required S_INPUT ioctl and the v4l plugin emulated it
<snawrocki> it all depends what v4l application you intend to use
<snawrocki> in tizen normally gst camerasrc plugin is used to abstract the ISP details
kloczek has joined #linux-exynos
nighty- has quit [Quit: Disappears in a puff of smoke]
<forkbomb> snawrocki: for now, i just want to make sure i can get buffers from the camera on all the boards i'm working on
<willmore> Does anyone know the status of mainline for S5P4418 SoC?
<forkbomb> i don't think s5p4418 is related at all to exynos/any existing s5p socs
<mszyprow> willmore: S5P4418 is made by Nexel and it has not much common with Samsung S5PXXXX family
droman0 has quit [Ping timeout: 264 seconds]
indy has quit [Ping timeout: 255 seconds]
<snawrocki> forkbomb: then media-ctl + some simple v4l2 capture application is enough, are you working with i9300 or something else?
<forkbomb> snawrocki: i have i9300, i9305, and n7100/n7105. all are mostly the same
<forkbomb> i9305 == S3 4G, n7100/n7105 == Note 2 3G/4G
<forkbomb> hmm... i don't seem to have /dev/media0
<snawrocki> forkbomb: ok, for i9300 I should have simple test scripts for setting up the pipeline with media-ctl
<forkbomb> that sounds useful!
<snawrocki> forkbomb: are there any errors reported in kernel log when grepping for "fimc"?
<forkbomb> not sure if [ 7.678542] s5p-fimc-md camera: Entity type for entity FIMC.0 was not initialized! is an error, too
mszyprow has quit [Read error: Connection reset by peer]
<snawrocki> forkbomb: No, it's just a warning, can you, could you put the log on pastebin.com instead?
<forkbomb> sure
<forkbomb> the offending line in the source is drivers/media/platform/exynos4-is/fimc-lite.c:531 (discriminator 1)
<snawrocki> forkbomb: new kernel, new bugs as it seems, It's been a while since I last time looked at exynos4x12 camera subsystem driver in mainline, could you post whole log?
<forkbomb> yep
<snawrocki> Maybe I will find time to get the board and check it myself
mszyprow has joined #linux-exynos
<snawrocki> forkbomb: but let us try to debug it first
<snawrocki> forkbomb: You don't have these enabled in kernel config: CONFIG_VIDEO_S5C73M3, CONFIG_VIDEO_S5K6A3 ?
<forkbomb> both are =m
<snawrocki> it looks like pipeline close code is now not exactly prepared for pipeline with missing sensor subdevs
<forkbomb> alright
<snawrocki> Can you make them "y" for now?
<snawrocki> there were some significant changes in the v4l2-async API recently
<forkbomb> yeah, i can make them "y" for now
<snawrocki> And VIDEO_EXYNOS_FIMC_LITE, VIDEO_EXYNOS4_FIMC_IS
nighty- has joined #linux-exynos
<willmore> mszyprow, that's the info I'm looking for, thanks.
<forkbomb> snawrocki: i think the fix might be as simple as this: https://pastebin.com/uy9VrwkH
<forkbomb> at least, i have /dev/media0 now
<snawrocki> forkbomb: looks good at first sight, feel free to submit a patch
droman0 has joined #linux-exynos
genii has joined #linux-exynos
<forkbomb> snawrocki: do you know if trats2 uses the same fimc-is firmware as the retail i9300?
<snawrocki> forkbomb: I'm not sure now what's the exact retail i9300 FW version, can you check it with
<snawrocki> strings <fw_file> | tail -1
<snawrocki> ?
<snawrocki> I have [E4412 540-2012/10/22 11:32:18]OABJ22
<forkbomb> [E4412 420-2012/04/16 13:30:52]OABD16
<snawrocki> with the trats2 firmware binary
<snawrocki> hm
<forkbomb> hang on, that might be from an old android release
<forkbomb> [E4412 533-2012/10/06 14:38:46]OABJ06
mszyprow has quit [Ping timeout: 276 seconds]
<forkbomb> i wonder if i can do any newer than that
<forkbomb> nope, 533 is the newest i can find
<snawrocki> forkbomb: mszyprow has the trats2 board set up for camera tests, I think we could test tomorrow if your latest FW version works properly with the mainline driver
willmore has quit [Ping timeout: 248 seconds]
willmore has joined #linux-exynos
Ultrasauce has quit [Remote host closed the connection]
Ultrasauce has joined #linux-exynos
<forkbomb> snawrocki: thanks. I emailed the firmware to you and mszyprow
nighty- has quit [Quit: Disappears in a puff of smoke]