On Wednesday 09 August 2006 13:34, Steven Ellis wrote:
> Hans Verkuil wrote:
> > Hi Steven,
> >
> > Is it possible to talk this over in the ivtv-dev channel of
> > irc://irc.freenode.net/ivtv-dev? It is probably easier to discuss
> > this on that IRC channel, at least initially.
> >
> > I can be on that channel between 8 pm and midnight tonight or
> > tomorrow, my timezone is GMT+2.
>
> Ok i'll add in the channel for my IRC client. I'm GMT + 12 (Auckland
> NZ) but I'm on conference calls the next couple of mornings for my
> "other" job so i'll probably miss you. I'll aim for Thursday night
> (you) Friday morning (me) but I can't be sure at the moment.
>
> > Let me know if and when you can be on IRC. If it's not possible,
> > then we continue by email.
>
> Just a quick pointer at the best code base for a DMA level comparison
> would be useful.
Well, that's interesting. I thought that this change was made in
ivtv-0.3.x, but the same code has been in there from the beginning and
was already in ivtv-0.2.x.
In your earlier mail you said that it was working for ivtv-0.3. I
suggest that you take a known working ivtv-0.3 version and see if you
can figure out what the differences are regarding DMA handling and DMA
error recovery.
I'm also interested in knowing what the latest working ivtv-0.3 version
is.
What would be a nice test is if you can get a ivtv-0.3 working and add
some debug code to ivtv-irq.c that shows a message in the kernel log
when a DMA error occurs. If you actually see that DMA errors occur
without any MPEG stream corruption, then I consider that a very strong
hint that a bug was introduced in the driver at some point.
It is by the way also possible that this problem might be related to
encoder firmware versions. Do you know with which firmware version
those ivtv-0.3 tests were done? Perhaps the newer fw we are using
actually has a bug that causes this problem. That's also an interesting
approach to keep in mind.
Interesting.
So my recommended approach would be to recreate a working setup with a
ivtv-0.3.x version. Then we can compare that version with the current
implementation.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
