public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <udo@hypervisor.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: v4l-dvb-maintainer@linuxtv.org, linux-media@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] 2.6.30: missing audio device in bttv
Date: Thu, 11 Jun 2009 23:38:17 +0200	[thread overview]
Message-ID: <20090611233817.757933aa@laptop.hypervisor.org> (raw)
In-Reply-To: <200906112218.11016.hverkuil@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

On Thu, 11 Jun 2009 22:18:10 +0200 Hans Verkuil (HV) wrote:

HV> On Thursday 11 June 2009 22:14:02 Udo A. Steinberg wrote:
HV> > Hi all,
HV> > 
HV> > With Linux 2.6.30 the BTTV driver for my WinTV card claims
HV> > 
HV> > 	bttv0: audio absent, no audio device found!
HV> > 
HV> > and audio does not work. This worked up to and including 2.6.29. Is
HV> > this a known issue? Does anyone have a fix or a patch for me to try?
HV> 
HV> You've no doubt compiled the bttv driver into the kernel and not as a
HV> module.
HV> 
HV> I've just pushed a fix for this to my tree:
HV> http://www.linuxtv.org/hg/~hverkuil/v4l-dvb

Yes, I've compiled bttv into the kernel. I've (hopefully correctly) ported
the commit http://www.linuxtv.org/hg/~hverkuil/v4l-dvb/rev/820630b2b12f
to 2.6.30. Now I'm getting:

bttv: driver version 0.9.18 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv 0000:06:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
bttv0: Bt878 (rev 2) at 0000:06:00.0, irq: 21, latency: 32, mmio: 0x50001000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
IRQ 21/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs
bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-1/1-0018/ir0 [bt878 #0 [sw]]
i2c-adapter i2c-1: sendbytes: NAK bailout.
tveeprom 1-0050: Huh, no eeprom present (err=-5)?
tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom.
bttv0: Hauppauge eeprom indicates model#0
bttv0: tuner absent
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950

Cheers,

	- Udo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-06-11 21:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 20:14 2.6.30: missing audio device in bttv Udo A. Steinberg
2009-06-11 20:18 ` [v4l-dvb-maintainer] " Hans Verkuil
2009-06-11 20:22   ` Hans Verkuil
2009-06-11 22:20     ` Mauro Carvalho Chehab
2009-06-11 22:26       ` Hans Verkuil
2009-06-11 23:07         ` Mauro Carvalho Chehab
2009-06-11 23:18           ` Hans Verkuil
2009-06-12  8:04             ` Jean Delvare
2009-06-11 21:38   ` Udo A. Steinberg [this message]
2009-06-11 21:46     ` Hans Verkuil
2009-06-11 22:35       ` Udo A. Steinberg
2009-06-11 23:01         ` Hans Verkuil
2009-06-12  0:00           ` Udo A. Steinberg

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=20090611233817.757933aa@laptop.hypervisor.org \
    --to=udo@hypervisor.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    /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