Send video4linux-list mailing list submissions to
video4linux-list@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://listman.redhat.com/mailman/listinfo/video4linux-list
or, via email, send a message with subject or body 'help' to
video4linux-list-request@xxxxxxxxxx
You can reach the person managing the list at
video4linux-list-admin@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of video4linux-list digest..."
------------------------------------------------------------------------
Today's Topics:
1. [ADVICE WANTED] by new cpia driver maintainer... (Duncan Haldane)
2. Re: [ADVICE WANTED] by new cpia driver maintainer... (Mark McClelland)
3. Re: Xawtv Help (Randy Halverson)
4. about bt878 pc104 card questions (ΤψΈ»ΐ΄)
5. Re: Problem with v4l2 & bttv mmap returning 13 (EACCES) (Gerd Knorr)
6. Re: terratec cinergy 400 (Gerd Knorr)
7. Re: xawtv & mmap (Gerd Knorr)
8. Pinnacle PCTV Pro (Edward Wohlman)
------------------------------------------------------------------------
Subject:
[ADVICE WANTED] by new cpia driver maintainer...
From:
Duncan Haldane <f.duncan.m.haldane@xxxxxxxxxxxxxxxx>
Date:
Sun, 17 Nov 2002 18:21:33 -0500 (EST)
To:
video4linux-list@xxxxxxxxxx
Hi
I seem to have inherited the position of cpia driver maintainer
for the obsolete cpia-chip based webcams...
I have been pushing updates for the drivers from
http://sourceforge.net/projects/webcam into the 2.4.20 and 2.5.x kernels via
Alan Cox. (A lot of work by the original driver authors had never been
put into official kernel sources).
I am right now trying to get simultaneous viewing of two cpia webcams
working if possible with the v4l1 in 2.4.20-rc2 kernel.
If two cameras are registered, one on /dev/video0 and one on /dev/video1,
and I use e.g. xawtv or gqcam to monitor them, I cannot open /dev/video1
when /dev/video0 is open and vice-versa. This happens for two cpia
devices and one cpia + one ov511 device.
If I try to start the ov511 device with the cpia one already running,
it tries to open, but fails, and the running cpia device also hangs shortly
afterwards.
Am I running into an intrinsic limitation of v4l1, or does this
means something is screwed up
in the cpia driver's v4; initialization, or whatever. Unfortunately,
I dont have two ov511's to see if that combination works ok with v4l1,
assuming that driver is correct.
Any suggestions? Should I expect to be able to simultaneously
view two webcams with v4l1 if some cpia driver bug can be fixed?
Duncan
------------------------------------------------------------------------
Subject:
Re: [ADVICE WANTED] by new cpia driver maintainer...
From:
Mark McClelland <mark@xxxxxxxxxxxxxxxx>
Date:
Sun, 17 Nov 2002 18:12:08 -0800
To:
f.duncan.m.haldane@xxxxxxxxxxxxxxxx
Duncan Haldane wrote:
>If two cameras are registered, one on /dev/video0 and one on
/dev/video1,
>and I use e.g. xawtv or gqcam to monitor them, I cannot open /dev/video1
>when /dev/video0 is open and vice-versa. This happens for two cpia
>devices and one cpia + one ov511 device.
>
>If I try to start the ov511 device with the cpia one already running,
>it tries to open, but fails, and the running cpia device also hangs
shortly
>afterwards.
>
>
That's because both cameras are trying to use nearly all of the USB's
bandwidth. Or, more precisely, each is trying to schedule an ISO packet
of nearly the maximum size (1023, IIRC) at the same time. Only one will
get through. I'm not sure why that hangs the devices though; you'd think
it would just corrupt both cameras' images.
>Am I running into an intrinsic limitation of v4l1, or does this
>means something is screwed up
>in the cpia driver's v4; initialization, or whatever. Unfortunately,
>I dont have two ov511's to see if that combination works ok with v4l1,
>assuming that driver is correct.
>
>
It works, as long as you load ov511 with "cams=2". That will lower the
ISO packet size of each camera to 513 (which is still too big but seems
to work anyway, go figure). I've been able to get three OV511 cameras
working at the same time with packet size of 257, without problems
(other than a really crappy frame rate).
>Any suggestions? Should I expect to be able to simultaneously
>view two webcams with v4l1 if some cpia driver bug can be fixed?
>
Check the descriptors. As long as there's an alternate setting where
MxPS <= 1023 / 2 then you should be in business. You can either have the
packet size or alternate number be a module param, or you can do a
"cams" thing like ov511. Or, you can allow the frame rate to be set
somewhere, and have the driver automatically choose the minimum possible
packet size that can still sustain that frame rate.
The best methodology depends on the hardware design. Some hardware (eg.:
OV511) has no concept of a frame rate, for instance. Other hardware may
require the frame rate to be explicitly lowered when MxPS is reduced.
------------------------------------------------------------------------
Subject:
Re: Xawtv Help
From:
"Randy Halverson" <randyh3@xxxxxxxxxxx>
Date:
Sun, 17 Nov 2002 20:10:50 -0700
To:
<video4linux-list@xxxxxxxxxx>
I have the same card. I don't think bttv supports it. I haven't found any
way to do video capture unless I fire up Windows ME. I got a new X driver
or server from the Gatos project that allows xawtv to work. I think its
http://gatos.sf.net
----- Original Message -----
From: "Phil Lambert" <beerme@xxxxxxxxxxxxxxx>
To: <video4linux-list@xxxxxxxxxx>
Sent: Sunday, November 03, 2002 10:12 AM
Subject: Xawtv Help
I am hoping someone can give me some help with xawtv. I have an ATI
All-in-Wonder 128 Pro AGP. I cannot get xawtv or zapping to work with
RH8. I have seen this card work under RH7.1 but when I try to execute
xawtv I get the following error under RH8.
[beerme@localhost sbin]# xawtv
This is xawtv-3.74, running on Linux/i686 (2.4.18-17.8.0)
can't open /dev/video0: No such device
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: No such device
v4l: open /dev/video0: No such device
no video grabber device available
Any insight that someone can provide is appreciated. FYI, I am running
the default workstation RH8 load with the athlon kernel.
Thanks again,
Phil
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/video4linux-list
------------------------------------------------------------------------
Subject:
about bt878 pc104 card questions
From:
"ΤψΈ»ΐ΄" <zfl21cn@xxxxxxxx>
Date:
Mon, 18 Nov 2002 16:51:55 +0800 (CST)
To:
video4linux-list@xxxxxxxxxx
Hello,all:
I have any questions for getting BGR(8:8:8) image data by my BT878 PC104 card.
1:
How I know my v4l2 is working? I can't use X window on my graphics chip and framebuffer in currently environment. frambuffer is competent for it? xawtv tell me it can't display.
2:
root# ./tuner:
/dev/i2c-0 /0xC0/210.25MHz... write: rc=-1,error=Remote I/O error.
root# ./ir
Remote I/O error.
this is proc/pci infomation. The ioports infomation is suited.
Bus 0,device 12,function 0:
Multimedia video controller:Brooktree lorporation bt878(rev 17)
IRQ 9
Master capable catency=32.Min Gnt=16.Max Lat=40
Prefetchable 32 bit memory at 0xee000000[0xee000fff]
Function 1:
Gnt=4.Max Lat=255 memory at 0xee001000[0xee001fff]
Can any suggestive idea?
thanks
Fulai Zeng
----------------------------------------------
ΙΟ΄«Γΐΐφ»αΤ±φ¦ΥΥ£¬Σ®Θ΅F4Ρέ³?»αΓΕΖ±
http://sms.21cn.com/f4/index.html
Χ¨?µΧγ²ΚΠΕΟΆ£¬ΎΝΚΗΥβΓ΄ΊΓ²ΚΣ®²¨£΅
http://sms.21cn.com/europe.jsp
3ΥΫΘΘΒτΌ΄½«½ΨΦΉ£¬ΒνΙΟΠΠ¶―£΅
http://mail.21cn.com/huodong/9yue/
21CNΘ«ΠΒΝψΒηΣ²ΕΜΙΑΑΑµΗ³΅
http://mail.21cn.com/huodong/11yue/
------------------------------------------------------------------------
Subject:
Re: Problem with v4l2 & bttv mmap returning 13 (EACCES)
From:
Gerd Knorr <kraxel@xxxxxxxxxxx>
Date:
18 Nov 2002 10:19:44 GMT
To:
video4linux-list@xxxxxxxxxx
vid_fd = open(device, O_RDONLY);
^^^^^^^^
vimage[i].data = (char*)mmap(0, vimage[i].vidbuf.length, PROT_WRITE |
^^^^^^^^^^
Doesn't work ...
Gerd
------------------------------------------------------------------------
Subject:
Re: terratec cinergy 400
From:
Gerd Knorr <kraxel@xxxxxxxxxxx>
Date:
18 Nov 2002 10:28:44 GMT
To:
video4linux-list@xxxxxxxxxx
I think a comment about I2C in the kernel notes at the V4L devices would
save many from making the same mistake. Alan?
This isn't true for all v4l drivers. The bttv readme already says so,
and so does the saa7134 readme (althrough that one isn't shipped with
the kernel yet ...)
Gerd
------------------------------------------------------------------------
Subject:
Re: xawtv & mmap
From:
Gerd Knorr <kraxel@xxxxxxxxxxx>
Date:
18 Nov 2002 10:25:19 GMT
To:
video4linux-list@xxxxxxxxxx
I recently noticed that xawtv sometimes tries to mmap() buffers for
display. If you resize the video window, it apparently re-requests and
re-mmap()s the buffers,
Done in grabdisplay mode, for obvious reasons ...
however, it does this without munmap()ping the
old buffers. My drivers gives errors 'buffers already allocated' errors.
Huh? Really? I should have noticed this, as bttv + saa7134 should
return -EBUSY on REQBUFS if there are still buffers mapped ...
Is this indeed true for xawtv-3.78? If so, would a patch to fix this be
appreciated (i.e., is this the intended behaviour or would you rather,
as I imagine it, see the old buffers being munmap()'ed before
requesting/mmap()ing the new buffers?)?
xawtv should unmap them first of course.
Gerd
------------------------------------------------------------------------
Subject:
Pinnacle PCTV Pro
From:
"Edward Wohlman" <eddwo@xxxxxxxxxx>
Date:
Mon, 18 Nov 2002 12:26:29 -0000
To:
<video4linux-list@xxxxxxxxxx>
I'm very new to linux but would like to get my tv card working on it.
I've got the application running, but it cannot tune in to any channels.
This seems to be the same problem as you had, but I don't really
understand how to use these patches, how to get it working. All I can
get at the moment is static.
I'm using Xandros desktop.
Do you think you could help me?
Thanks
Edward
Quote:
Good point! Sorry about those.. dunno what happened.
Basically, the message was to say I'd fixed the problems, and to
apologise to you all. It was the patch - as you correctly pointed out,
I don't think it contained the necessary tuner patches to enable the
tda9887 support required for the mt2032 tuner. It's up and running
using the patches from bytesex.org (slaps head for not trying them
earlier), the tuner is picked up, the tda9887 is enabled and all is
well. Now running 2.4.20-rc1 with the i2c, bttv and tuner patches from
bytesex.org.
Thanks for your help, I've sent a mail to the guy who maintained the
other patch set to let him know, but have had no reply yet.
Cheers,
Philip.
------------------------------------------------------------------------
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/video4linux-list
