Duncan Webb wrote:
Hi all
Busy setting up a freevo system on a AMD64 system and have notices a
few problems in freevo 1.5.4 in src/tv/v4l2.py.
The attached patch when applied to the ivtv-0.4.0 driver prints the
record sizes of ioctl calls to the ivtv driver and the small
application v4l-test does the same.
The problem seems to be that struct.pack with a L is packing 8 bytes
on an amd64 system and 4 bytes on a i386 system, all this means is
that the structure sizes are incorrect when passed to the driver. I've
not tracked them all down yet but here are some changes that will
allow mplayer to play from the tv card.
QUERYCAP_ST = "16s32s32sLL16x"
QUERYCAP_ST = "16s32s32sII16x" #NEW
QUERYCAP_NO = _IOR('V', 0, QUERYCAP_ST)
INPUT_ST = "L"
INPUT_ST = "I"; #NEW
GETINPUT_NO = _IOR('V', 38, INPUT_ST)
SETINPUT_NO = _IOWR('V', 39, INPUT_ST)
FMT_ST = "L7L4x168x"
FMT_ST = "L7I4x168x" #NEW
GET_FMT_NO = _IOWR ('V', 4, FMT_ST)
SET_FMT_NO = _IOWR ('V', 5, FMT_ST)
I've not tested these changes on an i386 system, but I would guess
that an int is 4 bytes.
Okay now had time to test these changes on my P3 system and these
changes seems to work.
Is there a test program somewhere if freevo to test the v4l2.py
interface? If there is then I would like to run the tests and see what
needs to be changed and then send in a patch.
Regards,
Duncan
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
