On Wednesday 22 February 2006 10:22, Jarod Wilson wrote:
> On Sunday 19 February 2006 15:03, Hans Verkuil wrote:
> > On Saturday 18 February 2006 06:01, Jarod Wilson wrote:
> > > > > And could anyone test current SVN by MPG600GR(NTSC) version
> > > > > of wo/GR,YCS or wo/GR ?
> > > >
> > > > I've been meaning to dig out the MPG600GR I've got that's
> > > > sans-GR/YCS and try it out since the merge, just haven't had
> > > > time. Lemme see if I can't get to it this weekend...
> > >
> > > A little tardy getting around to it, but I finally tried out my
> > > MPG600GR today, with current svn trunk ivtv and v4l-dvb. The
> > > drivers mostly load okay, though I get a few i2c hardware not
> > > found messages, which I'm guessing are the missing GR and YCS
> > > chips, and I get no video off the tuner (just a black screen),
> > > while ~1 year ago, I was able to at least get black and white
> > > video off the tuner (paken 0.2.x-based ivtv, iirc). While trying
> > > to find any working video right now, a bunch of these get logged:
> > >
> > > ivtv0: i2c hardware 0x00005000 not found for command 0xc008561c!
> >
> > That's a bug. I've just fixed this. Can you try again?
>
> Bah, I've since upgraded that box from FC4 to pre-FC5 (and thus
> pre-4.1 GCC), and now I have new problems:
It looks like the pre-FC5 already contains some i2c patches from 2.6.16,
even though it is a 2.6.15 kernel. It should be quite easy to change
the test in the i2c drivers to check for 2.6.15 instead of 2.6.16. Then
it should compile again.
I don't know about the kernel oops. I suspect that there may be other
i2c changes for which ivtv hasn't been updated yet. I haven't
investigated that yet.
Hans
>
> 1) the i2c-drivers fail to build:
>
> make -C /lib/modules/2.6.15-1.1955_FC5/build M=/root/ivtv/i2c-drivers
> modules make[1]: Entering directory
> `/usr/src/kernels/2.6.15-1.1955_FC5-i686' CC [M]
> /root/ivtv/i2c-drivers/upd64031a.o
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘upd64031a_write’:
> /root/ivtv/i2c-drivers/upd64031a.c:144: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c:148: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘write_all_regs’:
> /root/ivtv/i2c-drivers/upd64031a.c:157: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘chg_channel’:
> /root/ivtv/i2c-drivers/upd64031a.c:174: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘chg_input’:
> /root/ivtv/i2c-drivers/upd64031a.c:210: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘upd64031a_set_norm’:
> /root/ivtv/i2c-drivers/upd64031a.c:237: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘upd64031a_command’:
> /root/ivtv/i2c-drivers/upd64031a.c:341: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c:350: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c:374: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: In function ‘upd64031a_attach’:
> /root/ivtv/i2c-drivers/upd64031a.c:446: error: ‘I2C_CLIENT_ALLOW_USE’
> undeclared (first use in this function)
> /root/ivtv/i2c-drivers/upd64031a.c:446: error: (Each undeclared
> identifier is reported only once
> /root/ivtv/i2c-drivers/upd64031a.c:446: error: for each function it
> appears in.)
> /root/ivtv/i2c-drivers/upd64031a.c:450: error: ‘struct i2c_driver’
> has no member named ‘name’
> /root/ivtv/i2c-drivers/upd64031a.c: At top level:
> /root/ivtv/i2c-drivers/upd64031a.c:509: error: unknown field ‘name’
> specified in initializer
> /root/ivtv/i2c-drivers/upd64031a.c:509: warning: initialization makes
> integer from pointer without a cast
> /root/ivtv/i2c-drivers/upd64031a.c:510: error: unknown field ‘flags’
> specified in initializer
> /root/ivtv/i2c-drivers/upd64031a.c:510: error: ‘I2C_DF_NOTIFY’
> undeclared here (not in a function)
> /root/ivtv/i2c-drivers/upd64031a.c:519: error: unknown field ‘owner’
> specified in initializer
> /root/ivtv/i2c-drivers/upd64031a.c:519: warning: missing braces
> around initializer
> /root/ivtv/i2c-drivers/upd64031a.c:519: warning: (near initialization
> for ‘i2c_driver.driver’)
> /root/ivtv/i2c-drivers/upd64031a.c:519: warning: initialization from
> incompatible pointer type
> make[2]: *** [/root/ivtv/i2c-drivers/upd64031a.o] Error 1
> make[1]: *** [_module_/root/ivtv/i2c-drivers] Error 2
> make[1]: Leaving directory `/usr/src/kernels/2.6.15-1.1955_FC5-i686'
> make: *** [all] Error 2
>
>
> 2) rmmod'ing ivtv (after it failed to load the necessary i2c drivers,
> since I forgot to build them) resulted in a segfault, though that may
> be pre-FC5's fault, not ivtv's...
>
> Unable to handle kernel paging request at virtual address 444442b7
> printing eip:
> f9527582
> *pde = 00000000
> Oops: 0000 [#1]
> last sysfs file: /class/firmware/0000:00:0e.0/loading
> Modules linked in: tda9887 tuner v4l2_common ivtv(U) v4l1_compat
> tveeprom videodev ipv6 autofs4 nfs lockd nfs_acl rfcomm l2cap
> bluetooth sunrpc ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp
> iptable_filter ip_tables x_tables dm_mirror dm_mod video button
> battery ac lp parport_pc parport floppy nvram ehci_hcd ohci1394
> ieee1394 uhci_hcd ns83820 nvidia(U) snd_cmipci gameport snd_seq_dummy
> snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss
> via_ircc snd_pcm irda crc_ccitt i2c_viapro i2c_core snd_page_alloc
> snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi
> snd_seq_device snd soundcore ext3 jbd
> CPU: 0
> EIP: 0060:[<f9527582>] Tainted: P VLI
> EFLAGS: 00210203 (2.6.15-1.1955_FC5 #1)
> EIP is at ivtv_stop_all_captures+0x24/0x45 [ivtv]
> eax: 444442ab ebx: 6b6b6b6a ecx: 00000000 edx: f9520d6e
> esi: d8d8d740 edi: f0120000 ebp: edbb7000 esp: edbb7efc
> ds: 007b es: 007b ss: 0068
> Process rmmod (pid: 6385, threadinfo=edbb7000 task=f75d3000)
> Stack: <0>f0120000 c1945540 f9546b0c f9520ddb c19454f8 c01ccec3
> c19455e8 c02273fc
> c1945540 f7fdf88c f9546b0c c02276c5 f9546b0c 00000000 c0350460
> c0226c5c f9546b0c f9546ae0 bfcaa620 c02277d0 f9547680 c01cd015
> f9547680 00000000 Call Trace:
> [<f9520ddb>] ivtv_remove+0x6d/0x3b9 [ivtv] [<c01ccec3>]
> pci_device_remove+0x16/0x28
> [<c02273fc>] __device_release_driver+0x5c/0x74 [<c02276c5>]
> driver_detach+0x8e/0xbc
> [<c0226c5c>] bus_remove_driver+0x57/0x75 [<c02277d0>]
> driver_unregister+0x8/0x13
> [<c01cd015>] pci_unregister_driver+0xd/0x73 [<c01315f8>]
> sys_delete_module+0x191/0x1ce
> [<c0105568>] do_syscall_trace+0x104/0x14a [<c0102bc1>]
> syscall_call+0x7/0xb
> Code: 5a 59 5b 5e 5f 5d c3 57 56 53 89 c7 8b 80 84 1f 00 00 8d 58 ff
> 69 c0 20 01 00 00 8d b0 e0 fe ff ff eb 1f 89 f0 03 87 88 1f 00 00
> <8b> 40 0c a8 40 74 09 89 da 89 f8 e8 ef ee ff ff 4b 81 ee 20 01
> Continuing in 1 seconds.
> Segmentation fault
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
