On Monday 02 January 2006 20:42, [EMAIL PROTECTED] wrote:
> Quick answer:
>
> [EMAIL PROTECTED]:/usr/src/ivtv-0.4.2/driver$ gcc -v
> Using built-in specs.
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
> --with-gxx-include-dir=/usr/include/c++/4.0.2 --enable-shared
> --with-system-zlib --libexecdir=/usr/lib --enable-nls
> --without-included-gettext --enable-threads=posix
> --program-suffix=-4.0 --enable-__cxa_atexit
> --enable-libstdcxx-allocator=mt --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-java-gc=boehm
> --enable-java-awt=gtk-default --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre
> --enable-mpfr --disable-werror --enable-checking=release
> x86_64-linux-gnu
> Thread model: posix
> gcc version 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
>
> Should I be using 3.4?
No, that's what I've been using. But it may be related to this problem.
I have a hunch, but it depends on the results of the tests of my
previous post. Please let me know asap.
Hans
>
> Cheers,
> Michael
>
> Quoting Hans Verkuil <[EMAIL PROTECTED]>:
> > Quick question,
> >
> > What gcc version are use using to compile the driver?
> >
> > Hans
> >
> > On Monday 02 January 2006 20:17, [EMAIL PROTECTED] wrote:
> > > Hans,
> > >
> > > I wasn't able to apply the patch ( I'm a newbie w/ linux ) so I
> > > just modified the source with the information contained in your
> > > file.
> > >
> > > no hotplug gives:
> > >
> > > [ 1348.171567] ivtv0: loaded /lib/modules/v4l-cx2341x-enc.fw
> > > firmware (262144 bytes) [ 1348.423225] ivtv0: firmware sum =
> > > 0084a9cb
> > >
> > >
> > > hotplug gives:
> > >
> > > [ 1865.847204] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144
> > > bytes, sum = 0084a9cb)
> > > [ 1866.098870] ivtv0: firmware sum = 00206879
> > >
> > > This is very interesting, it loads the firmware in load_fw_direct
> > > and then has the incorrect firmware in ivtv_enc_firmware_copy.
> > > The memcpy was successful, it did not return NULL(I checked).
> > >
> > > Could something else be overwriting this variable? Another thread
> > > perhaps?
> > >
> > > I'm willing to continue debugging but need a little help.
> > >
> > > Thanks,
> > >
> > > Michael
> > >
> > > Quoting Hans Verkuil <[EMAIL PROTECTED]>:
> > > > Michael,
> > > >
> > > > I've attached a patch for ivtv-firmware.c. I'm curious what the
> > > > results will be. To be continued tomorrow...
> > > >
> > > > Hans
> > > >
> > > > On Monday 02 January 2006 01:15, [EMAIL PROTECTED] wrote:
> > > > > Hans,
> > > > >
> > > > > Your guess was bang on - reverting to the "old way" of
> > > > > loading the firmware results in success. Something in the
> > > > > hotplug is causing grief.
> > > > >
> > > > > If you can give me a hand with the C, I can attempt the
> > > > > summations that you have requested. It would be nice to get
> > > > > to the bottom of this one.. I'm probably not the only one
> > > > > that has run into this problem.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Michael
> > > > >
> > > > > Quoting Hans Verkuil <[EMAIL PROTECTED]>:
> > > > > > On Monday 02 January 2006 00:27, [EMAIL PROTECTED] wrote:
> > > > > > > Hans,
> > > > > > >
> > > > > > > I've performed the operations as requested, and achieve
> > > > > > > the same result - I assume this removes zero padding on
> > > > > > > the firmware file?
> > > > > >
> > > > > > correct
> > > > > >
> > > > > > > [ 307.521854] ivtv0: loaded v4l-cx2341x-enc.fw firmware
> > > > > > > (262144 bytes) [ 307.753271] ivtv0 warning: Encoder
> > > > > > > mailbox not found [ 307.784732] ivtv0 warning: Decoder
> > > > > > > mailbox not found [ 307.784735] ivtv0: Error locating
> > > > > > > firmware. [ 307.791075] ivtv0: Error -12 on
> > > > > > > initialization [ 307.791084] ivtv: probe of 0000:02:06.0
> > > > > > > failed with error -12 [ 307.791090] ivtv:
> > > > > > > ==================== END INIT IVTV ====================
> > > > > > >
> > > > > > > To be certain that the firmware was correct, I reloaded
> > > > > > > 0.4.0 using the shortened firmware file and was able to
> > > > > > > watch tv once again.
> > > > > > >
> > > > > > > I believe we have ruled out the firmware.. could there be
> > > > > > > something in ivtv 0.4.1/2 that is causing the grief? Is
> > > > > > > there some means of enabling more verbose debug messages?
> > > > > > > I don't mind recompiling...
> > > > > >
> > > > > > Well, ivtv-0.4.1 switched to the hotplug mechanism. My
> > > > > > guess the problem is with that.
> > > > > >
> > > > > > Edit ivtv-firmware.c, look for CONFIG_FW_LOADER and replace
> > > > > > that #if with #if 0. Do the same in ivtv-driver.h and
> > > > > > cx25840.h.
> > > > > >
> > > > > > Recompile, install and test. If it now works again, then it
> > > > > > is the new hotplug stuff that breaks things. But why don't
> > > > > > I get the same problems? Weird.
> > > > > >
> > > > > > If it is hotplug related and if you are handy with C, then
> > > > > > can you perhaps do some tests? I was thinking of hacking
> > > > > > ivtv-firmware.c so that the firmware load routines so a
> > > > > > simple sum of all the bytes in the firmware and then show
> > > > > > the grand total when done. I'd be very interested to see if
> > > > > > there are any difference between the hotplug and
> > > > > > non-hotplug cases.
> > >
> > > _______________________________________________
> > > ivtv-users mailing list
> > > [email protected]
> > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
