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