[pvrusb2] New driver snapshot: pvrusb2-mci-20060101

Frans Meulenbroeks fransmeulenbroeks at yahoo.com
Thu Jan 5 11:19:09 CST 2006


Mike,

I moved to the 20060103 snapshot today.
However that does not fix the interlace 1 and vert res
288 issue.
Also the v42l  do_ioctil errors are still there.
See the log below.
Note that until this point I have not done anything.
This is the log immediately after plugging in the
device.
When I then manually change interlace to 1 and the
vert res to 576  the device works as before. (it might
be that the image quality is a little bit less, but
this could als be my perception or based on channel or
programme).

Best regards, Frans.

pvrusb2 pvr2_stream_create: sp=c090b2a0
pvrusb2 pvr2_hdw_setup: video stream is c090b2a0
pvrusb2 pvr2_hdw_setup(hdw=c077b000) done, ok=1
init_ok=1
pvrusb2 Device initialization completed successfully.
pvrusb2 Registered pvrusb2 v4l device, minor=0
pvrusb2 pvr2_v4l2_do_ioctl failure, ret=-22
(0xffffffea)
pvrusb2 pvr2_v4l2_do_ioctl failure, ret=-515
(0xfffffdfd)
pvrusb2 pvr2_v4l2_do_ioctl failure, ret=-22
(0xffffffea)
pvrusb2 /*--TRACE_COMMIT--*/ "Horizontal capture
resolution" <-- 720 (<integer>)pvrusb2
/*--TRACE_COMMIT--*/ "Vertical capture resolution" <--
288 (<integer>)
pvrusb2 /*--TRACE_COMMIT--*/ "Interlace mode" <-- 1
(<integer>)
pvrusb2 pvr2_decoder_set_size(720x288)
pvrusb2 i2c v4l2 set_size(720x288)
pvrusb2 pvr2_v4l2_do_ioctl failure, ret=-22
(0xffffffea)


--- Mike Isely <isely at isely.net> wrote:

> 
> Frans:
> 
> There was a problem introduced in the 20051231
> snapshot involving capture 
> resolution that was fixed by the 20060102A snapshot.
>  The problem caused 
> the default resolution to not be initialized
> properly when the device 
> comes up in PAL B/G mode.  You can see this in your
> log because it had 
> initially selected 720x480 as the capture
> resolution.
> 
> However I do not understand what happened at the
> tail end of your log, 
> where something apparently later on set the capture
> resolution to 720x288 
> with interlace = 1.  Was that your attempt to clear
> the problem?  The 
> driver could not have done that on its own.
> 
> In any case, try the 20060103 snapshot and I think
> you'll be fine.
> 
>    -Mike
> 
> 
> -- 
>                          |         Mike Isely       
>   |     PGP fingerprint
>       Spammers Die!!     |                          
>   | 03 54 43 4D 75 E5 CC 92
>                          |   isely @ pobox (dot) com
>   | 71 16 01 E2 B5 F5 C1 E8
>                          |                          
>   |
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
>
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> 



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 



More information about the pvrusb2 mailing list