<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   hverkuil: hi mauro
   syoung: hi all
   hverkuil: <u>pinchartl</u>: sailus: ping
   <br> While waiting for them I can give an update: my compliance tests for a stateful encoder are almost done, hope to finish it tomorrow. Based on those tests I proposed some changes for the next version of the stateful encoder spec, so that needs to be agreed with Tomasz first.
   mchehab: good
   hverkuil: Dafna told me she wants to work in her own time on the stateless encoder support in vicodec, so that would be nice to have as well.
   mchehab: as a reminder, I'll be OOT from tomorrow up to April, 20
   <br> so, I applied pending patches earlier this week
   <br> will try to do another spin before departuring
   <br> either today or tomorrow
   hverkuil: OK, good to know. I'll try to make a pull request with bug fixes today.
   mchehab: I'll likely apply pending patches once per week, except for the next week
   <br> s/pending patches/pending pull requests/
   <br> @all, feel free to handle patches that I would usually pick myself - if any - and put on your PRs
   sailus: Hello!
   hverkuil: <u>mchehab</u>: before you leave, can you clean up patchwork? I.e. set all patches you've already handled to Accepted so that they don't appear in the list anymore?
   mchehab: I do that when I merge stuff
   <br> well, if the patch doesn't change
   sailus: I'll try to send my pending stuff today. There's not a lot.
   syoung: <u>mchehab</u>: I haven't looked at this patch in detail, but I would like your opinion before you OOT please. https://patchwork.linuxtv.org/patch/54831/
   mchehab: my script takes a checksum from the patch content in order to compare two patches. It ignores the patch description/subject when calculating the checksum
   <br> <u>syoung</u>: that has the potential of breaking lots of things
   syoung: yes exactly
   <br> I tried reproducing the warning and failed, so it might not be an issue any more. However I need to spend a lot more time on it.
   <br> if you don't know then let me spend time on it first
   mchehab: <u>syoung</u>: yeah, either that or to use the new i2c binding way
   <br> with would be better, but may require more time
   <br> well, it could be done just for stb0899, but you'll likely need a device with it in order to test
   hverkuil: <u>mchehab</u>: patchwork is indeed clean, but there are a bunch of cleanup  and vim2m patches from you. I think those can be merged (provided vim2m passes the 'test-media vim2m' test suite).
   mchehab: just ignore patches I authored
   <br> I'll try to cleanup those before leaving
   <br> btw, it seems that vim2m's one of RGB15 formats are handled wrong
   <br> (at least colors are wrong when testing with qvidcap)
   <br> I remember I had fixed that before
   <br> but either something changed at qvidcap or I ended by merging a wrong version
   <br> I'll see If I can fix it before leaving
   <br> it is at	[1]: 'RGBR' (RGB565 (BE))
   <br> at the capture interface
   hverkuil: I see you use this in vim2m.c: u16 pix = *(u16 *)(src[i]);
   mchehab: hmm... it has endiannes issues
   <br> good point
   hverkuil: right :-)
   mchehab: bbiab
   hverkuil: Shall we still have a quick meeting for the next few weeks, even though Mauro is on vacation? I think it is useful to touch base.
   <br> Except perhaps on the 18th since I'm on vacation as well that week.
   mchehab: back
   <br> if you decide to keep the meetings (IMO, it makes sense), I'll follow it via backlogs
   hverkuil: Let's keep them for the next two weeks and just skip the one on the 18th.
   mchehab: well, if are there enough people for 18th, they can still do a meeting on such day
   pinchartl: <u>hverkuil</u>: pong
   <br> sorry, I was flying back from Tokyo
   <br> or rather travelling from the plane to home