| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| tockitj | kbingham_, sorry for late response (night passed in my timezone), here is command output: https://gist.github.com/anonymous/e632edfbafda4081e4eed6d5ef1131a3 | [08:00] |
| oddly enough this is clearly 2megapixel camera when image is viewed in windows | [08:11] | |
| Hmm.. three are 3 failures in compliance test (v4l2-compliance): https://gist.github.com/anonymous/dd1c4496805d8947eb2b83011df1c1a1 | [08:18] | |
| ......... (idle for 44mn) | ||
| mchehab | sailus: just pushed 4.12-rc1
together with a fix that won't crash the build with atomisp driver | [09:02] |
| ............ (idle for 55mn) | ||
| hverkuil: as we merged back the atomisp driver, we'll be handling patches for it via our tree... So, we should stop marking those patches as "not applicable" | [09:57] | |
| *** | neg has quit IRC (Read error: Connection reset by peer) | [09:57] |
| mchehab | I'll sync with greg and alan with regards to any patches that were sent already, pending merge | [09:58] |
| hverkuil | mchehab: Thanks for letting me know. And yuck, I am really not looking forward to having to wade through all the atomisp patches.
To be honest, I would prefer if someone from Intel would collect/review those patches, at least until it is in a better shape than it is now. | [10:01] |
| mchehab | well, alan is doing that job
yeah, the driver is on very bad shape from my PoV, everything that alan acked or send us while the driver is still on staging should be applied | [10:02] |
| hverkuil | So Alan will send periodic pull requests to you? I don't have to be involved, at least for now? | [10:03] |
| mchehab | no need for a deep review
yeah, I don't think you need to be involved not sure yet if Alan will send those as pull requests or patch series I guess that, with Greg, he's sending patch series anyway, as atomisp will appear on our build (and will produce *hundreds* of warnings), I guess it is for the best if we handle it via our tree I'll likely try to shut up those warnings when I have some time, if nobody does that before me | [10:04] |
| hverkuil | OK. So for now I am not doing anything. If you want me to do something (such as collecting those patches into pull requests), then let me know. | [10:08] |
| mchehab | ok! thanks!
(you may collect them - but let me first sync with alan/greg, as greg has still a pile of patches there) | [10:10] |
| hverkuil | Yes, they need to sync up with you first. | [10:17] |
| .... (idle for 16mn) | ||
| *** | benjiG has left | [10:33] |
| ttomov | pinchartl: Hi
I'll have to get back to the upstreaming of the QC camera driver, so when you have time please check the questions which I have sent I'll be on vacation next week but after that I continue with this I have some new features too - UYVY to NV12 conversion in VFE. Now I also have resizer and crop support in VFE for NV12 but for these I'm still waiting for clearance to publish. | [10:40] |
| hverkuil | mchehab: please take a look at the pending 4.12 pull requests: I have two, and I think there are others as well. Important regression fixes. | [10:44] |
| mchehab | hverkuil: yeah, I'm handling them already
I already applied some things, but it is hard to test with all those warnings I'm needing to change my scripts for now after applying the pending requests, I'll work on cleaning up the warnings with gcc 7.1, there are several new warnings even without atomisp hverkuil: btw, it seems you sent two pull requests with the same patches it this pull request superseded? Patchwork: http://patchwork.linuxtv.org/patch/41065/ | [10:53] |
| hverkuil | Yes, that's superseded. Did I forget to mark it as such? | [11:04] |
| sailus | mchehab: Great, thanks! :-) | [11:06] |
| mchehab | hverkuil: yes, it was marked as new. just updated it
sailus: anytime | [11:08] |
| ............ (idle for 58mn) | ||
| sailus | neg: Rebased the v4l2-acpi branch and sent the pull request. | [12:06] |
| ........ (idle for 37mn) | ||
| hverkuil | Notice: I am away for the next three days, but I plan on going through pending patches on Monday and make pull requests for them if they are OK. | [12:43] |
| .............. (idle for 1h6mn) | ||
| kbingham_ | mchehab: Hi Mauro, I have patches submitted at https://www.spinics.net/lists/linux-renesas-soc/msg13945.html which change both RCarDU (DRM) and VSP1. How would you like to see those get integrated. Can I get your ACK for integration through DRM, or should I get an ACK from DRM to go through linux-media? | [13:49] |
| mchehab | kbingham_: either way would work...
the best would be to submit it via the tree with is more pertinent. just based on the changelog, it seems that this is more a DRM-related change so I guess the best would be to get VSP1 maintainer's ack (and me) and submit via DRM tree | [13:51] |
| kbingham_ | mchehab: Yes, it fixes the DRM pipeline (but touches the VSP)
mchehab: Ok, lets go that way then Thanks. | [13:52] |
| mchehab | just sent my ack | [13:54] |
| kbingham_ | mchehab: Thankyou :) | [13:54] |
| mchehab | anytime | [13:54] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |