Re: [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue bufferfailed: Bad address" (2 Nov 2005, 11 Nov 2005)

[Michael Krufky]

Junichi Uekawa wrote:

> Hi,
>
> > > I've tried running mplayer v4l2 input on a bt878 card, and it fails.
> > > xawtv works fine, and 2.6.14-rc5 used to work fine.
> > >
> > > On git 3b44f137b9a846c5452d9e6e1271b79b1dbcc942 :
> > >
> > > $ mplayer  tv://1 -tv driver=v4l2
> > > MPlayer dev-CVS--4.0.2 (C) 2000-2005 MPlayer Team
> > > CPU: Advanced Micro Devices Athlon 64 Newcastle,Winchester,San Diego,Venice; Sempron Palermo (Family: 15, Stepping: 0)
> > > Detected cache-line size is 64 bytes
> > > CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
> > > Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2
> > bttv currently only supports v4l1.  We are still in the process of 
> > porting the bttv driver from v4l1 to v4l2. Nickolay is working on it.
> Thanks for the info. It's strange since this is a regression
> (pre 2.6.14 used to work. New code made it fail).
> Do you mean there was a change that broke v4l2 support in bttv ?
> Ever since Linux Kernel 2.6.3, I used v4l2 for recording (more
> than one and a half years...)
>  
v4l2 support could not have been broken, since it was never present.  
You were going through a compat layer.... Maybe that's where the 
regression is.

Anyhow, I will discuss this with the other v4l guys... One of us will 
get back to you, maybe ask you to test a patch or two.

One question -- At exactly what point does this break for you?  The git 
commit key above was from today, but at what point did this LAST work 
for you?  It would be really helpful if you can do a git bisection test, 
so that we can isolate the trouble patch if in fact it is a regression.

You might also like to join us in #v4l on irc.freenode.net ... Sometimes 
it's much quicker to troubleshoot this stuff over irc instead of email.

-Michael Krufky
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/