From: Jan Dittmer <j.dittmer@portrix.net>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with bttv in latest bk
Date: Thu, 20 Mar 2003 17:34:39 +0100 [thread overview]
Message-ID: <3E79ED9F.1000402@portrix.net> (raw)
In-Reply-To: <87znnqmitn.fsf@bytesex.org>
>>
>>------------[ cut here ]------------
>>kernel BUG at drivers/media/video/bttv-risc.c:742!
>
>
> Not reproducable here with latest bttv bits. Sure you have the latest
> module loaded? bttv prints the version number at insmod time, should be
> 0.9.6 (vanilla 2.5.65 has 0.9.4 I think) ...
>
> Gerd
>
bttv: driver version 0.9.7 loaded
Would it make sense to try as module? Currently it is compiled in.
Jan
Linux video capture interface: v1.00
bttv: driver version 0.9.7 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Host bridge is VIA Technologies, In VT8363/8365 [KT133/K
bttv: Host bridge is VIA Technologies, In VT82C686 [Apollo Sup
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at 00:0e.0, irq: 5, latency: 32, mmio: 0xeb120000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: BT878(Hauppauge (bt878)) [card=10,autodetected]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=61324, tuner=Philips FI1216 MK2 (5), radio=no
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
msp34xx: init: chip=MSP3410D-B4 +nicam +simple
msp3410: daemon started
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54
(PV951),ta8874z
tuner: probing bt848 #0 i2c adapter [id=0x10005]
tuner: chip found @ 0xc2
tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
tda9887: probing bt848 #0 i2c adapter [id=0x10005]
next prev parent reply other threads:[~2003-03-20 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 18:48 Oops with bttv in latest bk Jan Dittmer
2003-03-19 22:44 ` Gerd Knorr
2003-03-20 6:52 ` Jan Dittmer
2003-03-20 10:30 ` Gerd Knorr
2003-03-20 16:34 ` Jan Dittmer [this message]
2003-03-20 19:42 ` Gerd Knorr
2003-03-21 11:53 ` Jan Dittmer
2003-03-21 14:57 ` Gerd Knorr
2003-03-21 16:21 ` Jan Dittmer
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=3E79ED9F.1000402@portrix.net \
--to=j.dittmer@portrix.net \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.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