On 06/11/2007, <b class="gmail_sendername">Steven Toth</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gregoire Favre wrote:<br>> On Mon, Nov 05, 2007 at 01:52:26PM -0500, Steven Toth wrote:<br>>>>> At this stage I'm looking for a "Yes, in principle we like the idea, but<br>>>>> show me how you do feature XYZ" from other devs. At which point I'll flush
<br>>>>> out more code this would probably lead to an RFC for your approval.<br>>>><br>>>> Seems like no one is interested.<br>>> yeah, apparently.<br>><br>> Well, you only asked developpers... I think it would be a good idea...
<br><br>You and I appear to be in a very small minority.</blockquote><div><br><br>Ahem?! :) <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
><br>>> In reality, that was a year ago and maybe it's time to revisit DVB-S<br>>> support for the HVR4000. Given the current political climate I think I<br>>> like that idea. I'll rework the driver and present a patch later this week.
<br>><br>> HVR-4000 without DVB-S2 support could be added directly from<br>> <a href="http://dev.kewl.org/hvr4000/v4l-dvb-hg-2007-11-04.diff">http://dev.kewl.org/hvr4000/v4l-dvb-hg-2007-11-04.diff</a> which is based on
<br>> a removed hg repo. (See <a href="http://dev.kewl.org/hvr4000/">http://dev.kewl.org/hvr4000/</a> ).<br>><br>> I always wondered why this patch (or previous ones) weren't included in<br>> v4l-dvb ???<br>
<br><br>I built an new tree last night with HVR4000 and HVR4000lite support<br>taken from my other trees. After testing I'll likely push that tree up<br>this evening. My dish is compromised right now, so no doubt we'll have fun.
<br><br>Darron's patch has some IR and I2C related changes that I'm not<br>comfortable merging, without more information/investigation.<br><br>We can persue those after the test tree is built, and merge any<br>subsequent changes and/when required.
<br><br>This will be a good step forward.<br><br>- Steve</blockquote><div><br>As soon as the new tree is up, I'll grab it and give it a test out here. I am stuck for a couple of days with work, but can put in some testing time and report back anything I find.