Hi,
I downloaded "bttv-0.9.11" driver to upgrade the current
"bttv-0.7.96" in my system.
When I run make the following error occurs. How to rectify this
and compile the same
successfully ? The same is the case with bttv-0.9.5. I am working
in Red Hat Linux
9.0, kernel-2.4.20-8, bttv based "Pixelview Play Tv Pro" Tv tuner
card (bt878)
environment.
In file included from video-buf.c:36:
video-buf.h:137: field `field' has incomplete type
video-buf.h:159: warning: parameter has incomplete type
video-buf.h:169: field `type' has incomplete type
video-buf.h:171: field `field' has incomplete type
video-buf.h:172: field `last' has incomplete type
video-buf.h:195: warning: parameter has incomplete type
video-buf.h:195: warning: parameter has incomplete type
video-buf.h:201: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.h:201: warning: its scope is only this definition or
declaration, whic
h is probably not what you want
video-buf.h:201: warning: parameter has incomplete type
video-buf.h:203: warning: `struct v4l2_requestbuffers' declared
inside parameter
list
video-buf.h:204: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.h:206: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.h:208: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.c:351: parameter `type' has incomplete type
video-buf.c:351: parameter `field' has incomplete type
video-buf.c:432: return type is an incomplete type
video-buf.c:432: conflicting types for `videobuf_next_field'
video-buf.h:199: previous declaration of `videobuf_next_field'
video-buf.c: In function `videobuf_next_field':
video-buf.c:433: variable `field' has initializer but incomplete
type
video-buf.c:433: storage size of `field' isn't known
video-buf.c:435: `V4L2_FIELD_ANY' undeclared (first use in this
function)
video-buf.c:435: (Each undeclared identifier is reported only
once
video-buf.c:435: for each function it appears in.)
video-buf.c:437: `V4L2_FIELD_ALTERNATE' undeclared (first use in
this function)
video-buf.c:438: `V4L2_FIELD_TOP' undeclared (first use in this
function)
video-buf.c:439: `V4L2_FIELD_BOTTOM' undeclared (first use in this
function)
video-buf.c:446: warning: `return' with a value, in function
returning void
video-buf.c:433: warning: unused variable `field'
video-buf.c: At top level:
video-buf.c:451: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.c:452: parameter `type' has incomplete type
video-buf.c:452: conflicting types for `videobuf_status'
video-buf.h:201: previous declaration of `videobuf_status'
video-buf.c: In function `videobuf_status':
video-buf.c:453: dereferencing pointer to incomplete type
video-buf.c:454: dereferencing pointer to incomplete type
video-buf.c:455: dereferencing pointer to incomplete type
video-buf.c:456: dereferencing pointer to incomplete type
video-buf.c:457: dereferencing pointer to incomplete type
video-buf.c:459: dereferencing pointer to incomplete type
video-buf.c:459: `V4L2_BUF_FLAG_MAPPED' undeclared (first use in
this function)
video-buf.c:464: dereferencing pointer to incomplete type
video-buf.c:464: `V4L2_BUF_FLAG_QUEUED' undeclared (first use in
this function)
video-buf.c:468: dereferencing pointer to incomplete type
video-buf.c:468: `V4L2_BUF_FLAG_DONE' undeclared (first use in
this function)
video-buf.c:475: dereferencing pointer to incomplete type
video-buf.c:476: dereferencing pointer to incomplete type
video-buf.c:477: dereferencing pointer to incomplete type
video-buf.c:478: dereferencing pointer to incomplete type
video-buf.c: At top level:
video-buf.c:483: warning: `struct v4l2_requestbuffers' declared
inside parameter
list
video-buf.c:484: conflicting types for `videobuf_reqbufs'
video-buf.h:203: previous declaration of `videobuf_reqbufs'
video-buf.c: In function `videobuf_reqbufs':
video-buf.c:488: dereferencing pointer to incomplete type
video-buf.c:490: dereferencing pointer to incomplete type
video-buf.c:494: dereferencing pointer to incomplete type
video-buf.c:506: dereferencing pointer to incomplete type
video-buf.c:507: dereferencing pointer to incomplete type
video-buf.c: At top level:
video-buf.c:515: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.c:516: conflicting types for `videobuf_querybuf'
video-buf.h:204: previous declaration of `videobuf_querybuf'
video-buf.c: In function `videobuf_querybuf':
video-buf.c:517: dereferencing pointer to incomplete type
video-buf.c:519: dereferencing pointer to incomplete type
video-buf.c:519: dereferencing pointer to incomplete type
video-buf.c:521: dereferencing pointer to incomplete type
video-buf.c:523: dereferencing pointer to incomplete type
video-buf.c:523: warning: passing arg 1 of `videobuf_status' from
incompatible p
ointer type
video-buf.c: At top level:
video-buf.c:529: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.c:530: conflicting types for `videobuf_qbuf'
video-buf.h:206: previous declaration of `videobuf_qbuf'
video-buf.c: In function `videobuf_qbuf':
video-buf.c:532: storage size of `field' isn't known
video-buf.c:541: dereferencing pointer to incomplete type
video-buf.c:543: dereferencing pointer to incomplete type
video-buf.c:543: dereferencing pointer to incomplete type
video-buf.c:545: dereferencing pointer to incomplete type
video-buf.c:555: type of formal parameter 3 is incomplete
video-buf.c:532: warning: unused variable `field'
video-buf.c: At top level:
video-buf.c:574: warning: `struct v4l2_buffer' declared inside
parameter list
video-buf.c:575: conflicting types for `videobuf_dqbuf'
video-buf.h:208: previous declaration of `videobuf_dqbuf'
video-buf.c: In function `videobuf_dqbuf':
video-buf.c:584: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:605: dereferencing pointer to incomplete type
video-buf.c:606: warning: passing arg 1 of `videobuf_status' from
incompatible p
ointer type
video-buf.c: In function `videobuf_read_zerocopy':
video-buf.c:661: storage size of `field' isn't known
video-buf.c:674: type of formal parameter 3 is incomplete
video-buf.c:661: warning: unused variable `field'
video-buf.c: In function `videobuf_read_one':
video-buf.c:702: storage size of `field' isn't known
video-buf.c:728: type of formal parameter 3 is incomplete
video-buf.c:702: warning: unused variable `field'
video-buf.c: In function `videobuf_read_start':
video-buf.c:776: storage size of `field' isn't known
video-buf.c:793: type of formal parameter 3 is incomplete
video-buf.c:776: warning: unused variable `field'
make[2]: *** [video-buf.o] Error 1
make[2]: Leaving directory
`/root/PT06/Refrences/bttv/bttv-0.9.11'
make[1]: *** [_mod_/root/PT06/Refrences/bttv/bttv-0.9.11] Error
2
make[1]: Leaving directory `/usr/src/linux-2.4.20-8'
make: *** [default] Error 2
With Regards,
S.Suriya Mohan.
On Wed, 30 Jul 2003 Lucas Correia Villa Real wrote :
Hi,
I guess this can be done using the Video4Linux2 BTTV driver,
since it allows
opening the same device twice.
Give a look at http://bytesex.org/bttv/ for patches and
instructions on
configuration.
Kind regards,
Lucas
On Wednesday 30 July 2003 01:30, suriya mohan wrote:
> Hi champ,
> In u'r mail to "video4linux-list" subjected "Multi-port
video
> card
> support" u have specified as follows.
>
> " Video devices are split up like Lamar said..
> /dev/videoN (0-3). I've used port 0 and 1 with full motion
(at
> 352x288 and 640x480) with no problems.Another nice thing
about
> this
> setup, though I have not tested it, while "motion" is
using
> /dev/video0 and /dev/video1, I _think_ I can use port 2 and
3
> with
> other applications without interfering with motion (ie - not
> conflicting - device busy.. etc). "
>
> I have similar problem. I am using Xawtv to view TV. It
reads
> from
> "/dev/video0". Xawtv records video streams in "avi" format.
And
> then
> we have to convert it into "mpeg". What I want is to record
> video
> streams directly into "mpeg". So I used FFMPEG to record
video
> streams. It also uses "/dev/video0". When I run FFMPEG in
> parallel
> with XAWTV "device or resource busy" error occurs. XAWTV
uses
> "/dev/video0" and when I execute FFMPEG, it also tries to
read
> "/dev/video0" which results in aforesaid error.I tried
creating
> a
> symbolic link "/dev/video0" and made FFMPEG to use it. It
fails
> to
> work out.
>
> ffmpeg -vd /dev/video0 /root/samp.mpg.
>
> What i want is to visualize "xawtv" and record video streams
> using
> "ffmpeg" simultaneously. How to accomplish this ? Is it
possible
> to
> make the video input available at both /dev/video0 and
/dev/video1
> ?
> So that I can make FFMPEG to use "/dev/video1" and let XAWTV
use
> the
> default /dev/video0.
>
> I am using bttv based "Pixel View PlayTV Pro" Tv Tuner card
> (BT878)
> and kernel 2.4.18-14.
>
> With Regards,
> S.Suriya Mohan.
>
> ___________________________________________________
> Download the hottest & happening ringtones here!
> OR SMS: Top tone to 7333
> Click here now:
> http://sms.rediff.com/cgi-bin/ringtone/ringhome.pl
>
>
>
> --
> video4linux-list mailing list
> Unsubscribe
mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
--
video4linux-list mailing list
Unsubscribe
mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
___________________________________________________
Download the hottest & happening ringtones here!
OR SMS: Top tone to 7333
Click here now:
http://sms.rediff.com/cgi-bin/ringtone/ringhome.pl
