well, we still haven't gotten a real good answer as to
why yuv decoding doesn't tell us where to send the
data.

that's all that's really buggin' me

-tmk

--- Axel Thimm <[EMAIL PROTECTED]> wrote:

> I suggest to collect questions on current ivtv
> issues that Hauppauge
> engineering and development can help solving.
> Hauppauge is open to the
> Linux community, nevertheless the process to acquire
> and clear out
> information is slow. It pays off to do so for a set
> of questions IMHO,
> at least that was the experience with the former Q&A
> (not QA ;)
> sessions.
> 
> Can you formulate your questions appropriately
> (assume full knowledge
> on any hardware detail, but little on ivtv and Linux
> kernel drivers)?
> You can send them as reply to this post or off-list
> and I will create
> a summary.
> 
> Thanks!
> 
> On Wed, Jan 05, 2005 at 10:03:17PM -0000, John
> Harvey wrote:
> > Axel
> >     The question I have I think was asked by Hans but
> I never saw an
> > answer. I have been trying to get UYV playback to
> work. If you initiate a
> > YUV dma request and then query the status it says
> that it need 622080 bytes
> > (for PAL) which is correct but it says that the
> address to transfer to is 0
> > and that the dma type is 0(mpeg).  
> >     If it transfer a small amount say 4 bytes then
> query the status on
> > the interrupt for dma completing it says it need
> 622076 bytes to an address
> > 0f 4 and type 0. 
> > 
> >     I don't believe we should be transferring to
> address 0 so we
> > presumably need to add some offset to this (just
> like the osd has to add the
> > osd base address) but there doesn't appear to be
> an api to find the offset. 
> > 
> > Can Hauppauge help us to understand how to use the
> YUV dma transfer?
> > 
> > Alternatively there are 9 yuv buffers pointed to
> from the 9 words at
> > 0x0100140. If I modify the driver to continue to
> display the last frame it
> > is displaying the yuv from one of these buffers
> and if I write yuv (in
> > Hauppauge style yuv) to the correct buffer it is
> displayed on the output.
> > However I cant determine which of the 9 buffers is
> the correct one to write
> > to or to control which one to use. If we cant make
> the api work then
> > possibly we might be able to find a way to control
> which of these buffers is
> > used and then we could control this ourselves.
> > 
> > Do you think Hauppauge will be able to help us
> with this? 
> > 
> > Thanks
> > 
> > John
> > 
> > > From: [EMAIL PROTECTED]
> [mailto:ivtv-devel-
> > > [EMAIL PROTECTED] On Behalf Of Axel
> Thimm
> > > Sent: 28 August 2004 22:39
> > > To: [email protected]
> > > Subject: [ivtv-devel] Re: Hauppauge specific
> questions (was: Hauppauge's
> > > commitment to Linux support)
> > > 
> > > Hans Verkuil wrote:
> > > > Axel Thimm wrote:
> > > > > If you need information from Hauppauge or
> one of its suppliers,
> > > > > e.g. for the ivtv project, Conexant, there
> are two cases:
> > > > >
> > > > > o if the information is under Hauppauge's
> authority, it can and will
> > > > >   be disclosed.
> > > > > o if the information is under Conexant's
> authority, Hauppauge will try
> > > > >   to mediate, so you don't get stuck with a
> sales person at Conexant
> > > > >   again.
> > > 
> > > > OK, here is the first set of questions. These
> questions are all
> > > Hauppauge
> > > > specific (except perhaps for the last
> question). I'll post a separate
> > > list
> > > > with Conexant questions. The autodetect
> questions have the highest
> > > priority.
> > > 
> > > Here are the answers to Hans' questions, the
> refined questions based
> > > on these answers, the refined answers based on
> these refined
> > > questions and so on ;)
> > > 
> > > Some of the tuner documentation has already been
> used in current ivtv
> > > snapshots, hopefully more will follow.
> > > 
> > > Thanks for your patience!
> > 
> > 
> > 
> > The SF.Net email is sponsored by: Beat the
> post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt
> from ThinkGeek.
> > It's fun and FREE -- well,
> almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> >
>
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 
> -- 
> Axel.Thimm at ATrpms.net
> 

> ATTACHMENT part 2 application/pgp-signature 




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to