Yes,<br><br>I meant the mailing list as a group.<br><br>I want to add that I know coding the drivers themselves is more important (everybody hates documentation), but what use is a valid driver if almost no-one knows how to use it .. or worse that it exists?!?!
<br><br><div class="gmail_quote">On Jan 16, 2008 4:01 PM, Steven Toth <<a href="mailto:stoth@linuxtv.org">stoth@linuxtv.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Jean Paul Gatt wrote:<br>> In the meantime ...<br>><br>> While the whole kernel debate goes on ...can the wiki be updated with a<br>> semi-standard procedure to follow ?<br>><br>> Something on the lines ... you need this basic code <LINK> .. and patch
<br>> it with this diff file <LINK>.<br>><br>> Nothing too complex! I'm just like Ian. Been following development on<br>> this card for almost a year now, and I click on every HVR4000 related<br>> mail hoping to see ISSUES RESOLVED, especially since the card should now
<br>> practically work!<br>><br>> Having said that .... BIG Thanks for all the hard work all developers<br>> put into it!<br>><br>> On Jan 16, 2008 3:28 AM, Steven Toth <<a href="mailto:stoth@linuxtv.org">
stoth@linuxtv.org</a><br></div><div class="Ih2E3d">> <mailto:<a href="mailto:stoth@linuxtv.org">stoth@linuxtv.org</a>>> wrote:<br>><br>> Ian Bonham wrote:<br>> > Steve,<br>> ><br>
> > Is there anything that can be done now to progress the dev of this<br>> > driver and the facilities of this card? I remember clearly the<br>> > disagreements that occured, and it was hugely depressing. What
<br>> would be<br>> > needed now to encorage development?<br>> ><br>> > Ian<br>> ><br>> ><br>> > On 15/01/2008, *Steven Toth* <<a href="mailto:stoth@linuxtv.org">
stoth@linuxtv.org</a><br>> <mailto:<a href="mailto:stoth@linuxtv.org">stoth@linuxtv.org</a>><br></div><div class="Ih2E3d">> > <mailto:<a href="mailto:stoth@linuxtv.org">stoth@linuxtv.org</a> <mailto:
<a href="mailto:stoth@linuxtv.org">stoth@linuxtv.org</a>>>> wrote:<br>> ><br>> > Hans Werner wrote:<br>> > > -------- Original-Nachricht --------<br>> > >> Datum: Tue, 15 Jan 2008 16:18:11 +0300
<br>> > >> Von: Igor < <a href="mailto:goga777@bk.ru">goga777@bk.ru</a> <mailto:<a href="mailto:goga777@bk.ru">goga777@bk.ru</a>><br></div>> <mailto:<a href="mailto:goga777@bk.ru">
goga777@bk.ru</a> <mailto:<a href="mailto:goga777@bk.ru">goga777@bk.ru</a>>>><br><div class="Ih2E3d">> > >> An: <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a> <mailto:
<a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a>><br></div>> <mailto: <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a> <mailto:<a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org
</a>>><br><div><div></div><div class="Wj3C7c">> > >> Betreff: Re: [linux-dvb] HVR-4000<br>> > ><br>> > >>> b)explain how and when all the pieces of DVB-S2-relevant
<br>> code<br>> > will be<br>> > >> merged into the kernel and dvb-apps.<br>> > >><br>> > >> ahh, I think nobody knows the answer on this question.
<br>> > >><br>> > >> Igor<br>> > >><br>> > >><br>> > ><br>> > > I have read the previous correspondence on this issue.
<br>> There is<br>> > considerable working code so I would like to hear from the<br>> > > maintainer(s) where we go from here. It's 2008 already.<br>> ><br>> > You might want to cc the maintainer if you expect a response. :)
<br>> ><br>> > The driver was written during 2006 and for various technical<br>> reasons<br>> > could not be fully merged into the kernel. This lead to a major<br>> > conflict
<br>> > between kernel developers. As a result of a major<br>> disagreement I took<br>> > down my development trees and instructed Mauro not to merge<br>> my code with<br>> > my agreement.
<br>> ><br>> > A few trusted members of the community have taken the<br>> previously public<br>> > tree and patched it and made it available for download, which<br>> is well
<br>> > within the license agreement.<br>> ><br>> > The HVR4000 driver isn't going anywhere soon, it isn't going<br>> to be<br>> > official merged anytime soon. I made myself clear a few
<br>> months ago<br>> > during the heated multiproto debate.<br>> ><br>> > That's where we stand today.<br>> ><br>> > - Steve<br>><br>> Ian,
<br>><br>> It's times like this when I find myself re-writing emails multiple<br>> times, trying to find the right words and facts to reflect the true<br>> situation, not an emotional response.
<br>><br>> How do I start? Hmm, well....<br>><br>> I hear you.<br>><br>> Background: The HVR4000 patches are based on the Multiproto patches.<br>><br>> You should probably recognize that the situation has always been outside
<br>> of my control. I've tried to urge multiproto forward many times and in<br>> the end, driven by pure frustration, both Manu and I argued publically,<br>> it got personal and everyone walked away badly burned.
<br>><br>> No heroes. No villains. No right, no wrong.<br>><br>> It was obvious to me that I could not influence the situation. In<br>> response I took my development trees down and stated that I no longer
<br>> supported multiproto.<br>><br>> What's my position now? I'll review the HVR4000 situation when Manu<br>> gives the S-O-B for his patches and they are merged by Mauro into<br>> master.
<br>><br>> What should the community do? You could raise the subject with Manu.<br>><br>> No multiproto in the master = no HVR4000 S2 in the master.<br>><br>> - Steve<br><br></div></div>Hi,<br>
<br>I assume this suggestion was posted to the mailing list as a group,<br>rather than directly to me. Specifically, it should be aimed at the<br>people who are already producing hierarchies of patches on top of<br>multiproto, HVR4000 and various other things.
<br><br>That isn't me, and I didn't want you to be waiting for a non-reply from me.<br><br>Darron has being doing a great job at <a href="http://kewl.org" target="_blank">kewl.org</a> (?), he may be able to help.<br>
<br>- Steve<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.e-kavallieri.com">http://www.e-kavallieri.com</a>