mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Michael Krufky <mkrufky@m1k.net>
Cc: Junichi Uekawa <dancer@netfort.gr.jp>,
	linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
	debian-amd64@lists.debian.org
Subject: Re: [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 Nov 2005)
Date: Fri, 11 Nov 2005 21:06:07 +0900	[thread overview]
Message-ID: <87y83vl780.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <43740F06.6030504@m1k.net>

Hi,

> >>>$ 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.

> 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.

df70b17f88a4d1d8545d3569a1f6d28c6004f9e4 2 Nov 2005 Nonfunctional bttv
d83c671fb7023f69a9582e622d01525054f23b66 1 Nov 2005 (fails to boot due to USB issues)
6e9d6b8ee4e0c37d3952256e6472c57490d6780d 27 Oct 2005 Functional bttv

 
> 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.


joined, but currently rebooting sporadically to test 
different kernels.


regards,
	junichi

  reply	other threads:[~2005-11-11 12:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  4:26 mencoder fails with Linux kernel from linus's git tree (2 " Junichi Uekawa
2005-11-10 21:40 ` [x86_64] 2.6.14-git13 mplayer fails with "v4l2: ioctl queue buffer failed: Bad address" (2 Nov 2005, 11 " Junichi Uekawa
2005-11-10 22:58   ` Mike Krufky
2005-11-11  0:05     ` Junichi Uekawa
2005-11-11  3:24       ` Michael Krufky
2005-11-11 12:06         ` Junichi Uekawa [this message]
2005-11-11 13:11           ` Michael Krufky
2005-11-11 13:29           ` Junichi Uekawa
2005-11-11 14:06             ` Hugh Dickins
2005-11-12 22:22               ` Nickolay V. Shmyrev
2005-11-13  2:54                 ` Matti Aarnio
2005-11-13  4:24                   ` Junichi Uekawa
2005-11-16 12:50                   ` Nickolay V. Shmyrev
2005-11-16 17:47                     ` Hugh Dickins
2005-12-01  0:09                       ` Junichi Uekawa
2005-11-17  0:07                 ` Junichi Uekawa
2005-11-11 14:21             ` Junichi Uekawa
2005-11-12 21:11               ` Ricardo Cerqueira
     [not found]   ` <87mzj4uoys.dancerj%dancer@netfort.gr.jp>
2005-12-19 23:10     ` [x86_64] linux 2.6.15-rc6 mplayer fails to record ALSA audio Junichi Uekawa
2006-01-14  7:33       ` Junichi Uekawa
2006-01-19 23:11         ` [x86_64] bttv: linux 2.6.16-rc1 mplayer fails to record ALSA audio and fails tune TV Junichi Uekawa
2006-02-02  9:13           ` Junichi Uekawa
2006-02-02 13:53             ` Manu Abraham
2006-02-02 23:04               ` Junichi Uekawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y83vl780.dancerj%dancer@netfort.gr.jp \
    --to=dancer@netfort.gr.jp \
    --cc=debian-amd64@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@m1k.net \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome