On Saturday 20 January 2007 15:51, Maarten Maathuis wrote:
> Will you do that? (i'm not really that well informed on ivtv
> sourcecode)
I'll do it. Actually, I think I'm going to redesign the code that uses
the semaphore, it's much too complicated for what it does.
Hans
>
> Maarten.
>
> On 1/20/07, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > On Saturday 20 January 2007 13:13, Maarten Maathuis wrote:
> > > Here is a patch that should fix this issue.
> >
> > Looking at the patch I see that it can be made simpler by just
> > replacing the semaphore with a mutex. It's the only one not yet
> > converted to a mutex.
> >
> > Hans
> >
> > > Maarten.
> > >
> > > On 1/20/07, Maarten Maathuis <[EMAIL PROTECTED]> wrote:
> > > > I meant, i still use 2.6.19, and i get that error, which may
> > > > mean there is still a less than obvious bug to fix for me.
> > > >
> > > > Maarten.
> > > >
> > > > On 1/20/07, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > > > > On Saturday 20 January 2007 12:26, Maarten Maathuis wrote:
> > > > > > The current svn seems to compile without change, but i get
> > > > > > one error:
> > > > > >
> > > > > > ivtv: Unknown symbol
> > > > > > there_is_no_init_MUTEX_LOCKED_for_RT_semaphores
> > > > > >
> > > > > > I suspect that is something 2.6.20 related?
> > > > >
> > > > > Might well be the case. I haven't compiled against
> > > > > 2.6.20-rcX. I usually wait with that until the new kernel is
> > > > > actually released.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hans
> > > > >
> > > > > > Maarten.
> > > > > >
> > > > > > On 1/20/07, Hans Verkuil <[EMAIL PROTECTED]> wrote:
> > > > > > > On Saturday 23 December 2006 01:32, Sander Sweers wrote:
> > > > > > > > -------- Original Message --------
> > > > > > > > Subject: [ivtv-users] [PATCH] Compatibility with
> > > > > > > > realtime kernels Date: Fri, 22 Dec 2006 20:52:28 +0100
> > > > > > > > From: Maarten Maathuis <[EMAIL PROTECTED]>
> > > > > > > > Reply-To: User discussion about IVTV
> > > > > > > > <[email protected]> To: User discussion about
> > > > > > > > IVTV <[email protected]>
> > > > > > > >
> > > > > > > > I would thoroughly check the patch.
> > > > > > > >
> > > > > > > > It's been test compiled against a ck (my previous
> > > > > > > > kernel, aka a "more normal" kernel) kernel and compiled
> > > > > > > > against a realtime kernel.
> > > > > > > >
> > > > > > > > It should compile against 0.9.1.
> > > > > > > >
> > > > > > > > Let me know if it's ok or not.
> > > > > > > >
> > > > > > > > Maarten.
> > > > > > >
> > > > > > > Maarten,
> > > > > > >
> > > > > > > Sorry for the delay, I completely missed this post at the
> > > > > > > time and I just accidentally came across it.
> > > > > > >
> > > > > > > My question is: can you make a patch for the ivtv trunk
> > > > > > > code? I consider the current ivtv-0.9 code as end-of-life
> > > > > > > and it is to be replaced by new code that's currently in
> > > > > > > the ivtv subversion repository. Since it is changed very
> > > > > > > substantially it is better if you make a new patch for
> > > > > > > it.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
