Sorry, I missed this when it was posted. The osprey 230 should be treated the same as an Osprey 220 from bttv's perspective. For this to happen a one line code addition must be made in bttv-cards.c to add the eeprom identifier into the card type switch. Search for "btv->type = BTTV_OSPREY2x0;" and add "case 0x00A0:" to it's cases. This should at least make the card function as expected. The other alternative is to use the drivers available through Osprey's ftp site (ftp.ospreyvideo.com) which are based off of the 0.7.97 codebase. For btaudio support, I am not certain what would be required for the 230. The drivers on our ftp site are based (originally) on the btaudio-0.7 code, but there have been extensive changes to support our audio subsystems. If you can repeat the oops using the drivers available from our ftp site I would be happy to try and help resolve this problem. I'm not really certain if the wrong card identification could cause the divide by zero that you are seeing, but it's not completely impossible. -Scott Tillman Viewcast, Osprey Division > -----Original Message----- > From: video4linux-list-admin@xxxxxxxxxx > [mailto:video4linux-list-admin@xxxxxxxxxx]On Behalf Of Jure Pecar > Sent: Tuesday, August 05, 2003 9:35 AM > To: video4linux-list@xxxxxxxxxx > Subject: oops with osprey 230 > > > > Hi there, > > I have an repeatable oops, triggered by producer -pd (real producer, print > devices): > > Linux video capture interface: v1.00 > i2c-core.o: i2c core module > i2c-algo-bit.o: i2c bit algorithm module > bttv: driver version 0.7.104 loaded > bttv: using 4 buffers with 2080k (8320k total) for capture > bttv: Host bridge is PCI device 8086:254c (Intel Corp.) > bttv: Bt8xx card found (0). > bttv0: Bt878 (rev 17) at 04:04.0, irq: 9, latency: 64, mmio: 0xfbfe0000 > bttv0: detected: Osprey-200 [card=88], PCI subsystem ID is 0070:ff01 > bttv0: using: BT878(Osprey 200/250) [card=88,autodetected] > i2c-core.o: adapter bt848 #0 registered as adapter 0. > bttv0: osprey eeprom: card=88 name=Osprey 200/250 serial=32410068 > bttv0: using tuner=-1 > bttv0: PLL: 28636363 => 35468950 .. ok > bttv0: registered device video0 > bttv0: registered device vbi0 > btaudio: driver version 0.7 loaded [digital+analog] > btaudio: Bt878 (rev 17) at 04:04.1, irq: 9, latency: 64, mmio: 0xfbff0000 > btaudio: using card config "Osprey 200" > btaudio: registered device dsp0 [digital] > btaudio: registered device dsp1 [analog] > btaudio: registered device mixer0 > divide error: 0000 > btaudio bttv i2c-algo-bit soundcore i2c-core videodev lp parport autofs > e1000 keybdev mousedev hid input usb-uhci usbcore ext3 jbd aic79xx sd_mod > scsi_mod > CPU: 0 > EIP: 0060:[<f89c8062>] Not tainted > EFLAGS: 00010246 > > EIP is at btaudio_dsp_ioctl [btaudio] 0x112 (2.4.20-19.9) > eax: 001b5800 ebx: fffffff2 ecx: 00000000 edx: 00000000 > esi: f71e4180 edi: 00000000 ebp: 00000027 esp: f6cf1f4c > ds: 0068 es: 0068 ss: 0068 > Process producer (pid: 2449, stackpage=f6cf1000) > Stack: c2c94280 ffffffe9 c0146623 c2c94280 f6cd9d00 00000000 f7063000 > bfffe800 > bfffe668 c014654d c2cf4b80 c46c3340 00000000 f6cf1f84 ffffffe7 > 80045002 > f6cd9d00 00000027 c0156ea9 c2c94280 f6cd9d00 80045002 bfffe6b4 > c014691a > Call Trace: [<c0146623>] dentry_open [kernel] 0xd3 (0xf6cf1f54)) > [<c014654d>] filp_open [kernel] 0x6d (0xf6cf1f70)) > [<c0156ea9>] sys_ioctl [kernel] 0xc9 (0xf6cf1f94)) > [<c014691a>] sys_open [kernel] 0x8a (0xf6cf1fa8)) > [<c010953f>] system_call [kernel] 0x33 (0xf6cf1fc0)) > > > Code: f7 be 88 00 00 00 31 db 8b 54 24 58 d3 f8 89 02 89 d9 e9 3c > > That divide error looks especially interesting. > > Btw, what had redhat 9 done with ksymoops? Where is it hiding? > > -- > > Jure Pecar > > > -- > video4linux-list mailing list > Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/video4linux-list
